TP-Link websites & P/N DNS Servers
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Plusnet Community
- :
- Forum
- :
- Help with my Plusnet services
- :
- Broadband
- :
- Re: TP-Link websites & P/N DNS Servers
TP-Link websites & P/N DNS Servers
06-07-2014 8:37 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
After a bit of fiddling it seems Plusnet's default DNS servers are the problem. I set my ethernet adaptor to use Google DNS & I can now access all the TP-Link sites ok including the UK one.
Is there any reason why Plusnet's DNS servers are blocking these sites?
Re: TP-Link websites & P/N DNS Servers
06-07-2014 9:16 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
I think it's the DNS servers for tp-link.com (ns15.xincache.com and ns16.xincache.com) that are down or having problems, or connectivity to or from those to plusnet - while I was typing this, they worked again for a moment.
Nothing is being deliberately blocked, it's just that other DNS servers may cache positive responses for longer.
Re: TP-Link websites & P/N DNS Servers
06-07-2014 9:21 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
The only UK URL I've found is uk.tp-link.com, it resolves ok here with PN's dns.
Re: TP-Link websites & P/N DNS Servers
06-07-2014 9:31 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Strange the US site worked ok.
adie:quote
Re: TP-Link websites & P/N DNS Servers
06-07-2014 9:35 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Here dig does not resolve uk.tp-link.com using Plusnet resolvers.
Resolves ok using opendns, google dns, level3 dns and the root servers.
Looks like a PN issue from here.
Re: TP-Link websites & P/N DNS Servers
06-07-2014 9:39 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Wonder if the P/N team will pick this up tomorrow.
Re: TP-Link websites & P/N DNS Servers
06-07-2014 9:56 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Trouble is, if you repeat the same query 20 or so times in quick secession, even Plusnet's DNS servers will manage to remember the answer for a little while.
Re: TP-Link websites & P/N DNS Servers
07-07-2014 10:44 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
There's been sufficient time for it to expire from the various dns caches so it's not being served from a old google dns cache entry.
Dig +trace is still being intermittent in finding the name, so perhaps there's a plusnet routing issue to xincache.net.
Quote ; <<>> DiG 9.8.6-P1 <<>> uk.tp-link.com +trace
;; global options: +cmd
. 441028 IN NS a.root-servers.net.
. 441028 IN NS b.root-servers.net.
. 441028 IN NS c.root-servers.net.
. 441028 IN NS d.root-servers.net.
. 441028 IN NS e.root-servers.net.
. 441028 IN NS f.root-servers.net.
. 441028 IN NS g.root-servers.net.
. 441028 IN NS h.root-servers.net.
. 441028 IN NS i.root-servers.net.
. 441028 IN NS j.root-servers.net.
. 441028 IN NS k.root-servers.net.
. 441028 IN NS l.root-servers.net.
. 441028 IN NS m.root-servers.net.
;; Received 508 bytes from 192.168.1.10#53(192.168.1.10) in 15 ms
com. 172800 IN NS a.gtld-servers.net.
com. 172800 IN NS b.gtld-servers.net.
com. 172800 IN NS c.gtld-servers.net.
com. 172800 IN NS d.gtld-servers.net.
com. 172800 IN NS e.gtld-servers.net.
com. 172800 IN NS f.gtld-servers.net.
com. 172800 IN NS g.gtld-servers.net.
com. 172800 IN NS h.gtld-servers.net.
com. 172800 IN NS i.gtld-servers.net.
com. 172800 IN NS j.gtld-servers.net.
com. 172800 IN NS k.gtld-servers.net.
com. 172800 IN NS l.gtld-servers.net.
com. 172800 IN NS m.gtld-servers.net.
;; Received 492 bytes from 199.7.83.42#53(l.root-servers.net) in 46 ms
tp-link.com. 172800 IN NS ns15.xincache.com.
tp-link.com. 172800 IN NS ns16.xincache.com.
;; Received 111 bytes from 192.12.94.30#53(e.gtld-servers.net) in 76 ms
;; connection timed out; no servers could be reached
Re: TP-Link websites & P/N DNS Servers
07-07-2014 11:20 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Re: TP-Link websites & P/N DNS Servers
08-07-2014 6:17 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
; <<>> DiG 9.9.4-P2-RedHat-9.9.4-12.P2.fc20 <<>> @212.159.13.49 uk.tp-link.com +tries=1
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;uk.tp-link.com. IN A
;; ANSWER SECTION:
uk.tp-link.com. 2695 IN A 91.250.77.30
;; Query time: 23 msec
;; SERVER: 212.159.13.49#53(212.159.13.49)
;; WHEN: Tue Jul 08 06:03:57 BST 2014
;; MSG SIZE rcvd: 59
After many repeated queries, 212.159.13.49 now knows the IP address.
; <<>> DiG 9.9.4-P2-RedHat-9.9.4-12.P2.fc20 <<>> @212.159.13.50 uk.tp-link.com +tries=1
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 45766
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;uk.tp-link.com. IN A
;; Query time: 22 msec
;; SERVER: 212.159.13.50#53(212.159.13.50)
;; WHEN: Tue Jul 08 06:05:27 BST 2014
;; MSG SIZE rcvd: 43
However 212.159.13.50 was not so lucky and never managed to get the IP address, and now just serves up SERVFAIL in 22ms - it can't possibly have tried ns15.xincache.com or ns16.xincache.com in less than 22ms.
I also just saw occasional SERVFAIL replies from 4.2.2.1 and 208.67.220.220 for uk.tp-link.com - but it seems these servers don't stick with the SERVFAIL answer for so long - retry a couple of times and they'll return the IP address.
Re: TP-Link websites & P/N DNS Servers
11-07-2014 6:42 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Re: TP-Link websites & P/N DNS Servers
11-07-2014 7:06 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Quote ; <<>> DiG 9.8.6-P1 <<>> @212.159.13.49 uk.tp-link.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6684
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;uk.tp-link.com. IN A
;; ANSWER SECTION:
uk.tp-link.com. 1619 IN A 91.250.77.30
;; Query time: 31 msec
;; SERVER: 212.159.13.49#53(212.159.13.49)
;; WHEN: Fri Jul 11 18:46:46 GMT Summer Time 2014
;; MSG SIZE rcvd: 48
Quote ; <<>> DiG 9.8.6-P1 <<>> @212.159.13.50 uk.tp-link.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 26850
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;uk.tp-link.com. IN A
;; Query time: 31 msec
;; SERVER: 212.159.13.50#53(212.159.13.50)
;; WHEN: Fri Jul 11 18:47:16 GMT Summer Time 2014
;; MSG SIZE rcvd: 32
The problem is still there.
Plusnets response is deafening.
Gateway: ptw-ag01
Re: TP-Link websites & P/N DNS Servers
11-07-2014 7:48 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Earlier this evening I was on pcl-ag06 and the PCL plusnet DNS servers were resolving tp-link.com domains, but shortly later my line dropped and I'm now on ptn-ag02, and the PTN DNS servers tend to return the SERVFAIL responses. At the time this thread started, I was on ptw-ag04.
Re: TP-Link websites & P/N DNS Servers
13-07-2014 5:49 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Re: TP-Link websites & P/N DNS Servers
15-07-2014 11:41 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Quote from: ejs I think it's the DNS servers for tp-link.com (ns15.xincache.com and ns16.xincache.com) that are down or having problems...
I'd be inclined to agree. Their auth servers take an awfully long time to reply:
~$ dig tp-link.com @ns15.xincache.com
; <<>> DiG 9.3.4-P1.2 <<>> tp-link.com @ns15.xincache.com
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33291
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;tp-link.com. IN A
;; ANSWER SECTION:
tp-link.com. 3600 IN A 50.62.149.47
;; Query time: 533 msec
;; SERVER: 125.78.242.30#53(125.78.242.30)
;; WHEN: Tue Jul 15 11:37:32 2014
;; MSG SIZE rcvd: 45
And often do this:
~$ dig tp-link.com @ns15.xincache.com
; <<>> DiG 9.3.4-P1.2 <<>> tp-link.com @ns15.xincache.com
; (1 server found)
;; global options: printcmd
;; connection timed out; no servers could be reached
The TTL on the domain is an hour so in the event of a successful lookup, things will appear OK for a while. It's hit and miss whether or not you get a reply though. AIUI, if there's no reply, we'll fail the domain for 15 minutes.
We did have an internal problem raised to look into this (ref: 82031) however it was determined that whatever was causing the issue was outside of our network.
Bob Pullen
Plusnet Product Team
If I've been helpful then please give thanks ⤵
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Plusnet Community
- :
- Forum
- :
- Help with my Plusnet services
- :
- Broadband
- :
- Re: TP-Link websites & P/N DNS Servers