> From: [email protected] [mailto:[email protected]] On > Behalf Of Yves Dorfsman > > -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.
The only time name resolver caching is useful (DNS or otherwise) is when repeating the same lookups. If you look me up, to initiate a video chat or something, you're not likely to repeat the lookup ad-nauseum. Imagine if we didn't use DNS. Suppose we all subscribe to something like skype. There's still a server out there, resolving names. And it's even less disperse than the DNS solution would be. I think the lookup traffic, even in this case, is insignificant compared to the payload. > -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. I don't think reverse lookup is important for peer to peer, or anything that uses dynamic IP addresses. > -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? This necessitates a server. It's not scalable for things like video chat and so forth. I'm not trying to solve any problem. Just learning about IPv6, pros, cons, etc. _______________________________________________ Discuss mailing list [email protected] http://lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
