DNS failure - - network or configuration issue?
DNS and gateway configuration - - outage?
I’ve got an Ubuntu 18.04 server droplet deployed my DNS resolution is toast. I can’t access my server over ssh. I can only access my server using the web-based browser terminal emulator provided by DigitalOcean so I can’t copy and paste output. I need to use screenshots.
Here is screenshot with apt showing a DNS issue: https://i.imgur.com/KPw0WVV.png
Here are the contents of systemd-resolved –status: https://i.imgur.com/j5lhfY3.png
Here is the output of ip address: https://i.imgur.com/0crGJIT.png
The only file inside the netplan directory is 50-cloud-init.yaml. The contents of this file can be found here: https://i.imgur.com/fUs4BzZ.png
$ ping 184.108.40.206 produces: “Destination Host Unreachable”
$ ip -4 route produces:
220.127.116.11/18 dev eth0 proto kernel scope link src 18.104.22.168 and
10.17.0.0/16 dev eth0 proto kernel scope link src 10.17.0.5
$ sudo ip -4 route add default via 22.214.171.124 dev eth0 produces `RTNETLINK answers: File exists
A DO user with a similar issue asked last year in March but no one replied: https://www.digitalocean.com/community/questions/temporary-failure-resolving-digitalocean-mirrors
Is this a failure on DigitalOcean network? If it is not an outage, what could be wrong with my configuration? What other information could I provide to better diagnose the issue?
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.×