Ok so i did this, dns does work on the main node.

As far as I can tell there is nothing wrong with your routing table. I think the problem is either A or D from my list before. Most likely you have the old DNS records cached somewhere. So I suggest f

Change the main IP of your server to the IP you are currently using for the container and see if dns continues to work on the main node.

It's not something stupid like your host blocking port 53 outbound on the non main IP or forcing you to use their DNS servers? CC/HVH has a habit of blocking UDP ports and not telling you in tickets.

(Quote)

Did you try running "dig google.com @8.8.8.8" and seeing if it returns DNS records? I think some ubuntu templates have dig already installed.

(Quote)

And make sure "cat /etc/resolv.conf" inside the container lists the DNS servers you are using.

(Quote)

Have you added the DNS resolvers?

Letsencrypt is finally usable thanks to DNS based ownership verification and https://github.com/Neilpang/le which doesn't require sudo/root. I hate the official, auto updating client. Rings all sort o

I have (had, as they came back) 2 VPS down, in 2 different datacenters. And anycast DNS down, too.

Probably due to the fact that OVH DNS were down, too

11. google-public-dns-a.google.com 0.0% 25 22.3 22.3 22.2 22.3 0.0

cloudkilat cuma pengalaman beli shared, agak susah pas pengaturan DNS (via paralels) entah bawaan paralels atau seting mereka, yang jelas ngatur MX gak bisa dihapus MX default, jadi pas kirim gak nyam

Thanks everyone. as @cociu said, I have edited the zone file with the DNS servers of eleven2 and after a few hours, it accepts the nameservers. @deployvm

Otherwise, if doesn't work still, then use an external DNS.

we have been in DNS industry for 5 years. it's not easy to take the service available always.

Come on OP, is this another step into your "provide DNS" bullshit? Sounds like you're asking for a script to run in the background, like what Cloudflare would do during setup of a ne

* Reverse DNS