Questo contenuto non è disponibile nella lingua selezionata.
Chapter 2. Planning a DNS service deployment
This section discusses topics that are important to consider when planning your DNS service (designate) deployment with Red Hat OpenStack Services on OpenShift (RHOSO).
The topics included in this section are:
2.1. DNS service (designate) feature support matrix Copia collegamentoCollegamento copiato negli appunti!
The following table lists features in the DNS service (designate) that Red Hat OpenStack Services on OpenShift (RHOSO) 18.0 supports.
| Feature | Support level in RHOSO 18.0? |
|---|---|
| Back end - BIND 9 | Full support |
| Back end - all others | No support |
| Denylists (blacklists) | Full support |
| Designate Agent service | No support |
| Designate API - admin | No support |
| Designate API - v1 | No support |
| Designate API - v2 | Full support |
| Designate client - SDK | No support |
| Designate client - CLI | No support |
| Designate dashboard (horizon) | Full support |
| Designate database - MariaDB/Galera | Full support |
| Designate database - all others | No support |
| Designate notifications | Full support |
| Designate OpenStack client plug-in - CLI | Full support |
| Designate service - Central | Full support |
| Designate service - miniDNS | Full support |
| Designate service - Pool Manager | No support |
| Designate service - Producer | Full support |
| Designate service - Sink | No support |
| Designate service - Zone Manager | No support |
| Designate tempest plug-in | Full support |
| Designate service - Worker | Full support |
| Distributed lock manager - Redis | Full support |
| Distributed lock manager - all others | No support |
| hardware architecture - x86_64 | Full support |
| hardware architecture - all others | No support |
| High availability (HA) deployments | Full support |
| IPv4 | Full support |
| IPv6 | Technology Preview |
| Monasca integration | No support |
| OpenStack Python SDK - designate | Full support |
| Pool scheduler - default | Full support |
| Pool scheduler - all others | No support |
| Pools - single | Full support |
| Pools - multiple | No support |
| Quotas | Full support |
| Record type - A | Full support |
| Record type - AAAA | Full support |
| Record type - CAA | Full support |
| Record type - CERT | Full support |
| Record type - CNAME | Full support |
| Record type - MX | Full support |
| Record type - NAPTR | Full support |
| Record type - NS | Full support |
| Record type - PTR | Full support |
| Record type - SOA | Full support |
| Record type - SPF | Full support |
| Record type - SRV | Full support |
| Record type - SSHFP | Full support |
| Record type - TXT | Full support |
| Record types - all others | No support |
| Recursive resolver - Unbound | Full support |
| Recursive resolver - all others | No support |
| Role-based access control (RBAC) | Full support |
| Top-level domains (TLDs) | Full support |
| TSIG keys | Full support |
| Zone abandon | No support |
| Zone import and export | Full support |
| Zone ownership transfer | Full support |
| Zones - primary | Full support |
| Zones - secondary | No support |
2.2. DNS service resource requirements Copia collegamentoCollegamento copiato negli appunti!
The Red Hat OpenStack Services on OpenShift (RHOSO) DNS service (designate) requires a dedicated network, designate, and depends on various RHOSO core components.
These RHOSO core components are:
- Identity service (keystone)
- RabbitMQ
- MariaDB
- Redis
2.3. Integrating the DNS and Networking services Copia collegamentoCollegamento copiato negli appunti!
During deployment of the Red Hat OpenStack Services on OpenShift (RHOSO) DNS service (designate), you can choose to integrate with the RHOSO Networking service (neutron). When the DNS and Networking services are integrated, DNS records are automatically created whenever a cloud user creates a virtual machine instance, port, or floating IP by using the required zones, networks, and subnets provided by the cloud administrator.
For more information, see Using an integrated DNS service.
2.4. Recommended DNS service topology Copia collegamentoCollegamento copiato negli appunti!
The recommended topology consists of deploying the DNS service on the Red Hat OpenStack Services on OpenShift (RHOSO) control plane.
Figure 2.1. Recommended DNS service topology
In Figure 2.1, the DNS service components are running in their respective pods. The pods that are darker in color are the resources that the DNS service shares with the other RHOSO services.
The dotted lined pods represent an optional placement for BIND and Unbound. If your site has a heavy data traffic footprint, you might want to use a dedicated host to contain BIND and Unbound, respectively.
2.5. About DNS service high availability Copia collegamentoCollegamento copiato negli appunti!
The Red Hat OpenStack Platform (RHOSO) DNS service (designate) combines load balancing of data traffic and fault tolerance in a high availability mode known as active-active High Availability mode. In active-active mode, the DNS service simultaneously runs its component services on three or more nodes. If one of the nodes fail, the remaining nodes continue to run and to avoid interruptions and declines in performance. The DNS service attempts to load balance work across all of the service instances.
The DNS service components are run as services in the RHOSO control plane. For those environments with a distributed RHOSO control plane, the DNS service is highly available.