PowerFlex 4.x How To Update DNS Servers

1. From an MVM node, run the following command to view the current DNS servers.

cat /etc/resolv.conf

delladmin@mvm1:~> cat /etc/resolv.conf
### /etc/resolv.conf is a symlink to /run/netconfig/resolv.conf
### autogenerated by netconfig!
#
# Before you change this file manually, consider to define the
# static DNS configuration using the following variables in the
# /etc/sysconfig/network/config file:
#     NETCONFIG_DNS_STATIC_SEARCHLIST
#     NETCONFIG_DNS_STATIC_SERVERS
#     NETCONFIG_DNS_FORWARDER
# or disable DNS configuration updates via netconfig by setting:
#     NETCONFIG_DNS_POLICY=''
#
# See also the netconfig(8) manual page and other documentation.
#
### Call "netconfig update -f" to force adjusting of /etc/resolv.conf.
search boston.ee.com
nameserver 1.2.3.4  <----

2. To add/remove DNS servers on the MVM nodes, edit the NETCONFIG_DNS_STATIC_SERVERS section of the /etc/sysconfig/network/config file.

In the example below, DNS server 5.6.7.8 is being added. Save the file and exit after making the necessary changes.

sudo vi /etc/sysconfig/network/config

delladmin@mvm1:~> sudo vi /etc/sysconfig/network/config
...
## Type:        string
## Default:     ""
#
# List of DNS nameserver IP addresses to use for host-name lookup.
# When the NETCONFIG_DNS_FORWARDER variable is set to "resolver",
# the name servers are written directly to /etc/resolv.conf.
# Otherwise, the nameserver are written into a forwarder specific
# configuration file and the /etc/resolv.conf does not contain any
# nameservers causing the glibc to use the name server on the local
# machine (the forwarder). See also netconfig(8) manual page.
#
NETCONFIG_DNS_STATIC_SERVERS="1.2.3.4 5.6.7.8"  <----

3. Run the following command to push the changes to /etc/resolv.conf:

sudo netconfig update -f

delladmin@mvm1:~> sudo netconfig update -f

4. Verify that the changes have been applied:

delladmin@mvm1:~> cat /etc/resolv.conf
 
### /etc/resolv.conf is a symlink to /run/netconfig/resolv.conf
### autogenerated by netconfig!
#
# Before you change this file manually, consider to define the
# static DNS configuration using the following variables in the
# /etc/sysconfig/network/config file:
#     NETCONFIG_DNS_STATIC_SEARCHLIST
#     NETCONFIG_DNS_STATIC_SERVERS
#     NETCONFIG_DNS_FORWARDER
# or disable DNS configuration updates via netconfig by setting:
#     NETCONFIG_DNS_POLICY=''
#
# See also the netconfig(8) manual page and other documentation.
#
### Call "netconfig update -f" to force adjusting of /etc/resolv.conf.
search boston.ee.com
nameserver 1.2.3.4
nameserver 5.6.7.8     <-----

5. Repeat the above steps on all MVM nodes.

6. Delete the coredns pods to propagate the changes to those pods:

for x in `kubectl get pods -n kube-system| grep -i rke2-coredns-rke2-coredns | awk '{print $1}' | grep -iv auto`; do kubectl delete pods -n kube-system $x; done

7. Verify that DNS changes are now reflected in the coredns pods (there are two coredns pods responsible for DNS):

for x in `kubectl get pods -n kube-system|grep -i rke2-coredns-rke2-coredns|awk '{print $1}'|grep -iv auto`; do echo $x; kubectl exec -it $x -n kube-system -- cat /etc/resolv.conf; echo " "; done
 

rke2-coredns-rke2-coredns-6d6fb45d66-8t962
search boston.ee.com
nameserver 1.2.3.4
nameserver 5.6.7.8     <-----
 
rke2-coredns-rke2-coredns-6d6fb45d66-b5c8f
search boston.ee.com
nameserver 1.2.3.4
nameserver 5.6.7.8     <-----