DNS timeouts

[mairuay]

I use merlin 374.42_2 in my AC68U. I recognized that some websites take long to initially load for some time now. This weekend i found out that i get alot of random DNS timeouts on my win81 system. So, i tested with different DNS Servers form different providers and I also tested different static DNS servers on the router, static DNS Servers to give to the DHCP clients. I updated to the lateset merlin version, rebooted the router several times. I disabled all features in the router and so on... but nothing really helped. The only thing that helps is connecting my Win81 to the internet thru my phone with tethering.
Is there any known issue with DNS?

 

[sfx2000]

have you tried flushing the DNS cache on the Win81 box?

on the command line...

ipconfig /flushdns

 

[RMerlin]

Make sure your computers aren't trying to use an IPv6 DNS.

 

[mairuay]

Make sure your computers aren't trying to use an IPv6 DNS.

I disabled IPv6 on the interface. No Luck.
"ipconfig /flushdns" did not help as well

I can run the nslookup command on the routers cmdline without any timeouts.
Ill try with a cable.

 

[RMerlin]

I disabled IPv6 on the interface. No Luck.
"ipconfig /flushdns" did not help as well

I can run the nslookup command on the routers cmdline without any timeouts.
Ill try with a cable.

Make sure your computer doesn't contain some old invalid DNS. I've see that happen in the past - Windows bug. It can also happen if you have a VPN tunnel configured on the computer, with its own DNS.

ipconfig /all

Check all reported DNS IPs for all interfaces.

 

[mairuay]

i don't think its my computer. nslookups run well when i use my mobiles tethering to connect to the internet.

C:\>ipconfig /all

Windows IP Configuration

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

Wireless LAN adapter Local Area Connection* 11:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
   Physical Address. . . . . . . . . : AE...
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wi-Fi 2:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : ASUS PCE-AC68 802.11ac Network Adapter
   Physical Address. . . . . . . . . : AC...
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::.....(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.253(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Sunday, 1. June 2014 23:27:04
   Lease Expires . . . . . . . . . . : Monday, 2. June 2014 23:27:04
   Default Gateway . . . . . . . . . : 192.168.1.1
   DHCP Server . . . . . . . . . . . : 192.168.1.1
   DHCPv6 IAID . . . . . . . . . . . : 481042955
   DHCPv6 Client DUID. . . . . . . . : 00...

   DNS Servers . . . . . . . . . . . : 192.168.1.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter VMware Network Adapter VMnet1:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMne
1
   Physical Address. . . . . . . . . : 00-52-65-E0-00-11
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.127.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter VMware Network Adapter VMnet8:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMne
8
   Physical Address. . . . . . . . . : 00-51-55-B0-10-18
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.59.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Teredo Tunneling Pseudo-Interface:

   Media State . . . . . . . . . . . : Media disconnected
   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

Tunnel adapter isatap.{B591C947-522B-485B-8FE7-8D64237C712E}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{4CB7BA3F-869F-4EF0-A238-FF4CF6876651}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{6C237CE1-C772-4E81-A915-31F53F03B1ED}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #4
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

 

[MikeInNJ]

I haven't done a lot of testing but I think I may be seeing something like this as well. AC66U with .42.

 

[seth_space]

There are several options to set your DNS.
I see you have the Router as redirect set tot an external DNS
Client>>192.168.1.1 >>> extDNS>>

You could put in the opendns servers in your client dhcp settings (LAN) so they receive the DNS via the DHCP option.

I.E: The OpenDNS nameservers are 208.67.222.222 and 208.67.220.220.

 

[lancer73]

Did you check the iptables settings on the router?

On the router command line:
iptables -t nat -L -v

You can influence the behavior of DNS (and the related iptables settings) using the parental controls

 

[mairuay]

resetted to factory. everything fine now.