#1  
Old January 31st, 2013, 05:22 PM
valerio_vanni valerio_vanni is offline
Junior Member
NETGEAR Newbie
 
Join Date: Dec 2010
Posts: 43
valerio_vanni is on a distinguished road
Default www.routerlogin.net: how does it work?

I think it's all clear when the PC has the router as dns server: the PC asks for www.routerlogin.net, and the router answers with his own IP instead of asking to its forwarder.

The case I don't understand is when the PC has NOT the router between his dns servers.

Example (manual configuration, no DHCP):
Indirizzo IP. . . . . . . . . . . . . : 192.168.1.173
Subnet mask . . . . . . . . . . . . . : 255.255.255.0
Gateway predefinito . . . . . . . . . : 192.168.1.1
Server DNS . . . . . . . . . . . . . : 8.8.8.8

Notice that the ONLY dns server is 8.8.8.8 (google public dns).

"ping www.routerlogin.net" -> it resolves to 192.168.1.1

"nslookup www.routerlogin.net" -> the same

And 8.8.8.8 (obviously) doesn't know anything about www.routerlogin.net: froma a local network without a netgear router it doesn't resolve it.

How can it happen?
The only hypothesis i can do is that the router acts like a transparent proxy for TCP port 53, and doesn't let go out the request to 8.8.8.8 (or another DNS server) for www.routerlogin.net.
Reply With Quote
  #2  
Old February 1st, 2013, 10:39 AM
jmizoguchi's Avatar
jmizoguchi jmizoguchi is offline
Junior Member
 
Join Date: Feb 2007
Location: Kentucky, USA
Posts: 0
jmizoguchi is an unknown quantity at this point
Default Re: www.routerlogin.net: how does it work?

routerlogin.net only for router access.
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off



All times are GMT -8. The time now is 05:03 AM.