Some sites load, others don't and show ERR-NAME-RESOLUTION-FAILED

[#1]

I am now up and running using the OpenDNS servers, if you want to do the same (Windows 7+) open 'network and sharing centre' and under connections find 'properties' and locate TCP/IPv6, highlight this and select 'properties'. Now select  the radio button 'use following DNS server addresses' and set the primary DNS address as 208.67.222.222 and the secondary to 208.67.222.220 (or you could set this to 212.159.6.9 (the plusnet server).
You can always change back to 'obtain DNS server automatically' when things are back to normal.
Hope that helps

[#2]

It's not a DNS problem. It seems that some large parts of the network are unreachable. This looks like it includes the area where the DNS servers are. Chaging DNS servers will let you resolve names but you stil won't be able to access a large number of sites until they fix the issue.

[#3]

Using Google's 8.8.8.8 and 8.8.4.4 addresses has certainly improved things here, but not fixed them entirely.
I still can't get to some thing - eg the Lastpass server, Yahoo, Gizmodo, and gov.uk. My wife cannot connect to her company VPN, though email and Lync is working, which doesn't route via the VPN.
Some of these failures don't feel like DNS failures, suggesting there is something more fundamental going on.

[#4]

Quote from: rongtw

Bet the phone lines are HOT  Just goes to prove removal of 24 hr support DONT WORK !!!!!!!!!!!!

How correct you are on that taking away the 24/7 service is a very poor excuse by PlusNet as it has made no difference to call waiting times in fact upon calling as soon as they opened a message of a major service fault ,and a please call again later auto response-- click and then end off line tone....lol

[#5]

Quote from: jaark

It's not a DNS problem. It seems that some large parts of the network are unreachable. This looks like it includes the area where the DNS servers are. Chaging DNS servers will let you resolve names but you stil won't be able to access a large number of sites until they fix the issue.

Hmmm... I'm able to see all the sites I couldn't before I changed to 8.8.8.8
Can you give me an example of an unreachable site and I'll try it from here.

[#6]

Come on PlusNet please, lets have an update[flash=200,200][/flash]

[#7]

Quote from: creamola

It's a DNS issue - PlusNet's DNS servers are borked - but Googles' work fine. 1. Download netsetman from www.netsetman.com (it's free for personal use) 2. In netsetman, select a profile tab and click the twirly button which says "Network adapters list" when you hover over it. Select from the list of adapters it has found, the one you want to configure (probably WiFi) 3. IP and gateway - select "obtain an address automatically" 4. DNS server - tick in the box and select "use the following DNS server addresses". First line 8.8.8.8 and second line 8.8.4.4 5. Click "Activate" top right. This will locally (i.e. on just your PC only) set your DNS to Google. Obviously, reverse this out one Plusnet have fixed the problem.

I have manually set my Netgear router to look at the Google DNS sites - but perhaps you could explain why you say "reverse this out" - why can't it just be left thus? What are the drawbacks?

[#8]

Yes a walk through be very helpful!

[#9]

Quote from: drj

why can't it just be left thus? What are the drawbacks?

None. Nothing to lose, all to gain! http://www.howtogeek.com/167239/7-reasons-to-use-a-third-party-dns-service/

[#10]

mod:note
merged the two largest threads to try and keep all info in one place..

[#11]

Still not working here, annoyed isn't the word. 

[#12]

Quote from: racquel

Quote from: jaark It's not a DNS problem. It seems that some large parts of the network are unreachable. This looks like it includes the area where the DNS servers are. Chaging DNS servers will let you resolve names but you stil won't be able to access a large number of sites until they fix the issue. Hmmm... I'm able to see all the sites I couldn't before I changed to 8.8.8.8 Can you give me an example of an unreachable site and I'll try it from here.

Sure,
bbc.co.uk (212.58.246.103)
slashdot.org (216.34.181.45)
Both reachable from other networks but not Plusnet

[#13]

I can't get on to any of the above links they are all 'webpage not available' and this site is slowing down but that's probably down to number of customers browsing.

[#14]

Quote from: jaark

bbc.co.uk (212.58.246.103) slashdot.org (216.34.181.45) Both reachable from other networks but not Plusnet

Both sites loading fine here with the 8.8.8.8 fix.
Try a reboot?

Tracing route to slashdot.org [216.34.181.45]
over a maximum of 30 hops:
  1     3 ms     3 ms     3 ms  dsldevice.lan [192.168.1.254]
  2   202 ms    41 ms    33 ms  lo0-central10.pcl-ag05.plus.net [195.166.128.186]
  3    33 ms    34 ms    33 ms  link-b-central10.pcl-gw02.plus.net [212.159.2.178]
  4    33 ms    33 ms    32 ms  xe-1-2-0.pcl-cr02.plus.net [212.159.0.210]
  5   223 ms    33 ms    34 ms  195.99.126.98
  6    35 ms    42 ms    33 ms  core3-te0-12-0-20.faraday.ukcore.bt.net [109.159.249.145]
  7    37 ms    35 ms    35 ms  213.121.193.26
  8    35 ms    34 ms    35 ms  transit2-xe3-0-0.ealing.ukcore.bt.net [62.6.200.181]
  9    34 ms    34 ms    35 ms  t2c4-xe-10-1-0-0.uk-eal.eu.bt.net [166.49.168.37]
 10    35 ms    35 ms    33 ms  5-1-2.ear2.London2.Level3.net [212.187.201.153]
 11    98 ms    35 ms   156 ms  ae-22-52.car2.London1.Level3.net [4.69.139.99]
 12    34 ms    33 ms    34 ms  ae-22-52.car2.London1.Level3.net [4.69.139.99]
 13   223 ms   204 ms   206 ms  savvis [4.68.127.34]
 14   208 ms    35 ms   149 ms  cr1-te-0-0-5-0.uk1.savvis.net [204.70.206.61]
 15   124 ms   123 ms   124 ms  cr1-te-0-1-0-0.chd.savvis.net [206.28.100.229]
 16   124 ms   124 ms   123 ms  hr3-xe-8-0-0.elkgrovech3.savvis.net [204.70.198.73]
 17   339 ms   126 ms   132 ms  das5-v3030.ch3.savvis.net [64.37.207.150]
 18   131 ms   123 ms   160 ms  64.27.160.194
 19   493 ms     *      386 ms  slashdot.org [216.34.181.45]

[#15]

Same here, wifi devices timing out, wired is extremely slow/failing totally.