Asus RT-N65U Questions

Toggle sidebar Toggle sidebar
fastoy

fastoy

Distinguished
Sep 8, 2010
24
0
18,510
I have an ASUS RT-N65U with firmware version 3.0.0.4.374.1317. I know there's a new firmware available but that was current when I implemented it.

DNS lookups were failing with router.asus.com not responding. If I tested with nslookup it also failed. If I ran nslookup with 8.8.8.8 it worked. router.asus.com worked again after I power cycled the router.

On the LAN / DHCP-Server page, I changed the DNS Server to 8.8.8.8. That causes the DHCP server to give a client DNS servers of 8.8.8.8 and 192.168.1.1. How can I specify to give a client DNS servers of 8.8.8.8 and 8.8.4.4?

Or is there a better idea than what I did?
 
Sort by date Sort by votes
D

dizzyh

Distinguished
Apr 11, 2013
181
0
18,760
Click on the WAN settings of the router , go under WAN dns setting. Where it says connect to dns server automatically, click no. And input 8.8.8.8 in the first box and 8.8.4.4 in the second. Remove the changes you made on the LAN side
 
Upvote 0 Downvote
fastoy

fastoy

Distinguished
Sep 8, 2010
24
0
18,510

Won't that put the router back to handing out router.asus.com as a DNS server to the LAN? Whatever process in the router than services router.asus.com is what seems to be failing. For example right now I am still in the configuration I described. When I do "nslookup google.com router.asus.com" it times out. "nslookup google.com" and "nslookup google.com 172.17.2.1" both work.
 
Upvote 0 Downvote
B

bill001g

Titan
Aug 9, 2012
28,323
2,755
125,640
If you set it manually in the PC it will completely ignore any DNS information from the DHCP server.

You can't put a DNS name in for the DNS server itself. It now must use a DNS server to find the DNS server. Then again this may some of strangeness that violates standards that router manufacture do.

If you go back to when you configured your router with 8.8.8.8 This router does not support multiple DNS server so it give you the secondary as router itself. You could put 8.8.8.4 into the router as its dns server. DNS only uses the primary dns it will not even attempt to try the second one if the first will talk to it. If the first tell the pc a site is unkown it will not try the second. It will only try the second one if the first one does not answer at all. What would happen in your case if the 8.8.8.8 fails it will ask the router which is pretending to be a DNS server. It is highly unlikely 8.8.8.8 would ever fail. Even if a single server goes down there are many many of these 8.8.8.8 servers in the world.
 
Upvote 0 Downvote
fastoy

fastoy

Distinguished
Sep 8, 2010
24
0
18,510

I'd rather not have to change the DNS setting on every PC/device on my network. I realize that I misspoke when I said that the router was "handing out router.asus.com as a DNS server to the LAN." Clearly it was handing out its own address as DNS. However this reversed to router.asus.com. (I realize that I may be getting some of these technical terms wrong.)

I agree that it is "highly unlikely 8.8.8.8 would ever fail" but it actually has. I guess in the end 8.8.8.8 is way more dependable that the internal process in the router. I think I'm going to leave it as it is as it's working for now.

Thanks to everyone for weighing in here.
 
Upvote 0 Downvote
fastoy

fastoy

Distinguished
Sep 8, 2010
24
0
18,510
Just FYI, I upgraded from 3.0.0.4.372_1363 to 3.0.0.4.374_1317 today and left my DNS configured as described in my original post. After about 12 hours I ran the following commands:

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

Non-authoritative answer:
Name: monoprice.com
Address: 204.74.99.100

C:\Users\Ben Moore>nslookup monoprice 192.168.1.1
Server: router.asus.com
Address: 192.168.1.1

*** router.asus.com can't find monoprice: Non-existent domain

C:\Users\Ben Moore>nslookup monoprice.com 8.8.4.4
Server: google-public-dns-b.google.com
Address: 8.8.4.4

Non-authoritative answer:
Name: monoprice.com
Address: 204.74.99.100

You can see that 192.168.1.1 calls itself router.asus.com and fails when looking up monoprice.com. 8.8.8.8 and 8.8.4.4 both successfully lookup monoprice.com.

Whatever widget/daemon/service that is instantiated by the router as the DNS service at 192.168.1.1 (calling itself router.asus.com) has failed.
 
Upvote 0 Downvote
B

bill001g

Titan
Aug 9, 2012
28,323
2,755
125,640
On the router itself what do you have the DNS set for. Are you using the ISP dns (this is default config) or are you also having the router use 8.8.4.4

When you ask 192.168.1.1 all it really is doing is forwarding the request to whatever DNS is configured on the router (normally on the wan port). If you are using 8.8.4.4 then the router has some strange issue since all it is suppose to do is forward your request to that configured actual DNS. If you are using the ISP for your DNS service then that is your issue. Many ISP are not the brightest when it comes to setting up a DNS.
 
Upvote 0 Downvote
fastoy

fastoy

Distinguished
Sep 8, 2010
24
0
18,510

You've got a good eye! That worked.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Ben Moore>nslookup monoprice.com 192.168.1.1
Server: router.asus.com
Address: 192.168.1.1

Non-authoritative answer:
Name: monoprice.com
Address: 204.74.99.100


On http://192.168.1.1/Advanced_WAN_Content.asp I have "Connect to DNS Server automatically" set to "Yes."

On http://192.168.1.1/Advanced_DHCP_Content.asp I have "DNS Server" set to 8.8.8.8.

I agree with "When you ask 192.168.1.1 all it really is doing is forwarding the request to whatever DNS is configured on the router (normally on the wan port)." My perception was that the router (via 192.168.1.1) was failing to forward the request.

I have not observed this since 3.0.0.4.374_1317. The change log (http://support.asus.com/download.aspx?SLanguage=en&m=RT-N65U) references some DHCP changes - "Fixed HK ISP DHCP connection issue.". Perhaps this has now been fixed.
 
Upvote 0 Downvote
fastoy

fastoy

Distinguished
Sep 8, 2010
24
0
18,510
Ok. Now my son-in-law has gone and gotten an Asus RT-AC68U which is demonstrating the same problem. He's had it installed less than a week and has flashed it to the latest firmware (sorry but I'm not there to get the level). They have observed it "not getting on the Internet" a couple of times. Power cycling it remedies that.

When I was over there yesterday I was getting the same problem. Here's what I got from nslookup:

C:\Users\John>nslookup ipaper.com
Server: router.asus.com
Address: 172.17.2.1

*** router.asus.com can't find ipaper.com: Query refused

C:\Users\John>nslookup ipaper.com 172.17.2.1
Server: router.asus.com
Address: 172.17.2.1

*** router.asus.com can't find ipaper.com: Query refused

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

Non-authoritative answer:
Name: ipaper.com
Address: 141.129.200.199

Then I made the same changes to his router that I made to mine. On the LAN / DHCP-Server page, I changed the DNS Server to 8.8.8.8. That causes the DHCP server to give a client DNS servers of 8.8.8.8 and 172.17.2.1.

Immediately after that I got the following from nslookup:

C:\Users\John>nslookup ipaper.com
Server: router.asus.com
Address: 172.17.2.1

Non-authoritative answer:
Name: ipaper.com
Address: 141.129.200.199


C:\Users\John>nslookup ipaper.com 172.17.2.1
Server: router.asus.com
Address: 172.17.2.1

Non-authoritative answer:
Name: ipaper.com
Address: 141.129.200.199


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

Non-authoritative answer:
Name: ipaper.com
Address: 141.129.200.199

I need to make a small confession here. My LAN network address is 172.17.2.1 as is his. I replaced "172.17.2" with "192.168.1" in the previous posts so as to not introduce another question/tangent. But now I'm wondering if the problem is related to the unusual network address?
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom