Advertisement
Twometer

DNS results

Feb 12th, 2022 (edited)
115
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.52 KB | None | 0 0
  1. ### DNS on my local machine
  2. $ nslookup google.de
  3. Server: 127.0.0.53
  4. Address: 127.0.0.53#53
  5.  
  6. Non-authoritative answer:
  7. Name: google.de
  8. Address: 142.250.179.163
  9. Name: google.de
  10. Address: 2a00:1450:400e:802::2003
  11.  
  12. ### DNS on docker ###
  13. $ sudo docker run -it tutum/dnsutils nslookup google.de
  14. ;; connection timed out; no servers could be reached
  15.  
  16. ### Ping from within docker ###
  17. $ sudo docker run -it tutum/dnsutils ping 1.1.1.1
  18. PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
  19. From 172.17.0.2 icmp_seq=1 Destination Host Unreachable
  20. From 172.17.0.2 icmp_seq=2 Destination Host Unreachable
  21. From 172.17.0.2 icmp_seq=3 Destination Host Unreachable
  22. From 172.17.0.2 icmp_seq=5 Destination Host Unreachable
  23. From 172.17.0.2 icmp_seq=6 Destination Host Unreachable
  24. From 172.17.0.2 icmp_seq=7 Destination Host Unreachable
  25. From 172.17.0.2 icmp_seq=8 Destination Host Unreachable
  26. From 172.17.0.2 icmp_seq=9 Destination Host Unreachable
  27. ^C
  28. --- 1.1.1.1 ping statistics ---
  29. 11 packets transmitted, 0 received, +8 errors, 100% packet loss, time 10232ms
  30. pipe 4
  31.  
  32.  
  33. ### I then tried restarting the docker demon - and it started working again ###
  34. $ sudo systemctl restart docker
  35.  
  36. $ sudo docker run -it tutum/dnsutils nslookup google.de
  37. Server: 85.214.7.22
  38. Address: 85.214.7.22#53
  39.  
  40. Non-authoritative answer:
  41. Name: google.de
  42. Address: 142.250.179.163
  43.  
  44. ### But, the very next docker run failed again
  45. $ sudo docker run -it tutum/dnsutils nslookup google.de
  46. ;; connection timed out; no servers could be reached
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement