Reply
Contributor
Posts: 41
Registered: ‎2010-12-18

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.
Regular Contributor
Posts: 89,285
Registered: ‎2009-01-27

Re: www.routerlogin.net: how does it work?

routerlogin.net only for router access.
VPN Case Study

VPNCASESTUDY.COM

"Our Second To None VPN Related Setup Case Study[/COLOR][/URL]

"One Stop Solution To Your Netgear VPN Connectivity"

*Visit the site for Non-VPN related Doc & Links* [Windows & Mac user/support]





June Mizoguchi-
Discussion Stats
  • 1 reply
  • 8678 views
  • 0 kudos
  • 2 in conversation
Top Contributors