| ??? 07/16/09 17:19 Read: times |
#167438 - dynDNS Responding to: ???'s previous message |
Raj Nambiar said:
1. With DynDNS, how will my client know and acquire the dynamic address of the hardware? Many routers are smart enough to realize that when the dynamic addressed assigned by the ISP changes, it can update your DynDNS account with the new IP address. That's half of the magic. 2. If the device address is not public, then will DynDNS work? DynDNS doesn't care about the private addresses (NAT) behind your router. It only cares about the public address that is dynamically assigned by the ISP. The other half of the magic is that you register a domain name and you set up your DynDNS account to map your domain name to the dynamic/public IP address assigned by the ISP. So nobody needs to know or care about the IP address ... you just point your browser (or other software) at http://www.mydomain.foo and it just works. Generally, we use a UDP relay socket on a public IP to handle changing IPs. This works fine even if the machines are private, behind a public router. If some service can do this thing, it would be great!! See above! Really, it works. -a PS: Obviously my home cable-modem service uses dynamic addressing. However, in practice, that address rarely, if ever, changes. It didn't change even when I swapped modems! I suspect this is done because my ISP (Cox Cable) is secretly filtering my data packets (the illegal wiretapping you've read about), and it's hard to keep track to exactly whom you are tapping if you keep changing the IP addresses. |
