Edward Ned Harvey wrote: > > But, I just got the idea from startssl.net ... All you need to do is connect > to a webpage, or any web service for that matter, and they know your client > IP address. As long as you have *any* way to uniquely identify yourself to > a web site, the automatic DDNS could be updated simply and easily. Could be > a client installed on your system with saved credentials. Could be a signed > cert of some kind used to identify your system... > > And then you've got simple, reliable, globally available DDNS.
I use editdns.net, and that is how they do it, a quick wget with the right user id and password, and it updates the DNS record you're targetting - they even support different passwords for each record. But, I think this is the wrong approach: -for your idea to work, you have to have a short TTL on your DNS record. The DNS infrastructure was meant to use caching as much as possible, with a lot of short TTL, the DNS servers are going to be hit hard. -more importantly, you can setup A record with ddns, but NOT the reverse lookup, only the owner of the block can do that. A reverse lookup is often done as an added security to make sure the machine talking to us really is who they claim they are, a lot of mail servers do that for example. -as mentioned yesterday, there are protocols out there that use proper authentication over encypted channels to let peers establish a peer to peer connection through a dialogue through servers that work well. What problem are you trying to solve? -- Yves. http://www.SollerS.ca/ gmail, jabber, LiveJournal, nimbuzz, ovi, dreamhost xim.ca: xmpp:y...@zioup.com _______________________________________________ Discuss mailing list Discuss@lopsa.org http://lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
