wiki help with Dynamic DNS Services

[ispyisail]

Hi all

I'm trying to document "Dynamic DNS Services" on our wiki

http://www.gargoyle-router.com/wiki/dok ... s_services

I've become come a little stuck and have decided to ask the wise men here

I know how Dynamic DNS Services works on a DSL router, no problems there but...........

In New Zealand the primary domestic internet connection is PPPoA

Code: Select all

internet -- xDSL Router -- Gargoyle -- PC 

What we have is double NAT. If we set up Dynamic DNS Services on gargoyle the private WAN address will be sent to Dynamic DNS provider

The question is can we bridge my DSL router running PPPoA?

With PPPoE I assume you bridge your DSL router?

Help!

[Eric]

It doesn't really matter how you obtain your WAN IP.

Dynamic DNS determines the outer WAN IP by visiting a website (there are several of these that it rotates using so it doesn't hit one over and over) that shows what IP it thinks is connecting. [Side note, that I just considered: Do NOT try to run Tor and dynamic DNS at the same time... you'll end up associating the domain name with the Tor exit node]. Then, it checks whether that IP is currently assocated with the specified domain name(s), and if not sends instructions to the Dynamic DNS provider to assocate the WAN IP with the requested domain(s).

[hnl_dk]

Hello Eric
Looking at the syslog information from ispyisail, it looks like his dynamic DNS is searching all the time. Is that because of Tor?
http://www.gargoyle-router.com/phpbb/vi ... 430#p10430

[Eric]

hnl_dk: I don't see any messages in that syslog output from dynamic dns... maybe you linked to the wrong thread?

[hnl_dk]

hnl_dk: I don't see any messages in that syslog output from dynamic dns... maybe you linked to the wrong thread?

I thought that this had something to do with dynamic DNS (I have removed everything else from the log):

Code: Select all

    Jan 20 15:30:52 Gargoyle daemon.info dnsmasq[2487]: exiting on receipt of SIGTERM
    Jan 20 15:30:53 Gargoyle user.notice dnsmasq: DNS rebinding protection is active, will discard upstream RFC1918 responses!
    Jan 20 15:30:53 Gargoyle user.notice dnsmasq: Allowing 127.0.0.0/8 responses
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: started, version 2.55 cachesize 150
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: compile time options: IPv6 GNU-getopt no-DBus no-I18N DHCP TFTP
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq-dhcp[3200]: DHCP, IP range 192.168.15.100 -- 192.168.15.250, lease time 12h
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.142.171.235#53 for domain micro
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.211.32.162#53 for domain micro
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 66.244.95.20#53 for domain micro
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.142.171.235#53 for domain oss
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.211.32.162#53 for domain oss
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 66.244.95.20#53 for domain oss
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.142.171.235#53 for domain null
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.211.32.162#53 for domain null
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 66.244.95.20#53 for domain null
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.142.171.235#53 for domain ing
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.211.32.162#53 for domain ing
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 66.244.95.20#53 for domain ing
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.142.171.235#53 for domain indy
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.211.32.162#53 for domain indy
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 66.244.95.20#53 for domain indy
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.142.171.235#53 for domain gopher
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.211.32.162#53 for domain gopher
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 66.244.95.20#53 for domain gopher
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.142.171.235#53 for domain geek
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.211.32.162#53 for domain geek
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 66.244.95.20#53 for domain geek
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.142.171.235#53 for domain fur
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.211.32.162#53 for domain fur
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 66.244.95.20#53 for domain fur
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.142.171.235#53 for domain free
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.211.32.162#53 for domain free
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 66.244.95.20#53 for domain free
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.142.171.235#53 for domain bbs
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.211.32.162#53 for domain bbs
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 66.244.95.20#53 for domain bbs
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.142.171.235#53 for domain dyn
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.211.32.162#53 for domain dyn
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 66.244.95.20#53 for domain dyn
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.142.171.235#53 for domain parody
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.211.32.162#53 for domain parody
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 66.244.95.20#53 for domain parody
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.142.171.235#53 for domain glue
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.211.32.162#53 for domain glue
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 66.244.95.20#53 for domain glue
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 78.47.86.43#53 for domain bit
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 178.32.31.41#53 for domain bit
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using local addresses only for domain lan
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: reading /tmp/resolv.conf.auto
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 192.168.0.1#53
    Jan 20 15:30:56 Gargoyle daemon.warn dnsmasq[3200]: ignoring nameserver 192.168.15.1 - local interface
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.142.171.235#53 for domain micro
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.211.32.162#53 for domain micro
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 66.244.95.20#53 for domain micro
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.142.171.235#53 for domain oss
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.211.32.162#53 for domain oss
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 66.244.95.20#53 for domain oss
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.142.171.235#53 for domain null
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.211.32.162#53 for domain null
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 66.244.95.20#53 for domain null
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.142.171.235#53 for domain ing
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.211.32.162#53 for domain ing
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 66.244.95.20#53 for domain ing
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.142.171.235#53 for domain indy
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.211.32.162#53 for domain indy
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 66.244.95.20#53 for domain indy
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.142.171.235#53 for domain gopher
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.211.32.162#53 for domain gopher
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 66.244.95.20#53 for domain gopher
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.142.171.235#53 for domain geek
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.211.32.162#53 for domain geek
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 66.244.95.20#53 for domain geek
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.142.171.235#53 for domain fur
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.211.32.162#53 for domain fur
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 66.244.95.20#53 for domain fur
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.142.171.235#53 for domain free
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.211.32.162#53 for domain free
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 66.244.95.20#53 for domain free
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.142.171.235#53 for domain bbs
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.211.32.162#53 for domain bbs
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 66.244.95.20#53 for domain bbs
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.142.171.235#53 for domain dyn
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.211.32.162#53 for domain dyn
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 66.244.95.20#53 for domain dyn
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.142.171.235#53 for domain parody
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.211.32.162#53 for domain parody
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 66.244.95.20#53 for domain parody
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.142.171.235#53 for domain glue
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 95.211.32.162#53 for domain glue
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 66.244.95.20#53 for domain glue
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 78.47.86.43#53 for domain bit
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using nameserver 178.32.31.41#53 for domain bit
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: using local addresses only for domain lan
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq[3200]: read /etc/hosts - 2 addresses
    Jan 20 15:30:56 Gargoyle daemon.info dnsmasq-dhcp[3200]: read /etc/ethers - 0 addresses

I at least do not that this in my own syslog. And I find it to be very heavily part of his syslog (I would guess that it will make his router slower).

[Eric]

No, that's dnsmasq, the dns server built into the router. That should appear at boot in 1.5.2+ as it's just noting the servers used to register the OpenNIC and NameCoin domains -- it's not slowing anything down.

Messages from dynamic dns (which will be prominent in the log, if activated, since it logs every time it checks whether an update is needed, ~ every 15 minutes depending on how you have it configured) don't seem to be present in this log.

[hnl_dk]

No, that's dnsmasq, the dns server built into the router. That should appear at boot in 1.5.2+ as it's just noting the servers used to register the OpenNIC and NameCoin domains -- it's not slowing anything down.

Ah, okay, I have just never noticed in my own syslogs, so I just wondered.
EDIT: Just saw it now... when one of my computers got started. But that is only two logposts in one hour, compared to all the logposts in his syslog.

Messages from dynamic dns (which will be prominent in the log, if activated, since it logs every time it checks whether an update is needed, ~ every 15 minutes depending on how you have it configured) don't seem to be present in this log.

okay, thank you.

[Eric]

Actually... just double checked the Tor issue. The way I have it set up now, communications that originate from the router itself (not connected clients), don't get sent through Tor, so dynamic dns would in fact determine the correct WAN IP.

On the other hand, it means communications from the router itself are "leaking"... not sure if that matters or not, since by itself the router isn't doing anything that problematic. Note that there is also a bug that's causing all Tor DNS requests to leak in 1.5.2 (which is very bad!), that's since been patched.

[ispyisail]

Thanks guys

I will attempt and document the procedure

In still unsure how the Dynamic DNS provider knows which is my outer WAN?

[hnl_dk]

Thanks guys

I will attempt and document the procedure

In still unsure how the Dynamic DNS provider knows which is my outer WAN?

If you visit/ping anything on the net, it will always know your external WAN address, except if you run it through a proxy (like Tor), as your computer is not the one visiting the website, in that case, but the proxyserver/"tor node".