cancel
Showing results for 
Search instead for 
Did you mean: 

DNS not seeing a web site..

Rigga
Grafter
Posts: 57
Registered: ‎31-07-2007

DNS not seeing a web site..

Hi all,
I am currently using the plusnet DNS servers,
212.159.6.9
212.159.6.10
And I am unable to locate the www.tudorhallschool.com web site.
If I switch to the open DNS servers, it finds it first time.
I have waited over 4 weeks to report this to allow for propagation.
Any ideas???
R.
2 REPLIES 2
Anonymous
Not applicable

Re: DNS not seeing a web site..

You might want to read the following threads, as the Plusnet DNS seems to have problems with several school's websites  Angry
http://community.plus.net/forum/index.php/topic,95618.0.html
and
http://community.plus.net/forum/index.php/topic,89425.0.html
MJN
Pro
Posts: 1,318
Thanks: 161
Fixes: 5
Registered: ‎26-08-2010

Re: DNS not seeing a web site..

You might be interested in this thread which discussed similar problems recently, however I do not think the same cause is to blame this time.
What appears to be happening at the moment is that the DNS responsibility for the e4education.co.uk domain (which www.tudorhallschool.com is an alias to records of) appears to be being migrated from Rackspace to LiveDNS (perhaps as part of a general hosting move) however it is being done badly because inconsistencies of authoritative data are occurring and cracks appearing. In particular, both Rackspace and LiveDNS both consider themselves authoritive for the e4education.co.uk domain but only Rackspace have any records within it (e.g. web7.e4education.com in this case). Unfortunately Nominet (.uk) say that LiveDNS are the authority...
The bottom line of both these episodes is that whoever is responsible for DNS for UK schools really doesn't know what they're doing. There's really no excuse other than incompetence to account for what is happening here. I don't mean to sound nasty, but given the consequences of getting this wrong it really ought to be being managed by someone with a handle on what needs to be done.
In your particular case I don't think there is much that Plusnet can do about it because their resolvers are only taking the word of the broken authotitative servers (moving from PowerDNS to BIND might help but that's only because it behaves differently when looking up CNAMEs (aliases) - neither is fundamentally right/wrong though). The likes of OpenDNS are a bit more resilient to these problems through extreme caching of previous results, and perhaps they're not using PowerDNS either.
Mathew