|
| 1 | +# DNS troubleshooting |
| 2 | + |
| 3 | +## DNS resolution for pods |
| 4 | + |
| 5 | +### Driver Container failed to access archive.ubuntu.com |
| 6 | + |
| 7 | +#### Issue: |
| 8 | + |
| 9 | +Driver Container logs display the following error messages: |
| 10 | + |
| 11 | + |
| 12 | + |
| 13 | +#### Troubleshooting: |
| 14 | + |
| 15 | +follow the steps located here: https://kubernetes.io/docs/tasks/administer-cluster/dns-debugging-resolution/ to troubleshoot DNS pod resolution. |
| 16 | + |
| 17 | +To install the dnsutils pod, launch the command: |
| 18 | +``` |
| 19 | +kubectl apply -f https://k8s.io/examples/admin/dns/dnsutils.yaml |
| 20 | +``` |
| 21 | + |
| 22 | +In a working CNS deployment, you should have an output similar to below: |
| 23 | + |
| 24 | +``` |
| 25 | +nvidia@ipp1-1394:~$ kubectl exec -i -t dnsutils -- nslookup archive.ubuntu.com |
| 26 | +Server: 10.96.0.10 |
| 27 | +Address: 10.96.0.10#53 |
| 28 | +
|
| 29 | +Non-authoritative answer: |
| 30 | +Name: archive.ubuntu.com |
| 31 | +Address: 91.189.91.82 |
| 32 | +Name: archive.ubuntu.com |
| 33 | +Address: 185.125.190.82 |
| 34 | +Name: archive.ubuntu.com |
| 35 | +Address: 185.125.190.83 |
| 36 | +Name: archive.ubuntu.com |
| 37 | +Address: 185.125.190.81 |
| 38 | +Name: archive.ubuntu.com |
| 39 | +Address: 91.189.91.81 |
| 40 | +Name: archive.ubuntu.com |
| 41 | +Address: 91.189.91.83 |
| 42 | +Name: archive.ubuntu.com |
| 43 | +Address: 2620:2d:4002:1::103 |
| 44 | +Name: archive.ubuntu.com |
| 45 | +Address: 2620:2d:4000:1::101 |
| 46 | +Name: archive.ubuntu.com |
| 47 | +Address: 2620:2d:4002:1::102 |
| 48 | +Name: archive.ubuntu.com |
| 49 | +Address: 2620:2d:4002:1::101 |
| 50 | +Name: archive.ubuntu.com |
| 51 | +Address: 2620:2d:4000:1::103 |
| 52 | +Name: archive.ubuntu.com |
| 53 | +Address: 2620:2d:4000:1::102 |
| 54 | +``` |
| 55 | + |
| 56 | +Note that Name must be exactly 'archive.ubuntu.com': |
| 57 | + |
| 58 | +***Name: archive.ubuntu.com*** |
| 59 | + |
| 60 | + |
| 61 | +If you get a different output, it is recommended to fix the root cause (check with the team in charge of the DNS server. They may have created an entry for the archive.ubuntu.com and if this is the case, they must remove it). |
| 62 | + |
0 commit comments