View Single Post
Old 11-30-2010, 05:26 PM  
Ethersync
Confirmed User
 
Ethersync's Avatar
 
Join Date: Mar 2008
Location: London, Saint-Tropez, Bermuda, Moscow
Posts: 5,289
Quote:
Originally Posted by Spudstr View Post
If its on port 53 and UDP traffic they can do whatever they please with it. .p2p doesn't mean squat, it just means those applications will have a "embeded" dns root to include for their TLD. DNS request goes out on port 53 and UDP. Thats the way the DNS RFC was written.

The only way around it is utilizing a IPsec VPN to connect and tunnel all your traffic.
You no doubt know far more on the subject than me. Thanks for the feedback.

Here is a comment I found on DSL Reports:

Quote:
The P2P based DNS service won't be using port 53. So ISP based filters will have no effect on this at all. The DNS queries to .P2P will be over encrypted P2P channels no doubt using high numbered ports that can be changed at random.
http://www.dslreports.com/shownews/P...P2P-DNS-111605

I have no idea if the person posting this knows what he is talking about or not, but is what he describes possible?
__________________
The best ePassporte replacement I have found: OKPAY
Ethersync is offline   Share thread on Digg Share thread on Twitter Share thread on Reddit Share thread on Facebook Reply With Quote