running dns is ultra easy.

(Quote)

CloudFlare DNS is solid.

(Quote)

Yeah try Cloudflare's dns it's really good.

(Quote)

I picked Free Dns because it's good enough for hosting normal sites and Namecheap because I like it better than GD. For more complex cases with low volume, I'd go with a paid service. For high complex

(Quote)

You can use cloudflare for just DNS as well, they're amongst the fastest available and free.

Which would be the best option. If you have used any, please comment below. If you know something additional. Please be kind enough to add. Thank you.

Most easy way to use tor (any socks5) for any application (but not for entire system) is to use proxychains(dns working too with this). "proxychains wget http://". For enitre system

* Reverse-dns -> doesn't need match for your domain

Oh I forgot to mention, you should totally use torsocks if your goal is to use it exclusively with Tor -- tsocks is general SOCKS5 proxy and doesn't proxy the DNS query by default; torsocks goes furth

Not if it passes forward confirmed reverse DNS check. But yeah, good call, the A record should match hostname+PTR.

* Reverse DNS Available (On Request)

* Reverse DNS

I would suggest you to setup your own dns instead of using google. Otherwise this could be some caching issues with online.net' dns. Only ISP must apply censorship.

Switch to Google DNS. Online.net resolvers don't honour TTLs below 3600.

(Quote)

I don't know a lot about the inner workings of DNS, but it seems that KAT's nameserver ns1.hostednsor.com won't resolve using Online's resolver.