cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to resolve DNS and 400+ms ping time

floods
Dabbler
Posts: 22
Thanks: 2
Registered: ‎17-09-2017

Re: Unable to resolve DNS and 400+ms ping time

I checked early this morning, the network should not be busy at this time....surprisingly slow

C:\Users\Sean>time /T
06:10

C:\Users\Sean>tracert ntp.plus.net

Tracing route to ntp.plus.net [212.159.13.50]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * 25 ms cdns02.plus.net [212.159.13.50]

Trace complete.

C:\Users\Sean>nslookup bbc.co.uk
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 212.159.6.9

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out

C:\Users\Sean>

floods
Dabbler
Posts: 22
Thanks: 2
Registered: ‎17-09-2017

Re: Unable to resolve DNS and 400+ms ping time

Hi Bob,

These tests have been run from a desk top computer over a wired connection to the JL router. Netflix and Amazon are on a smart TV behind my other router on a wired connection, we have found that they cannot load Amazon, and yes I understand that my router could still have an impact, but my desktop (Zak1) is having problems loading pages (these community pages, gmail, amazon, BBC), all the results I have pasted have been from Zak1. 

Here is the ipconfig /all results......

C:\Users\Sean>time /T
06:18

C:\Users\Sean>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Zak1
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller
Physical Address. . . . . . . . . : 00-1B-FC-5D-1E-6F
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::bccb:a8a5:bd78:4fe5%5(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.4(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 28 September 2017 17:32:15
Lease Expires . . . . . . . . . . : 30 September 2017 05:32:16
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 301997052
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-20-F7-01-67-00-1B-FC-5D-1E-6F
DNS Servers . . . . . . . . . . . : 212.159.6.9
212.159.6.10
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Ethernet 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Generic Marvell Yukon 88E8055 PCI-E Gigabit Ethernet Controller
Physical Address. . . . . . . . . : 00-00-00-00-00-00
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:242a:2858:3f57:fefb(Preferred)
Link-local IPv6 Address . . . . . : fe80::242a:2858:3f57:fefb%2(Preferred)
Default Gateway . . . . . . . . . : ::
DHCPv6 IAID . . . . . . . . . . . : 201326592
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-20-F7-01-67-00-1B-FC-5D-1E-6F
NetBIOS over Tcpip. . . . . . . . : Disabled

C:\Users\Sean>

 

Here is a another test without my netgear router attached(see attachment), wired connection to Zak1 and wifi disabled.....

C:\Users\Sean>time /T
06:39

C:\Users\Sean>tracert ntp.plus.net

Tracing route to ntp.plus.net [212.159.13.50]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * 1332 ms 25 ms cdns02.plus.net [212.159.13.50]

Trace complete.

C:\Users\Sean>nslookup bbc.co.uk
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 212.159.6.9

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
Non-authoritative answer:
Name: bbc.co.uk
Addresses: 2001:41c1:400c::bbc:2
2001:41c1:400c::bbc:1
2001:41c1:400c::bbc:3
2001:41c1:4008::bbc:2
2001:41c1:4008::bbc:1
2001:41c1:400c::bbc:4
2001:41c1:4008::bbc:3
2001:41c1:4008::bbc:4
212.58.244.23
212.58.246.79
212.58.244.22
212.58.246.78


C:\Users\Sean>

adamwalker
Plusnet Help Team
Plusnet Help Team
Posts: 16,878
Thanks: 882
Fixes: 221
Registered: ‎27-04-2007

Re: Unable to resolve DNS and 400+ms ping time

Hi there, I just wanted to make sure you've seen our latest response to ticket 157505178

If this post resolved your issue please click the 'This fixed my problem' button
 Adam Walker
 Plusnet Help Team
floods
Dabbler
Posts: 22
Thanks: 2
Registered: ‎17-09-2017

Re: Unable to resolve DNS and 400+ms ping time

C:\Users\Sean>time /T
16:48

C:\Users\Sean>tracert ntp.plus.net

Tracing route to ntp.plus.net [212.159.6.9]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 * * * Request timed out.
4 25 ms 26 ms 26 ms be3-3104.psb-ir01.plus.net [195.166.143.136]
5 * * * Request timed out.
6 1672 ms 25 ms 26 ms cdns01.plus.net [212.159.6.9]

Trace complete.

C:\Users\Sean>NSlookup bbc.co.uk
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 212.159.6.9

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out

C:\Users\Sean>

bobpullen
Community Gaffer
Community Gaffer
Posts: 16,889
Thanks: 4,983
Fixes: 316
Registered: ‎04-04-2007

Re: Unable to resolve DNS and 400+ms ping time

Message 31 doesn't show any slow down at all. Yes, the non responsive hops are unusual, and the nslookup failure doesn't look right, but the trace shows an end to end response time of 25ms which is good.
Looking at the ipconfig output, I'd suggest you try disabling IPv6 on both the router interface and the PC. For the PC, go to the network connection properties and untick IPv6. Can easily be re-enabled if there's no change.
I can't put my finger on it, but something doesn't strike me as right, and I'm not 100% convinced it's this side of the Zyxel.
I'm almost tempted to send you an Openreach VDSL modem that you can try hooking up to the Netgear, but you can achieve similar by putting the Zyxel into bridge mode.

Bob Pullen
Plusnet Product Team
If I've been helpful then please give thanks ⤵

Strat
Community Veteran
Posts: 31,320
Thanks: 1,609
Fixes: 565
Registered: ‎14-04-2007

Re: Unable to resolve DNS and 400+ms ping time

Moderator Note by Dick (Strat)

Duplicate post removed.

Windows 10 Firefox 109.0 (64-bit)
To argue with someone who has renounced the use of reason is like administering medicine to the dead - Thomas Paine