Which resolvers should i use? When i try to wget something it always takes like 3-4 seconds before the hostname gets translated to ip address - that does not seem normal.



I am running RHEL5 with Cpanel/WHM (latest). Any ideas?

no one?

i added resolver1.opendns.com

to top of the list. the performance is really good now, but anything unresolvable resolves to 208.67.216.132 which also isn't completely ok.

I personally use this configuration in /etc/resolv.conf

While not always the fastest they are very fast and work fine. When in doubt those are what I normally use.

Best to put in a ticket and figure out what resolvers are in your DC, each of the datacenters has a different set of resolvers.

I just posted all of our recursive DNS servers here:
http://forums.theplanet.com/index.php?showtopic=90730

yep i have my server in hstntx2 and those correctly setup, but their performance is far beyond my expectation (and opendns resolver performance)

Hstntx2
66.98.240.131
67.15.31.131

excuse my idiot question, but in etc/resolv.conf I insert my nameservers ips or these? (server in hstntx2)

66.98.240.131
67.15.31.131




WHm => Networking Setup => Resolver Configuration

According to: http://forums.theplanet.com/index.php?showtopic=90730


Hstntx2
66.98.240.131
67.15.31.131

Yes, you have what you should have.

At least for my box, resolves are happening super slowly (up to 4-5 seconds), I assume I'm in Dllstx4 since my resolv.conf was untouched since box install a few months ago, and it points to the ones listed for Dllstx4 in the other thread.

Can someone please look into this?

Now that I'm writing this and trying again, it seems a little faster (probably because I switched the order of the hosts in my resolv.conf), but this is still bad (this was done on my server with 0.00 load):

[root@new plugins]# time nslookup yahoo.com
Server: 216.185.111.10
Address: 216.185.111.10#53

Non-authoritative answer:
Name: yahoo.com
Address: 206.190.60.37
Name: yahoo.com
Address: 68.180.206.184


real 0m2.071s
user 0m0.004s
sys 0m0.006s

This should NOT take >2sec! In fact, this time it obviously skipped the first 2 DNS servers in my resolv.conf, which definitely means to me, there's something wonky. Here's my resolv.conf:

[root@new plugins]# cat /etc/resolv.conf
# see http://forums.theplanet.com/index.php?showtopic=90730
nameserver 67.19.0.10
nameserver 67.19.1.10
nameserver 216.185.111.10
nameserver 69.56.222.10

We were experiencing some issues yesterday with a few of the DLLSTX4 resolvers after one of the scheduled maintenances. This should now be resolved, please PM me if you continue to experience issues.

I'm experiencing problems with this right this second. My server uses by default
67.19.0.10
67.19.1.10

These were on error a few days ago and I was told via support ticket to use
70.84.160.10
70.84.161.10

instead...and now these are down too, and the originals aren't working either.

What gives? Is there somewhere I can see a vaguely realtime status indicator of the reverse DNS servers?

The IPs given are all using 'AnyCast' Technologies, which means it will always attempt to hit the local (closest) DNS cluster before leaving the datacenter. Recently we were experiencing some issues in DLLSTX4, and have made some further adjustments that should prevent this from happening in the future.