Red Hat Summit Red Hat SummitSupportoConsoleSviluppatoriInizia una provaContatti

Questo contenuto non è disponibile nella lingua selezionata.

Chapter 10. Troubleshooting the DNS service

By reviewing the Red Hat OpenStack Services on OpenShift (RHOSO) DNS service (designate) logs and using some simple commands, you can verify that the service is running properly. These actions are the first steps in troubleshooting the DNS service.

The topics included in this section are:

10.1. DNS service and BIND logs
Copia collegamento

Reviewing the Red Hat OpenStack Services on OpenShift (RHOSO) DNS service (designate) logs, can be useful when troubleshooting issues.

There is one log for each of the component services:

  • designate-api
  • designate-backendbind9
  • designate-central
  • designate-mdns
  • designate-producer
  • designate-redis
  • designate-unbound
  • designate-worker

You access the DNS service logs by running the following command from a workstation that has access to the RHOSO control plane as a user with cluster-admin privileges: 

$ oc logs <object_type>/<resource_name>
Example
$ oc logs deployment/designate-api

10.2. Viewing the DNS service pool configuration
Copia collegamento

You can use a copy of the DNS pool configuration to troubleshoot the Red Hat OpenStack Services on OpenShift (RHOSO) DNS service (designate).

Note

In RHOSO 18.0, multiple pools are not supported.

Prerequisites

  • You have the oc command line tool installed on your workstation.
  • You are logged on to a workstation that has access to the RHOSO control plane as a user with cluster-admin privileges.

Procedure

  • Run the designate-manage pool command remotely in the designate-central pod: 

    $ oc exec -it deployment/designate-central -- \
designate-manage pool show_config
    Sample output
    Pool Configuration:
-------------------
also_notifies: []
attributes: {}
description: Default BIND Pool
id: 794ccc2c-d751-44fe-b57f-8894c9f5c842
name: default
nameservers:
- host: 172.28.0.100
  port: 53
- host: 172.28.0.101
  port: 53
- host: 172.28.0.102
  port: 53
ns_records:
- hostname: ns1.example.org.
  priority: 10
- hostname: ns2.example.org.
  priority: 20
targets:
- description: BIND9 Server 0 (172.28.0.100)
  masters:
  - host: 172.28.0.98
    port: 5354
  - host: 172.28.0.99
    port: 5354
  - host: 172.28.0.97
    port: 5354
  options:
    host: 172.28.0.100
    port: '53'
    rndc_host: 172.28.0.100
    rndc_key_file: /etc/designate/rndc-keys/rndc-key-0
    rndc_port: '953'
  type: bind9
- description: BIND9 Server 1 (172.28.0.101)
  masters:
  - host: 172.28.0.99
    port: 5354
  - host: 172.28.0.97
    port: 5354
  - host: 172.28.0.98
    port: 5354
  options:
    host: 172.28.0.101
    port: '53'
    rndc_host: 172.28.0.101
    rndc_key_file: /etc/designate/rndc-keys/rndc-key-1
    rndc_port: '953'
  type: bind9
- description: BIND9 Server 2 (172.28.0.102)
  masters:
  - host: 172.28.0.97
    port: 5354
  - host: 172.28.0.98
    port: 5354
  - host: 172.28.0.99
    port: 5354
  options:
    host: 172.28.0.102
    port: '53'
    rndc_host: 172.28.0.102
    rndc_key_file: /etc/designate/rndc-keys/rndc-key-2
    rndc_port: '953'
  type: bind9
    Note

    The ns_records section contains the list of name servers that the DNS service advertises in the zones as available for query. These name servers are advertised from external networks.

10.3. Listing available DNS service endpoints
Copia collegamento

Determining the Red Hat OpenStack Services on OpenShift (RHOSO) DNS service (designate) endpoint and its status, can be useful when troubleshooting issues.

Prerequisites

  • The administrator has created a project for you and has provided you with a clouds.yaml file for you to access the cloud.

  • The python-openstackclient package resides on your workstation. 

    $ dnf list installed python-openstackclient

Procedure

  1. Confirm that the system OS_CLOUD variable is set for your cloud: 

    $ echo $OS_CLOUD
my_cloud

    Reset the variable if necessary: 

    $ export OS_CLOUD=my_other_cloud

    As an alternative, you can specify the cloud name by adding the --os-cloud <cloud_name> option each time you run an openstack command.

  2. List the RHOSO service endpoints: 

    $ openstack endpoint list -c "Service Name" -c Enabled -c URL
    Sample output
    +--------------+---------+-------------------------------------------------+
| Service Name | Enabled | URL                                             |
+--------------+---------+-------------------------------------------------+
| swift        | True    | http://198.51.100.61:8080                       |
| designate    | True    | http://203.0.113.103:9001                       |
| heat-cfn     | True    | http://192.0.2.137:8000/v1                      |
| designate    | True    | http://192.0.2.137:9001                         |
| placement    | True    | http://203.0.113.103:8778/placement             |
| cinderv3     | True    | http://203.0.113.103:8776/v3/%(tenant_id)s      |
| heat         | True    | http://203.0.113.103:8004/v1/%(tenant_id)s      |
| heat-cfn     | True    | http://203.0.113.103:8000/v1                    |
| nova         | True    | http://203.0.113.103:8774/v2.1                  |
| heat         | True    | http://192.0.2.137:8004/v1/%(tenant_id)s        |
| glance       | True    | http://203.0.113.103:9292                       |
| heat         | True    | http://203.0.113.103:8004/v1/%(tenant_id)s      |
| glance       | True    | http://203.0.113.103:9292                       |
| neutron      | True    | http://203.0.113.103:9696                       |
| nova         | True    | http://192.0.2.137:8774/v2.1                    |
| cinderv3     | True    | http://192.0.2.137:8776/v3/%(tenant_id)s        |
| placement    | True    | http://203.0.113.103:8778/placement             |
| keystone     | True    | http://192.168.24.17:35357                      |
| neutron      | True    | http://192.0.2.137:9696                         |
| nova         | True    | http://203.0.113.103:8774/v2.1                  |
| heat-cfn     | True    | http://203.0.113.103:8000/v1                    |
| cinderv3     | True    | http://203.0.113.103:8776/v3/%(tenant_id)s      |
| glance       | True    | http://192.0.2.137:9292                         |
| placement    | True    | http://192.0.2.137:8778/placement               |
| swift        | True    | http://198.51.100.61:8080/v1/AUTH_%(tenant_id)s |
| swift        | True    | http://192.0.2.137:8080/v1/AUTH_%(tenant_id)s   |
| designate    | True    | http://203.0.113.103:9001                       |
| keystone     | True    | http://192.0.2.137:5000                         |
| neutron      | True    | http://203.0.113.103:9696                       |
| keystone     | True    | http://203.0.113.103:5000                       |
+--------------+---------+-------------------------------------------------+
Red Hat logoGithubredditYoutubeTwitter

Formazione

Prova, acquista e vendi

Community

Informazioni sulla documentazione di Red Hat

Aiutiamo gli utenti Red Hat a innovarsi e raggiungere i propri obiettivi con i nostri prodotti e servizi grazie a contenuti di cui possono fidarsi. Esplora i nostri ultimi aggiornamenti.

Rendiamo l’open source più inclusivo

Red Hat si impegna a sostituire il linguaggio problematico nel codice, nella documentazione e nelle proprietà web. Per maggiori dettagli, visita il Blog di Red Hat.

Informazioni su Red Hat

Forniamo soluzioni consolidate che rendono più semplice per le aziende lavorare su piattaforme e ambienti diversi, dal datacenter centrale all'edge della rete.

Theme

© 2026 Red HatTorna in cima