DNS service and BIND logs
This reference describes DNS service logs for troubleshooting and verification.
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.
There is one log for each of the DNS 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
View DNS service pool configuration Copy linkLink copied!
Export the DNS pool configuration for troubleshooting purposes.
Before you begin Copy linkLink copied!
- You have the
occommand 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-adminprivileges.
About this task Copy linkLink copied!
In RHOSO 18.0, multiple pools are not supported.
Procedure Copy linkLink copied!
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: bind9Note The
ns_recordssection 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.
List DNS service endpoints Copy linkLink copied!
List DNS service endpoints and their status for troubleshooting.
Before you begin Copy linkLink copied!
- The administrator has created a project for you and has provided you with a
clouds.yamlfile for you to access the cloud. - The
python-openstackclientpackage is on your workstation.$ dnf list installed python-openstackclient