1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Files
openshift-docs/modules/k8s-nmstate-troubleshooting-dns-disconnected-bind9-dns.adoc
2026-01-21 15:16:22 +00:00

64 lines
1.6 KiB
Plaintext

// Module included in the following assemblies:
//
// * networking/k8s_nmstate/k8s-nmstate-troubleshooting-node-network.adoc
:_mod-docs-content-type: PROCEDURE
[id="k8s-nmstate-troubleshooting-dns-disconnected-bind9-dns_{context}"]
= Configuring the bind9 DNS named server
[role="_abstract"]
For a cluster configured to query a `bind9` DNS server, you can add the `root-servers.net` zone to a configuration file that contains at least one DNS record. For example you can use the `/var/named/named.localhost` as a zone file that already matches this criteria.
.Procedure
. Add the `root-servers.net` zone at the end of the `/etc/named.conf` configuration file by running the following command:
+
[source,terminal]
----
$ cat >> /etc/named.conf <<EOF
zone "root-servers.net" IN {
type master;
file "named.localhost";
};
EOF
----
. Restart the `named` service by running the following command:
+
[source,terminal]
----
$ systemctl restart named
----
. Confirm that the `root-servers.net` zone is present by running the following command:
+
[source,terminal]
----
$ journalctl -u named|grep root-servers.net
----
+
.Example output
[source,terminal]
----
Jul 03 15:16:26 rhel-8-10 bash[xxxx]: zone root-servers.net/IN: loaded serial 0
Jul 03 15:16:26 rhel-8-10 named[xxxx]: zone root-servers.net/IN: loaded serial 0
----
. Verify that the DNS server can resolve the NS record for the `root-servers.net` domain by running the following command:
+
[source,terminal]
----
$ host -t NS root-servers.net. 127.0.0.1
----
+
.Example output
[source,terminal]
----
Using domain server:
Name: 127.0.0.1
Address: 127.0.0.53
Aliases:
root-servers.net name server root-servers.net.
----