Chapter 10. Troubleshooting the DNS service

Procedure

1. Log in to one of the Controller nodes and display the current running DNS service pool configuration to the console.

   Example

   In this example, the administrator accesses a Controller node, controller-0.ctlplane, through SSH as the tripleo-admin user and executes the designate-manage pool show_config command running in the designate_central container:

   $ ssh tripleo-admin@controller-0.ctlplane sudo podman exec \
   designate_central designate-manage pool show_config

   Sample output

   Pool Configuration:
   -------------------
   also_notifies: []
   attributes: {}
   description: Default Pool
   id: 794ccc2c-d751-44fe-b57f-8894c9f5c842
   name: default
   nameservers:
   - host: 192.0.2.111
     port: 53
   - host: 192.0.2.109
     port: 53
   - host: 192.0.2.131
     port: 53
   ns_records:
   - hostname: ns2.example.com.
     priority: 2
   - hostname: ns1.example.com.
     priority: 1
   - hostname: ns3.example.com.
     priority: 3
   targets:
   - description: BIND9 Server 3
     masters:
     - host: 192.0.2.137
       port: 16002
     - host: 192.0.2.137
       port: 16001
     - host: 192.0.2.137
       port: 16000
     options:
       host: 192.0.2.111
       port: '53'
       rndc_config_file: /etc/designate/private/bind3.conf
       rndc_host: 192.0.2.111
       rndc_port: '953'
     type: bind9
   - description: BIND9 Server 2
     masters:
     - host: 192.0.2.137
       port: 16001
     - host: 192.0.2.137
       port: 16002
     - host: 192.0.2.137
       port: 16000
     options:
       host: 192.0.2.131
       port: '53'
       rndc_config_file: /etc/designate/private/bind2.conf
       rndc_host: 192.0.2.131
       rndc_port: '953'
     type: bind9
   - description: BIND9 Server 1
     masters:
     - host: 192.0.2.137
       port: 16002
     - host: 192.0.2.137
       port: 16001
     - host: 192.0.2.137
       port: 16000
     options:
       host: 192.0.2.109
       port: '53'
       rndc_config_file: /etc/designate/private/bind1.conf
       rndc_host: 192.0.2.109
       rndc_port: '953'
     type: bind9

2. If you want to export the current pool configuration to a file, use the designate-manage pool generate_file command.

   Example

   In this example, the administrator accesses a Controller node, controller-0.ctlplane, through SSH as the tripleo-admin user and executes the designate-manage pool generate_file --file <file_name> command running in the designate_central container. The DNS service exports the current pool configuration to a file that is specified by the --file option, in this example, ~/my_dns_service_config.yaml:

   $ ssh tripleo-admin@controller-0.ctlplane sudo podman exec \
   designate_central designate-manage pool generate_file \
   --file ~/my_dns_service_config.yaml

   Tip

   Use the podman cp command to copy files from a container to your local system.

Procedure

1. Source your credentials file.

   Example

   $ source ~/overcloudrc

2. List the available RHOSP service endpoints:

   $ openstack endpoint list --service designate -c Interface -c URL

   Sample output

   +-----------+-------------------------+
   | Interface | URL                     |
   +-----------+-------------------------+
   | internal  | http://172.17.1.44:9001 |
   | public    | http://10.0.0.147:9001  |
   | admin     | http://172.17.1.44:9001 |
   +-----------+-------------------------+