Intermittent DNS name resolution issues with non Plusnet DNS servers

[#1]

Hi All,

I have a strange issue whereby any DNS server but plusnets own seem to work intermittently. Almost as if there are DNS (UDP 53) filters or proxies breaking somewhere in plusnets network.

If I use plusnets DNS servers ( 212.159.13.49 ) name resolution works fine all the time, again showing that the issue is for DNS lookups outside of the plusnet network. 

For example if I query googles DNS with nslookup:

nslookup www.google.co.uk 8.8.8.8

The query Intermittently fails, where as the same query to plushest primary server works all the time:

nslookup www.google.co.uk 212.159.13.49

This is true of all the other non plusnet DNS servers I have tried (open DNS / uunet )  

I am using plusnets VDSL service and I have no other connectivity or performance issues, only this issue with non plus net DNS hosts.

I raise the issue on a web chat with plusnets support team but i'm not sure they are looking into this.

Has anyone else seen this issue?

regards

Rich

[#2]

I've been using OpenDNS since Plusnet Fibre was installed in Aug 2014.

Been working fine since, no problems.

Also the nslookup is working here.

C:\Users\Henri>nslookup google.com 8.8.8.8
Server:  google-public-dns-a.google.com
Address:  8.8.8.8

Non-authoritative answer:
Name:    google.com
Addresses:  2a00:1450:4009:811::200e
          216.58.213.174

And here with PN

C:\Users\Henri>nslookup www.google.co.uk 212.159.13.49
Server:  cdns01.plus.net
Address:  212.159.13.49

Non-authoritative answer:
Name:    www.google.co.uk
Addresses:  2a00:1450:4009:810::2003
          216.58.208.163  

OpenDNS

C:\Users\Henri>nslookup www.google.co.uk 208.67.220.220
Server:  resolver2.opendns.com
Address:  208.67.220.220

Non-authoritative answer:
Name:    www.google.co.uk
Addresses:  2a00:1450:4009:80f::2003
          216.58.213.99


C:\Users\Henri>nslookup www.google.co.uk 208.67.222.222
Server:  resolver1.opendns.com
Address:  208.67.222.222

Non-authoritative answer:
Name:    www.google.co.uk
Addresses:  2a00:1450:4009:80f::2003
          216.58.198.99

[#3]

Yep, this is also affecting me. Exactly as described.

I'm also seeing stalling on incoming TCP connections (e.g. SSH). 

I've got a ticket open to this effect (#129215255).

[#4]

Hi Riza,

Many thanks for replying, I probably should clarify that I see the error on the lookups randomly. Sometimes I do get 2 or 3 responses before a failure. 

Is there any chance you could run the google test again say 8 or 9 times in a row ? - from my testing this is sure to demonstrate the issue.

Of course it may be that it's only a part of the plus net network that has the issue.

Thanks agin for replying.

Regards

Rich

[#5]

jtjacques,

Thanks for the reply. When I get a moment I'll test an inbound connect as well. 

Is there anyway to track the ticket you have open from the web portal ? - I can't even seem to find a contact centre number to raise an issue ...

Rich

[#6]

I'm tracking my ticket from the "view my questions" section of the "member centre"; though I don't think there is a way to see others.

 -- https://www.plus.net/wizard/?p=search

I opened my ticket using http://faults.plus.net but had to go through a bunch of "have you turned it off and on again" type questions. I added my issue in the "extra information" bit at the end of the wizard. Now the ticket is open I've updated it with a bunch of extra information (after confirming that I have indeed tried the BT test socket, again!).

Hoping to hear back from someone with the requisite insight in to the network.

[#7]

From https://www.plus.net/home-broadband/contact/

Customer support

---

• 0800 432 0200 (from within the UK)

7.30am - 10pm, every day Please have your username and password handy.

 And the button in my signature is a link to Find Your Own Support Tickets 

[#8]

I believe this is linked with https://community.plus.net/t5/Fibre-Broadband/DNS-Routing-issues-for-the-last-36-hours/m-p/1348651/h...

Also happening for me when pinging that IP that timeouts. 

You're not alone on this one, a network problem with Plusnet 

[#9]

Just wanted to offer an update to say that after calling support and explaining that this was not a line issue and I did not need an OpenReach visit, I was moved to a different IP range (from 51.6.x.x to 80.229.x.x). My issue was immediately resolved and I confirmed this with the agent on the phone.

[#10]

I have been experiencing what seems like the same as above.

Had problems uploading over past several days and from last night been getting DNS_PROBE_FINISHED_BAD_CONFIG and either unable to view any web pages, or only certain ones and not others.