Unable to reach just one single URL....

[#1]

All,
I'm trying to access www.labrador-rescue.org.uk but cannot.
Sounds simple right, but its flexing my small brain today. I cannot access it from my personal laptop using Chrome or IE. I cannot access it from my partners Dell running Chrome and IE. I cannot access it from the Samsung Tablet using IE or Mozilla (I think it is). I cannot access it from my HTC Android phone handset either. I've disabled Norton on all my laptop, my phone doesn't have AV on it, the Dell uses AVG and the tablet is free of AV also.
However, I can access it from my phone if I swap to the providers data provision rather than wifi.
I had zero firewall config on my router, I've reset it more than once (having some speed issues as well) and have tried wired / wifi combinations with no luck. I know that the site is available as I can get family members on different ISPs to ctrl-f5 it and check the update dates on web pages. The site admins even confirmed it was up on their facebook wall.
This is the only address I've found that does this and it was working happily until very recently (c 1 - 2 weeks).
Any ideas ? Anyone else having strange experiences with the Plusnet DNS settings ?
Suggestions welcomed...
M
{edit} Forgot to add, cannot ping it from any pc device either {/edit}

[#2]

What happens if you run a tracert to it ?

Tracing route to labrador-rescue.org.uk [109.123.121.187]
over a maximum of 30 hops:
  1     2 ms     1 ms     7 ms  dsldevice.lan [192.168.1.1] 
  2    19 ms    22 ms    18 ms  lo0-central10.pcl-ag07.plus.net [195.166.128.188] 
  3    11 ms    11 ms    11 ms  link-b-central10.pcl-gw02.plus.net [212.159.2.186] 
  4    11 ms    11 ms    11 ms  xe-9-0-0.pcl-cr02.plus.net [212.159.0.218] 
  5    29 ms    17 ms    10 ms  ae1.ptw-cr02.plus.net [195.166.129.2] 
  6    12 ms    11 ms    12 ms  linx-226.as13213.net [195.66.236.19] 
  7    11 ms    11 ms    14 ms  83.170.70.238 
  8    17 ms   101 ms    13 ms  dc5.as13213.net [83.170.70.138] 
  9    13 ms    11 ms    12 ms  vinyamar.nevrast.org [109.123.121.187] 
Trace complete.

[#3]

"Unable to resolve target system name www.labrador.rescue.org.uk"
If I tracert the ip address you gave, which goes to a transcript fro the picture of Dorian Grey, I get the almost exact same response. Except it looks like you are using a different DNS setting to me. I'm getting 197 not 188.
I can resolve both ways on the example you gave, from url and ip address via Chrome / IE.
I was thinking DNS settings somewhere - but not sure if on a Plusnet box or my own (somehow).

[#4]

I'm using Google DNS servers (8.8.8.8 ) and open-dns DNS servers
Are you trying to resolve labrador.rescue or labrador-rescue ?

[#5]

Also try editing your hosts file ( c:\windows\system32\drivers\etc\hosts ) with the entry 109.123.121.187 www.labrador-rescue.co.uk this will be read first when you type in the URL and should take you to the labrador rescue page.
The easy way to do it in Windows 7/8 is to run CMD as administrator then cd \windows\system32\drivers\etc and type in "notepad hosts"

[#6]

So I've done that. No difference. However, I've got this problem across all devices on this network, so I'm not sure its a local file issue.

[#7]

Have you tried manually adding the Google / Open DNS servers in your network settings on one PC ?
Sometimes you need to restart your browser after editing the hosts file. The hosts file solution was just a temporary test by the way.

[#8]

One point to be aware of - I'm not trying to access www.labrador-rescue.co.uk . I am after labrador-rescue.org.uk . I can resolve to co.uk without any problems.
Will go look at the Open DNS options....

[#9]

Oops - my tracert was correct but you'd need to adapt my hosts suggestion for the .org.uk bit.
Let us know how you get on with the DNS - it could just be a screwy DNS entry at Plusnets DNS servers (hence the suggestion to try google / opendns which I use)

[#10]

Google DNS didn't do anything. Decided to give it a bang on the OpenDNS. Managed to get a ping and then a connect from Chrome + IE.
As I suspect, a screwy DNS entry at Plusnet probably.
Thanks for your help / support - I'd been going a bit in circles since normally DNS servers are pretty reliable...

[#11]

I can't access it via googles dns either, a nslookup fails on it.

[#12]

I thought I could but checking I have Google as my primary and OpenDNS as secondary so no problem was seen

[#13]

$ nslookup www.labrador-rescue.org.uk 8.8.8.8
Server: 8.8.8.8
Address: 8.8.8.8#53
** server can't find www.labrador-rescue.org.uk: NXDOMAIN
$ nslookup www.labrador-rescue.org.uk 208.67.222.222
Server: 208.67.222.222
Address: 208.67.222.222#53
Non-authoritative answer:
www.labrador-rescue.org.uk canonical name = labrador-rescue.org.uk.
Name: labrador-rescue.org.uk
Address: 109.123.121.187

[#14]

hairybiker@Duo:~$ nslookup
> server
Default server: 127.0.1.1
Address: 127.0.1.1#53
> server 8.8.8.8
Default server: 8.8.8.8
Address: 8.8.8.8#53
> www.labrador-rescue.org.uk
Server:		8.8.8.8
Address:	8.8.8.8#53
** server can't find www.labrador-rescue.org.uk: NXDOMAIN
> server 208.67.222.222                        
Default server: 208.67.222.222
Address: 208.67.222.222#53
> www.labrador-rescue.org.uk
Server:		208.67.222.222
Address:	208.67.222.222#53
Non-authoritative answer:
www.labrador-rescue.org.uk	canonical name = labrador-rescue.org.uk.
Name:	labrador-rescue.org.uk
Address: 109.123.121.187
> 

So googles dns fails to find it.
EDIT You just beat me to it.

[#15]

t:~$ dig www.labrador-rescue.org.uk @8.8.8.8
; <<>> DiG 9.9.5 <<>> www.labrador-rescue.org.uk @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 56754

Quote

SERVFAIL means that the domain does exist and the root name servers have information on this domain, but that the authoritative name servers are not answering queries for this domain.

I suspect Google has attempted to access ns3.labrador-rescue.org.uk over IPv6, (which is currently not responding to ping), failed to reach the server and has cached the fail and is now returning the above "This domain is broken" error.