Daniel
Premium,MVM
join:2000-06-26
Pleasanton, CA
clubs: 
|  reply to kosiac
DNS and Netgear...
Hmm.
Here are the results against my RT314:
-------
> server
Default server: 192.168.0.1
Address: 192.168.0.1#53
> set q=mx
> microsoft.com
Server: 192.168.0.1
Address: 192.168.1.1#53
Non-authoritative answer:
microsoft.com mail exchanger = 10 mailc.microsoft.com.
microsoft.com mail exchanger = 10 maila.microsoft.com.
microsoft.com mail exchanger = 10 mailb.microsoft.com.
Authoritative answers can be found from:
microsoft.com nameserver = DNS1.CP.MSFT.NET.
microsoft.com nameserver = DNS1.DC.MSFT.NET.
microsoft.com nameserver = DNS1.SJ.MSFT.NET.
microsoft.com nameserver = DNS1.TK.MSFT.NET.
microsoft.com nameserver = DNS3.JP.MSFT.NET.
microsoft.com nameserver = DNS3.UK.MSFT.NET.
mailc.microsoft.com internet address = 131.107.3.126
mailc.microsoft.com internet address = 131.107.3.121
maila.microsoft.com internet address = 131.107.3.124
maila.microsoft.com internet address = 131.107.3.125
mailb.microsoft.com internet address = 131.107.3.122
mailb.microsoft.com internet address = 131.107.3.123
DNS1.CP.MSFT.NET internet address = 207.46.138.20
DNS1.DC.MSFT.NET internet address = 207.68.128.151
DNS1.SJ.MSFT.NET internet address = 65.54.248.222
DNS1.TK.MSFT.NET internet address = 207.46.232.37
DNS3.JP.MSFT.NET internet address = 207.46.72.123
DNS3.UK.MSFT.NET internet address = 213.199.144.151
>
--------
I think your use of the virtual circuit nslookup command is your problem when it comes to the manual queries because mine fail as well using an internal or external server if I use it.
As for your queries in general, there should be no difference between using your router or using your router's configured DNS server directly. The thing to remember is that you are never asking your router for anything; it doesn't have any DNS info of its own. You are making all queries to the DNS server that is configured in your settings, so the results should be identical.
I would try re-configuring your DNS setting on your router, and maybe even reloading your firmware if that didn't fix it after a reboot.
Let me know how it goes...
--
"Opportunities multiply as they are seized." - Sun Tzu
[text was edited by author 2002-07-30 03:13:54] |
|
kosiac
join:2001-01-10
Dayton, OH
| Interesting. For me, the virtual circuit only fails when querying the router and not the external dns. I tried this from both my systems(XP and 2K). If I turn it off (it is by default in nslookup) the query works fine to the router.
Can you explain what "Virtual Circuit" actually means? I can not find a good definition of it.
Do you think I should I reload firmware or just restore the factory defaults or both?
True the router is not an authoritative source for DNS, I thought it acts as a DNS proxy, and it maintains a table with cached DNS entries and various other elements. I thought it was more than a passive pass through to the authoritative sources.
[text was edited by author 2002-07-31 00:43:42] |
|
kosiac
join:2001-01-10
Dayton, OH
| Answered one of my own questions. Found this about Virtual Circuit:
DNS uses IP port number 53 and can either use UDP or TCP for transport. Generally, UDP (limited to 512 bytes) is used for queries and responses i.e. Lookups but, TCP (virtual circuit) has to be used for Zone Transfers as the data shared between authoritative servers handling particular zones needs to be reliable.
Possibly the vc is unsupported on the Netgear.
--
- Dayton, Ohio, The TRUE Birthplace of Aviation - |
|
SYNACK
Just Firewall It
Premium,Mod
join:2001-03-05
Venice, CA
 ·Comcast Formerly ..
Host:
Networking
Virtual Private Ne..
Netgear
ZyXEL
| Yes, the router only listens for 53/UDP, not TCP.
try:
ip tcp stat
ip udp stat
... to see all services running on the router.
Simply configure with the external DNS servers directly, then it's just another outgoing TCP connection.
--
Where in the world is LA/OC ? |
|
