DNS errors

[#1]

The Plusnet DNS servers are incorrectly resolving www.ferryhouse.co.uk.
All the other servers I use return  77.72.204.33: PlusNet returns  81.21.75.30.
I get the correct web page using other DNS servers, and 404 using Plusnet servers.
~~~
C:\utils>nslookup www.ferryhouse.co.uk 8.8.8.8
Server:  google-public-dns-a.google.com
Address:  8.8.8.8
Non-authoritative answer:
Name:    ferryhouse.co.uk
Address:  77.72.204.33
Aliases:  www.ferryhouse.co.uk

C:\utils>nslookup www.ferryhouse.co.uk 212.159.6.9
Server:  cdns01.plus.net
Address:  212.159.6.9
Non-authoritative answer:
Name:    ferryhouse.co.uk
Address:  81.21.75.30
Aliases:  www.ferryhouse.co.uk

[#2]

Yes me as well.

[#3]

I'm getting the same IP from Google DNS and our DNS servers:
nslookup ferryhouse.co.uk 8.8.8.8
Server:  google-public-dns-a.google.com
Address:  8.8.8.8
Non-authoritative answer:
Name:    ferryhouse.co.uk
Address:  77.72.204.33

nslookup ferryhouse.co.uk 212.159.6.9
Server:  cdns01.plus.net
Address:  212.159.6.9
Non-authoritative answer:
Name:    ferryhouse.co.uk
Address:  77.72.204.33

[#4]

Ah, wait a second. www.ferryhouse.co.uk gives the other IP whereas ferryhouse.co.uk (without the www) is the same.

[#5]

Were the domain records for this updated recently? It may just be that the www record hasn't propagated yet on our DNS>

[#6]

Thanks for the quick response Chris.  I'm trying to check whether there was a recent update. 
At the moment I'm communicating with our friends at Ferry House and they are communicating with their website manager.  I'm trying to get direct contact to him which will cut out one link ....
(Meanwhile, if anyone wants somewhere amazing to stay, I hope I'm not breaking forum rules to say "try http://ferryhouse.co.uk/")

[#7]

Quote from: Chris

It may just be that the www record hasn't propagated yet on our DNS>

The domain has a time to live of 10 minutes, it's now been 5 hours since this was first reported. It doesn't take that long to propagate a change, once the TTL has expired the lookup should query the domains own name server.
Looks like PN's DNS is keeping stale records.

[#8]

Looks like PN's dns is starting to catch up. 

Quote

; <<>> DiG 9.8.6-P1 <<>> www.ferryhouse.co.uk @212.159.6.9 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17737 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;www.ferryhouse.co.uk.          IN      A ;; ANSWER SECTION: www.ferryhouse.co.uk. ; 174    IN      CNAME  ferryhouse.co.uk. ferryhouse.co.uk.      174    IN      A      77.72.204.33 ;; Query time: 32 msec ;; SERVER: 212.159.6.9#53(212.159.6.9) ;; WHEN: Mon Dec 29 21:48:42 GMT Standard Time 2014 ;; MSG SIZE  rcvd: 68

Quote

; <<>> DiG 9.8.6-P1 <<>> www.ferryhouse.co.uk @212.159.6.10 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 46056 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;www.ferryhouse.co.uk.          IN      A ;; ANSWER SECTION: www.ferryhouse.co.uk. ; 300    IN      CNAME  ferryhouse.co.uk. ferryhouse.co.uk.      600    IN      A      81.21.75.30 ;; Query time: 145 msec ;; SERVER: 212.159.6.10#53(212.159.6.10) ;; WHEN: Mon Dec 29 21:48:56 GMT Standard Time 2014 ;; MSG SIZE  rcvd: 68

[#9]

Quote from: npr

The domain has a time to live of 10 minutes, it's now been 5 hours since this was first reported. It doesn't take that long to propagate a change, once the TTL has expired the lookup should query the domains own name server. Looks like PN's DNS is keeping stale records.

It might have a TTL of 10 minutes now (or at 5pm, anyway), but that might have been reduced over the course of the day. It might not reflect what PN's server last saw...

[#10]

It was a reply from PN's dns which showed the TTL to be 10 minutes, so that's no excuse.

[#11]

The incorrect DNS remains.  There have not been any recent changes.  The issue persists this morning.
“Your tenant has reported the problem and has been asked by PlusNet if there have been any recent DNS changes. The answer is not for months, probably years - I fear the problem is deeper, and I guess with PlusNet. Both Google and OpenDNS servers report as I would expect. I cannot check PlusNet DNS servers as they are just timing out on me.”
I do not generally use ISP's DNS (especially when I was on BT).  I have a newish machine and hadn't got round to changing DNS settings, which is why I noticed the issue.

[#12]

@sjptd
Looking a little further into this:
The domain reports it's name servers as ns1.turbodns.co.uk and ns2.turbodns.co.uk.
This is the same for all the DNS servers I've tried.

Quote

; <<>> DiG 9.8.6-P1 <<>> ns ferryhouse.co.uk @8.8.8.8 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 14390 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;ferryhouse.co.uk.              IN      NS ;; ANSWER SECTION: ferryhouse.co.uk.      299    IN      NS      ns1.turbodns.co.uk. ferryhouse.co.uk.      299    IN      NS      ns2.turbodns.co.uk. ;; Query time: 171 msec ;; SERVER: 8.8.8.8#53(8.8.8.8) ;; WHEN: Tue Dec 30 11:50:35 GMT Standard Time 2014 ;; MSG SIZE  rcvd: 79

Unfortunately those name servers give the incorrect IP of 81.21.75.30

Quote

; <<>> DiG 9.8.6-P1 <<>> www.ferryhouse.co.uk @ns2.turbodns.co.uk ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 38702 ;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; WARNING: recursion requested but not available ;; QUESTION SECTION: ;www.ferryhouse.co.uk.          IN      A ;; ANSWER SECTION: www.ferryhouse.co.uk. ; 600    IN      A      81.21.75.30 ;; Query time: 31 msec ;; SERVER: 92.51.159.46#53(92.51.159.46) ;; WHEN: Tue Dec 30 11:53:49 GMT Standard Time 2014 ;; MSG SIZE  rcvd: 54

Strangely all the DNS resolvers I've tried, except for plusnet, appear to use ns1.naphosting.co.uk and ns2.naphosting.co.uk as the name servers for this domain and they report the correct IP address.

Quote

; <<>> DiG 9.8.6-P1 <<>> www.ferryhouse.co.uk @ns1.naphosting.co.uk ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58956 ;; flags: qr aa rd; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 0 ;; WARNING: recursion requested but not available ;; QUESTION SECTION: ;www.ferryhouse.co.uk.          IN      A ;; ANSWER SECTION: www.ferryhouse.co.uk. ; 300    IN      CNAME  ferryhouse.co.uk. ferryhouse.co.uk.      300    IN      A      77.72.204.33 ;; AUTHORITY SECTION: ferryhouse.co.uk.      300    IN      NS      ns2.turbodns.co.uk. ferryhouse.co.uk.      300    IN      NS      ns1.turbodns.co.uk. ;; Query time: 31 msec ;; SERVER: 83.223.98.50#53(83.223.98.50) ;; WHEN: Tue Dec 30 12:10:45 GMT Standard Time 2014 ;; MSG SIZE  rcvd: 113

From the above it looks like there may be something misconfigured in the domains records. I'm guessing that ns1.naphosting.co.uk and ns2.naphosting.co.uk should be configured as the domains name server and not ns1.turbodns.co.uk and ns2.turbodns.co.uk. Whoever is hosting your domain should be able to advise on this.
Why PN's dns behaves differently to all the other dns resolvers ---- I haven't a clue. 
It does rather look like PN's dns is doing things correctly and all the others are not. --- that can't be right surely. 

[#13]

@npr 
Thankyou very much for that.  I will report it back to the webmaster to see if he get the name servers resolved.
Meanwhile, I'm brushing up my knowledge of how dns works (or doesn't).
Another oddity is that www.ferryhouse.co.uk is always wrong (81...) with Plusnet.
ferryhouse.co.uk has given me wrong (81...) and right (77...) answers (almost?) at random on both cdns01.plus.net and cdns02.plus.net

[#14]

Even odder.
I checked at Nominet (http://www.nominet.org.uk/whois/lookup?query=ferryhouse.co.uk) and it gives
Name servers:
    ns1.naphosting.co.uk
    ns2.naphosting.co.uk
(and it does for www.ferryhouse.co.uk as well).
I don't know enough about the DNS system to know the roles of Nominet and of the source for the general
nslookup -type=NS www.ferryhouse.co.uk resolver1.opendns.com
type of lookup, and which is definitive.

[#15]

AFAIK nominet (nic.uk) hold the authoritative answer for the nameservers of UK domains.
ns1.nic.uk says ns*.naphosting.co.uk holds the authoritative record for the domain ferryhouse.co.uk.
When you query ns*.naphosting.co.uk it gives the correct IP for the web site which is fine.
The problem is, it also reports the domains nameserver as ns*.turbodns.co.uk which it wrong, although this only gives a problem to PN's dns servers.
AFAIK the record at ns*.naphosting.co.uk should either not contain a nameserver or if it does it should point to ns1.naphosting.co.uk and ns2.naphosting.co.uk.
A dig trace may help explain the lookup process.

Quote

; <<>> DiG 9.8.6-P1 <<>> +trace www.ferryhouse.co.uk ;; global options: +cmd .                      273227  IN      NS      c.root-servers.net. .                      273227  IN      NS      h.root-servers.net. .                      273227  IN      NS      g.root-servers.net. .                      273227  IN      NS      k.root-servers.net. .                      273227  IN      NS      m.root-servers.net. .                      273227  IN      NS      b.root-servers.net. .                      273227  IN      NS      j.root-servers.net. .                      273227  IN      NS      d.root-servers.net. .                      273227  IN      NS      a.root-servers.net. .                      273227  IN      NS      i.root-servers.net. .                      273227  IN      NS      l.root-servers.net. .                      273227  IN      NS      e.root-servers.net. .                      273227  IN      NS      f.root-servers.net. ;; Received 512 bytes from 127.0.0.1#53(127.0.0.1) in 15 ms uk.                    172800  IN      NS      ns1.nic.uk. uk.                    172800  IN      NS      ns4.nic.uk. uk.                    172800  IN      NS      ns2.nic.uk. uk.                    172800  IN      NS      ns5.nic.uk. uk.                    172800  IN      NS      nsc.nic.uk. uk.                    172800  IN      NS      nsa.nic.uk. uk.                    172800  IN      NS      nsd.nic.uk. uk.                    172800  IN      NS      ns6.nic.uk. uk.                    172800  IN      NS      nsb.nic.uk. uk.                    172800  IN      NS      ns7.nic.uk. ;; Received 466 bytes from 192.112.36.4#53(g.root-servers.net) in 47 ms ferryhouse.co.uk.      172800  IN      NS      ns1.naphosting.co.uk. ferryhouse.co.uk.      172800  IN      NS      ns2.naphosting.co.uk. ;; Received 85 bytes from 212.121.40.130#53(ns7.nic.uk) in 46 ms www.ferryhouse.co.uk. ; 300    IN      CNAME  ferryhouse.co.uk. ferryhouse.co.uk.      300    IN      A      77.72.204.33 ferryhouse.co.uk.      300    IN      NS      ns1.turbodns.co.uk. ferryhouse.co.uk.      300    IN      NS      ns2.turbodns.co.uk. ;; Received 113 bytes from 205.234.110.53#53(ns2.naphosting.co.uk) in 93 ms