Surf for free on any public wireless pay-network!

[manarak]

You can tunnel your internet connection through the DNS system.

This site explains how, and there is even a video!

http://dnstunnel.de/

Great when stuck somewhere...
Have fun..

[BAM]

You think that good I know someone who's rigged a Blackberry to do basically the same thing through the Cell companies DNS tunnelling everything from his BB to his VPN server using the Cell providers network for free. He can do VoIP, Web, email, etc all for free!

[Stogie]

What's This Site About?

Did you ever sit at the airport or at a cafe and there was a unencrypted wireless access point nearby, but whenever you wanted to visit a site their website would pop up asking for a fee to use the internet through their AccessPoint (aka. Captive Portal)?

Well, I did, several times. But in most cases you are able to look up arbitrary hostnames, ie. google.com. That is because if you cannot resolve a host name your browser won't display any site. So these providers usually allow to look up hostnames to then filter whether they are allowed to access the site or not. In the latter case, their pay-to-get-access site pops up.

But you can use the fact that you can resolve arbitrary hostnames to gain free connection to the internet. Not a very fast one, though, but still a free internet connection.
The Idea

The Idea is to tunnel all outgoing traffic through DNS. Yes, you heard right, through DNS, the Domain Name System, used to translate human-readable hostnames to numerical IP addresses and vice versa.

To understand how this'll work, you need a little knowledge of DNS. The DNS system has quite a lot of so-called types of records, such as A for address record, NS for nameserver record, CNAME for canonical name record etc. The most commonly used record is the A record. To let the hostname example.com point to 192.0.34.166 you'd set up the following in your DNS server's config:

example.com. IN A 192.0.34.166

Usually, such entries are stored at your provider's nameserver and you don't have any/full control over them (most likely if you bought a rather cheap webhosting package). But to allow DNS tunneling to work, there has to be a little bit more advanced setup.

What we'll do is delegate all requests to a certain subdomain (or, subzone) to another nameserver. That means: People want to look up your IP, get to your ISP's nameserver and will be redirected to your own nameserver which can then answer the request. For this, of course, you'll need a server running the client where you can become root.

Keep in mind: All requests to a certain subdomain are relayed to your host, which then answers them. And you won't look up ordinary hostnames, I tell you. Hope you got the idea.
Technical Setup

To delegate all requests to sub.example.com to ns.anothernameserver.com, you first have to delegate all requests to that server (NS record, line 1) and then send a so-called GLUE record (that is, glued to the record before because it's most likely the asking server will need this info as well) with your server's IP (line 2, A record).

sub.example.com. IN NS ns.anothernameserver.com.
ns.anothernameserver.com. IN A 192.0.34.166

If you just have a DynDNS account and no static IP, you'd set up the delegation using a CNAME record. As mentioned above, CNAME is a canonical name (speak: an alias). So when a server gets back a CNAME instead of an A record (IP address) he continues to look up this hostname. That brings us to the following:

sub.example.com. IN NS ns.extern.example.com.
ns.extern.example.com. IN CNAME foo.bar.dyndns.org.

The Fake Server

The fake server you can set up at your server to tunnel all the traffic through is a little program called OzymanDNS, written in Perl (Client and Server together 642 SLOC) by DNS guru Dan Kaminsky. The tool is split in four files, two of them being a file upload/download tool using DNS. Nice examples, but rather uninteresting for our approach.

The script nomde.pl is the server. Since the server binds to port 53 UDP on your server (which is a privileged port) you must be root to start the server. Also, make sure port 53 UDP is reachable from the outside (consider running nmap -v -sU host from a remote machine). You will usually want to start it as follows:

sudo ./nomde.pl -i 0.0.0.0 server.example.com

Here, the server will only listen to DNS requests for all subdomains of server.example.com. That way, people who don't know that exact address cannot use the service on your server.
The Client

The OzymanDNS client is just a perl script which encodes and transfers everything it receives on STDIN to it's destination, via DNS requests. Replys are written to STDOUT.

So this isn't particularly useful as a standalone program. But it was designed to be used together with SSH. And with SSH this works great. SSH has a config option, ProxyCommand, which lets you use OzymanDNS's droute.pl client to tunnel the SSH traffic. The command to connect to your server would look like this:

ssh -o ProxyCommand="./droute.pl sshdns.server.example.com" user@localhost

Note two things:

1. Add a sshdns. in front of the hostname you specified the server to listen to and
2. Since your connection will already have been tunneled through DNS (and thus has come out at your host already) there is no need to login as [email protected] (because that already is localhost)

Once the connection is established (you'll probably have to enter your password) you have a shell! The connection is a little bit droppy sometimes and has not got the best latency, but it is still good keeping in mind that connections to the internet are not allowed at this Cafe/Airport/....
Tunneling

Once you verified that the connection is actually working, you can set up a tunnel so that you may not only have shell, but complete web acces, can fetch mails using POP, etc., etc...

For this, I recommend to read my tutorial on How to Tunnel Everything through SSH.

Don't forget: It may provide great performance increases to use SSH's -C ("compress data") switch!
Communication between the Servers

So, now how might the servers communicate with each other, not being directly able to establish a connection?, you might ask now.

Well, since all subdomain resolve requests are delegatet (ie., relayed) to your host, you can include arbitrary data in the hostname which your server then can interpret and execute/relay.

The bytes you want to send to the server (upstream) will be encoded using Base32 (if you know what Base64 is, Base32 is just the same except there is no case sensivitiy, for EXAMPLE.COM ist just the same as example.com). After the data, there is a unique ID (since some DNS requests may take longer than others and the UDP protocol has no methods to check this) and either one of the keywords up or down, indicating whether the traffic's up- or downstream. Here is what an example request could look like (transferring something to the server):

ntez375sy2qk7jsg2og3eswo2jujscb3r43as6m6hl2ws
xobm7h2olu4tmaq.lyazbf2e2rdynrd3fldvdy2w3tifi
gy2csrx3cqczxyhnxygor72a7fx47uo.nwqy4oa3v5rx6
6b4aek5krzkdm5btgz6jbiwd57ubnohnknpcuybg7py.6
3026-0.id-32227.up.sshdns.feh.dnstunnel.de

The server's response comes as a DNS TXT record. A TXT record can hold arbitrary ASCII data and can hold uppercase letters as well as lowercase letters and numbers (some other characters, as well). So the responses come Base64 encoded. Such a response might look like the following one:

695-8859.id-39201.down.sshdns.feh.dnstunnel.de. 0 IN TXT
"AAAAlAgfAAAAgQDKrd3sFmf8aLX6FdU8ThUy3SRWGhotR6EsAa vqHgBzH2khqsQHQjEf355jS7cT
G+4a8kAmFVQ4mpEEJeBE6IyDWbAQ9a0rgOKcsaWwJ7GdngGm9j pvReXX7S/2oqAIUFCn0M8="
"MHw9tR0kkDVZB7RCfCOpjfHrir7yuiCbt7FpyX8AAAABBQAAAA AAAAAA"

That is, in rough outlines, how tunneling via DNS works.
Security Issues

There are a few security issues you'll have to think about before letting the server run permanently:

* As soon as some people guess which subdomain you use to tunnel DNS they can send arbitrary commands to the server. I haven't reviewed the code for too long, but there might be the possiblity of a bug which could be exploited to gain access to your system. But that ist just a unlikely hypothesis.
* The software still is very experimental and crashes every now and then (see below for a workaround).
* Consider that the server puts a high load on your system while actively surfing.

I own a Server but my ISP doesn't allow me to change (the relevant) DNS settings

Well, that is the reason I created this website. I offer to set up a subdomain for you which delegates all requests (see above) to your fake nameserver. For this you just need to set up your own listening server. That means you must have a machine connected to the internet on which you may become root.

If you want me to set up a delegation of a subdomain to your fake nameserver, just write me an email to . You should include your full name, your server's static IP or DynDNS hostname and the desired subdomain name (name.dnstunnel.de; I encourage you to keep this secret for your own security).

Please only send requests for hosts you really own. Please do NOT send requests for hosts you 0wn.

Please don't be disappointed: I have a lot of other stuff to do, so I probably cannot answer your request promptly€”sorry!
Legal Warning

Circumventing the AP's access controls (that includes DNS tunneling) is most probably considered to be a crime, depending on the country you live in. I am not responsible for whatever you do with your tunnel. I am just providing two simple entries in my ISP's DNS server to let a hostname point to your server's IP.
Helper Script

Here are two little helper scripts that'll allow you to automatically start OzymanDNS on system boot through initd. This is my /etc/init.d/ozymandns file:

#!/bin/sh
# Written by Julius Plenz

set -e

case "$1" in
start)
echo -n "Starting ozymandns listener..."
screen -d -m /usr/local/bin/ozymandns-listener
echo "."
;;
stop)
echo -n "Stopping ozymandns listener..."
kill `cat /var/run/ozymandns.pid`
echo "."
;;
restart)
/etc/init.d/ozymandns stop
/etc/init.d/ozymandns start
;;
reload|force-reload)
echo "cannot do that"
echo "."
;;
*)
echo "Usage: /etc/init.d/$NAME {start|stop|restart}"
exit 1
;;
esac

exit 0

Of course, you'll have to make the script executable. Then I'd suggest to put two links to automatically start and terminate the server on bootup/shutdown:

~# cd /etc/rc0.d/; ln -s ../init.d/ozymandns K15ozymandns
~# cd /etc/rc2.d/; ln -s ../init.d/ozymandns S99ozymandns

The program called from the init script (/usr/local/bin/ozymandns-listener) looks like this:

#!/bin/sh

REPLYIP=0.0.0.0
DNSHOST=name.dnstunnel.de

echo $$ > /var/run/ozymandns.pid

while [[ -e /var/run/ozymandns.pid ]] ; do
cd /usr/local/bin/
nomde.pl -i $REPLYIP $DNSHOST >/dev/null 2>&1
done

Note: This script again assumes you have installed the nomde.pl server in /usr/local/bin/ as well.

That easy, eh?

I'd rather just pay the one euro!

[manarak]

there are probably other sites explaining it better - this one contains much technical background info.

[manarak]

(BAM @ Jun. 19 2009,08:06) You think that good I know someone who's rigged a Blackberry to do basically the same thing through the Cell companies DNS tunnelling everything from his BB to his VPN server using the Cell providers network for free. He can do VoIP, Web, email, etc all for free!

I'm surprised the bandwidth over DNS is sufficient for VoIP!

[bunnytv]

just clone the mac adress of other user if you whant free wifi


air port hacking http://www.airporthackers.com/wifi-news/

[SamplerDoc]

Sticking your wifi where it does not belong can lead to very bad things if you are not careful

Some folks set others up with the free wifi offers to lure you in and highjack your info etc.....

Surf safe out there.

[bunnytv]

(SamplerDoc @ Jun. 19 2009,15:32) Sticking your wifi where it does not belong can lead to very bad things if you are not careful  

Some folks set others up with the free wifi offers to lure you in and highjack your info etc.....

Surf safe out there.  

you or right

but that can hapend any time pub or local net work


its best to just hack a lock net work less risk it loaging you

[manarak]

*ahem*

- it is unlikely that the DNS traffic will be logged by hotspot punks

- the traffic sent over the DNS system is compressed for speed, so they can't read it straight away, they will need to figure it out, and losers logging hotspot traffic don't like working (and I am pretty sure most of them don't know how to do it)

So I think your traffic is safer over the DNS hack than over the regular network.

[bunnytv]

how one can hack some one with out thim knowing it over wifi is ad hock


dns will not keep some one like me from geting info as im the server all i have to do is name  my self the other network name and xp will kick start on to my laptop

now i got full acess so dns will not be needed

and i can make vista i not try to many xp laptop one can hit

so as far as loging this will not mater we dnt need to log this way it slow and slopy


you wood get more may be but we can use cmd line to installl stuff on the user pc over telnet  then we can just install a key loger so when it did leve or network it wood log it

im tired so i probly need fix this gramer later and virus scan wood not del it as i will not be useing tool that in the list

[manarak]

i probly need fix this gramer

you could check the spelling too

[bunnytv]

HAHA ye
sorry haveing truble sleeping only got a hr1 sleep last nigt the dam babe keeping me up

[manarak]

(bunnytv @ Jun. 22 2009,21:43) HAHA ye
sorry haveing truble sleeping only got  a hr1 sleep last nigt the dam babe keeping me up

heh, that's a statement!

congrats, and... keep doing what you were at! :-)

[BAM]

(bunnytv @ Jun. 19 2009,12:33) just clone the mac adress of other user if you whant free wifi


air port hacking  http://www.airporthackers.com/wifi-news/

Looks like your Airport buddies missed their flight.........

Looking for who is responsible for airporthackers.com and followed ns2.inmotionhosting.com.

Nameservers for www.airporthackers.com:

ns.inmotionhosting.com returned (NORECORDS)
ns2.inmotionhosting.com returned (NORECORDS)

[bunnytv]

i dnt know i got it off google