I then have a TEST-DC server with AD on it, using the DNS from OVH on it.

(Quote)

(Quote)

(Quote)

For my personal things: ~ $400 / mth for dedicated servers, VPSes / Cloud VMs, DNS services, Backup services, VPN, subscribed PacktPub

IPv6 rDNS is required as one domain is used as a proof-of-concept (sort of) for proper DNS management. And rDNS adds convenience (identifying servers accessed by IP, e.g. for NTP - using local PTR is

Manual reverse DNS [PTR] management

* IP: 1x v4, native /64 v6, both with full rDNS control

I currently don't support reverse DNS at this time.

# dns-* options are implemented by the resolvconf package, if installed

* rDNS: We will change the reverse DNS for your IP to whatever you like for free.

(Quote)

Perhaps I just had some bad luck at BHS previously, was quite a bit slower when testing amongst a variety of queries. The thing that tipped me off to it was the rDNS lookups OpenSSH does for the conne

But yes, I agree, it depend on the cache. Google (and other like OpenDNS) get lot of request. The probability that you request something which is not in cache is low.

Even though it's lower latency, I found it took WAYYY longer to do standard lookups vs OpenDNS or Google DNS. Those servers must be getting hammered, lol. Even though Google DNS is like +20ms away, it

There's no decent implementation in VestaCP though unless you host DNS with it, so not using it on the classic product does make more sense.

That's what I did, set up a DNS resolver, forward all DNS requests to 213.186.33.99 and then point guest OSs to the internal IP of the DNS server you're running.

(Quote)

(Quote)

(Quote)