Setting a public DNS server inside the VM

You can configure a public DNS server inside the VM when internal VMware DNS is unreliable, external name resolution fails within Kubernetes, or you need to override DHCP-provided DNS before installing DevOps Loop.

Ensure that you have administrator privileges on the RHEL system where DevOps Loop will be installed.

Note: These steps apply to virtualized environments such as VMware or other hypervisor-based platforms that provide their own DNS or DHCP services.

Run the following command to update the nameserver in the resolv.conf file:
```
nmcli connection show
```
Get the connection name for your network adapter from the previous command output (for example, ens160) and replace the <connection_name> string in the following commands:
```
nmcli connection modify <connection_name> ipv4.ignore-auto-dns yes
    nmcli connection modify <connection_name> ipv4.dns "8.8.8.8"
    nmcli connection up <connection_name>
```
Confirm that the resolv.conf file now contains the expected DNS entry by running:
```
cat /etc/resolv.conf
```
Expected output:
```
nameserver = 8.8.8.8
```

Delete the CoreDNS pods to apply the changes:

kubectl get pods -n kube-system | grep coredns
    kubectl delete pod <coredns pod name 1> -n kube-system
    kubectl delete pod <coredns pod name 2> -n kube-system

You have successfully configured a public DNS server inside the VM.