mirrors/iodine
1
0
Fork 0
mirror of https://github.com/yarrick/iodine.git synced 2024-07-09 22:53:33 +00:00
Code Issues Packages Projects Releases Wiki Activity

added dyndns info

Browse source
This commit is contained in:
Erik Ekman 2007-06-12 16:41:46 +00:00
parent 331e1ab247
commit adb701e024
1 changed files with 7 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
README
View file

@ -28,14 +28,18 @@ HOW TO USE:
Server side: Server side:
To use this tunnel, you need control over a real domain (like mytunnel.com), To use this tunnel, you need control over a real domain (like mytunnel.com),
and a server with a static public IP number (not behind NAT) that does not and a server with a public IP number (not behind NAT) that does not yet run
yet run a DNS server. Then, delegate a subdomain (say, tunnel1.mytunnel.com) a DNS server. Then, delegate a subdomain (say, tunnel1.mytunnel.com) to the
to the server. If you use BIND for the domain, add these lines to the zone file: server. If you use BIND for the domain, add these lines to the zone file:
tunnel1host IN A 10.15.213.99 tunnel1host IN A 10.15.213.99
tunnel1 IN NS tunnel1host.mytunnel.com. tunnel1 IN NS tunnel1host.mytunnel.com.
Do not use CNAME instead of A above. Do not use CNAME instead of A above.
If your server has a dynamic IP, use a dynamic dns provider:
tunnel1 IN NS tunnel1host.mydyndnsprovider.com
Now any DNS querys for domains ending with tunnel1.mytunnnel.com will be sent Now any DNS querys for domains ending with tunnel1.mytunnnel.com will be sent
to your server. Start iodined on the server. The first argument is the tunnel to your server. Start iodined on the server. The first argument is the tunnel
IP address (like 192.168.99.1) and the second is the assigned domain (in this IP address (like 192.168.99.1) and the second is the assigned domain (in this