PowerFlex 4.x: come aggiornare i server DNS
Summary: Questo articolo della Knowledge Base descrive come modificare (rimuovere/aggiungere) i server DNS in un'ambiente PFMP 4.x con i nodi MVM che eseguono OS SLES 15 e versioni successive.
Instructions
1. Da un nodo MVM, eseguire il comando seguente per visualizzare i server DNS correnti.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. Per aggiungere/rimuovere server DNS sui nodi MVM, modificare la sezione NETCONFIG_DNS_STATIC_SERVERS del file /etc/sysconfig/network/config.
Nell'esempio riportato di seguito, viene aggiunto il server DNS 5.6.7.8. Salvare il file e uscire dopo aver apportato le modifiche necessarie.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. Eseguire il seguente comando per inviare le modifiche a /etc/resolv.conf:
sudo netconfig update -f
delladmin@mvm1:~> sudo netconfig update -f
4. Verificare che le modifiche siano state applicate:
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. Ripetere i passaggi precedenti su tutti i nodi MVM.
6. Eliminare i pod coredns per propagare le modifiche a tali pod:
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. Verificare che le modifiche DNS siano ora riflesse nei pod coredns (sono presenti due pod coredns responsabili del 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 <-----