View Full Version : Recommended resolving nameservers
matta
07-14-2005, 09:38 PM
The current list of resolving nameservers for /etc/resolv.conf are:
nameserver 209.51.143.76
nameserver 209.51.128.19
nameserver 209.51.128.20
(Current as of 11/21/2005)
Also note that both ns1.unixshell.com and ns2.unixshell.com are both only DNS hosting servers and cannot be used for resolving.
In the future if the preferred resolver IP's change I will post updates here.
wpietri
10-28-2005, 11:05 PM
Hi! Are these nameservers still the right ones? They don't seem to be working from my box:
% dig www.google.com@209.51.143.76
; <<>> DiG 9.2.5 <<>> www.google.com@209.51.143.76
;; global options: printcmd
;; connection timed out; no servers could be reached
% dig www.google.com@69.93.28.254
; <<>> DiG 9.2.5 <<>> www.google.com@69.93.28.254
;; global options: printcmd
;; connection timed out; no servers could be reached
I'm using one of my own for now, but it's an external box, so I'd rather use local ones.
Thanks,
William
My gentoo install came with the following name servers:
nameserver 209.51.143.76
nameserver 69.93.28.254
nameserver 69.10.150.194
Obviously the last isn't valid, but I came to check the box tonight seeing that some services weren't working correctly. None of those servers are currently responding.
iadea
11-21-2005, 05:41 AM
209.51.143.76
69.93.28.254
I have problems using the above DNS servers.
; <<>> DiG 9.2.4 <<>> @69.93.28.254 www.google.com
;; global options: printcmd
;; connection timed out; no servers could be reached
; <<>> DiG 9.2.4 <<>> @209.51.143.76 www.google.com
;; global options: printcmd
;; connection timed out; no servers could be reached
I am having quite a bit of problems.
Same thing is happening on my box, timeouts on both name servers, have to use an external DNS server for now :(
Hmm no wonder all emails got recejected with domain not found error :(
BTW my vm is on vm1.
Oh I'm using this nameserver for now
209.51.128.17 (dns1.gnax.net)
209.51.128.18 (dns2.gnax.net)
there dns problems right now? nothing is resolving for me. using the two nameservers from what ddmt posted and they work.
I'm having the same problem, "official" servers seem to be down since sometime Saturday. (Thanks ddmt for a pair that work!)
To have one go down is no big deal, that's why we always have two in resolv.conf, but both at the same time? C'mon guys, I expect better. :mad:
matta
11-21-2005, 03:02 PM
Our primary resolver runs dnscache and I suspect was subject to some sort of DoS attack. I have had to installed bind on it to get resolving to start again. I have updated this post with the current list of valid resolvers. Due to the nature of Xen we can't perform mass updates of clients servers.
I have updated this post with the current list of valid resolvers. Due to the nature of Xen we can't perform mass updates of clients servers.
May I suggest that such a critical configuration change should also go out in a mass e-mail...otherwise many people aren't going to find about it until afterwards, when something breaks and they come looking here for support.
matta
11-21-2005, 04:17 PM
I don't mind doing this so much to the forum as users can decide to not receive e-mail. The billing system is not quite so advanced, there is no opt out. We've sent a few via the billing system and received quite a few less than happy responses whenever we mass mail via it. This one is vey important so I will probably do so later.
Just e-mailing the forum users is not sufficient as it represents a minority of total active users.
dlahoti
11-21-2005, 09:18 PM
My brother-in-law just ordered a new server today, and it came
configured with 2 of the old IP's:
# cat /etc/resolv.conf
nameserver 209.51.143.76
nameserver 69.93.28.254
nameserver 69.10.150.194
Why are new servers still being given those old 2?
matta
11-21-2005, 09:40 PM
We have multiple rsync servers setup as distro mirrors. The mirrors are still being synced with the master.
vBulletin v3.0.6, Copyright ©2000-2009, Jelsoft Enterprises Ltd.