DNS doesn't seem to able to look up external addresses

$ sudo snap install microk8s --classic
$ sudo microk8s enable dns

$ sudo microk8s kubectl apply -f https://k8s.io/examples/admin/dns/dnsutils.yaml

$ sudo microk8s kubectl get all --all-namespaces
NAMESPACE     NAME                                          READY   STATUS    RESTARTS   AGE
default       pod/dnsutils                                  1/1     Running   0          2m25s
kube-system   pod/coredns-86f78bb79c-t79sd                  1/1     Running   0          35s
kube-system   pod/calico-node-zg58n                         1/1     Running   0          4m7s
kube-system   pod/calico-kube-controllers-847c8c99d-ltfm4   1/1     Running   0          4m7s

NAMESPACE     NAME                 TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)                  AGE
default       service/kubernetes   ClusterIP   10.152.183.1    <none>        443/TCP                  4m12s
kube-system   service/kube-dns     ClusterIP   10.152.183.10   <none>        53/UDP,53/TCP,9153/TCP   35s

NAMESPACE     NAME                         DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR            AGE
kube-system   daemonset.apps/calico-node   1         1         1       1            1           kubernetes.io/os=linux   4m12s

NAMESPACE     NAME                                      READY   UP-TO-DATE   AVAILABLE   AGE
kube-system   deployment.apps/coredns                   1/1     1            1           35s
kube-system   deployment.apps/calico-kube-controllers   1/1     1            1           4m12s

NAMESPACE     NAME                                                DESIRED   CURRENT   READY   AGE
kube-system   replicaset.apps/coredns-86f78bb79c                  1         1         1       35s
kube-system   replicaset.apps/calico-kube-controllers-847c8c99d   1         1         1       4m8s

DNS debug found here https://kubernetes.io/docs/tasks/administer-cluster/dns-debugging-resolution/

But can’t seem to get anything outside:

$ kubectl exec -i -t dnsutils -- nslookup github.com
;; connection timed out; no servers could be reached

command terminated with exit code 1

$ kubectl exec -i -t dnsutils -- nslookup bbc.co.uk
;; connection timed out; no servers could be reached

command terminated with exit code 1

$ kubectl exec -i -t dnsutils -- nslookup kubernetes.default
;; connection timed out; no servers could be reached

command terminated with exit code 1

[faireai-fmonorchio]

I have this exatcly problem with version v1.23.3 on debian 11 in a ha setup with 3 nodes. Dns pod and service are running correctly. Any help about this?

[natanhp]

I got this error with Microk8s v1.24.3 on CentOS 7.9.2009

kubectl exec -i -t dnsutils -- nslookup kubernetes.default

;; connection timed out; no servers could be reached

command terminated with exit code 1

Update

I managed to solve the issue by enabling ip masquarade

firewall-cmd --add-masquerade --permanent
firewall-cmd --reload

as I mentioned it in https://github.com/canonical/microk8s/issues/2407#issuecomment-1219083565