On Tue, 2007-06-19 at 13:33 +0530, Mrugesh Karnik wrote: > On Tuesday 19 Jun 2007 11:28:24 Nadeem M. Khan wrote: > > This seems to be normal stuff, but what strikes me the most is that it > > is able to see my private IP. > > Ever wondered how dynamic DNS works even behind a NATed connection?
Umm...AFAIK, Dynamic DNS doesnt have any relation to NATing. The reason why you're able to contact a webserver which is NATed by a firewall is because there is a rule in the firewall's configuration which forwards port 80 to your private IP. Dynamic DNS still points to the public IP itself. So, if you have a public IP like 59.x.x.x and run a webserver on a private IP 192.168.x.x port 80. Then, the Dynamic DNS will still resolve to 59.x.x.x. When the web browser of the client contacts this IP on port 80, the request is forwarded to the private IP 192.168.x.x The private IP which Rony and others saw on that site was because the system which was NATing their machine sent an HTTP header mentioning the private IP. -- Regards, Dinesh A. Joshi -- http://mm.glug-bom.org/mailman/listinfo/linuxers
