Dynamic DNS settings for AVM FritzBox router

Follow
Avatar
dirtyharry_28

I am using OpenDNS since yesterday and have set it up in my router (AVM Fritz!Box 7330) using the infos for the dynamic IP update which I gathered searching the internet and tried the following configurations:

Config 1:
Update-URL: updates.dnsomatic.com/nic/update?myip=<ipaddr>
Domainname: dnsomatic
Username: [my DNS-O-Matic username]
Password: [my DNS-O-Matic password]

with this config the IP update works (can be seen on DNS-O-Matic and OpenDNS) but my router shows this in the log:
"Dynamic DNS-Fehler: Der angegebene Domainname kann trotz erfolgreicher Aktualisierung nicht aufgelöst werden"
which means "Although update was successful the domain name could not be resolved". Sure it has no TLD.

The "domainname" entry in the router is the customer URL from the dynamic DNS provider which makes the router available from external, like "myusername.dyndns.org".

I did not find any information on the OpenDNS and DNS-O-Matic website what this "domainname" could be. I also tried dnsomatic.com but without success, same with "localhost" - then the error gets even worse:
"Dynamic DNS-Fehler: Die Dynamic DNS-Aktualisierung war erfolgreich, anschließend trat jedoch ein Fehler bei der DNS-Auflösung auf."

Means: Update was successful but an error in DNS resolving occured afterwards" although I can normally access websites.

Currently trying to update directly via OpenDNS instead of DNS-O-Matic using this config.

 

Config 2:
https://updates.opendns.com/nic/update?hostname=home
opendns
Username: [my OpenDNS username]
Password: [my OpenDNS password]

(where "home" is the name for the registered network associated with my account)

With every config I get this error described below config 1) every 30 minutes - which seems to be the interval for the router to send an IP address update to a dynamic DNS service.

 

My question now is:
what should I use as proper "domainname" in the dynamic DNS settings to use with OpenDNS dynamic IP updates?

Maybe "OpenDNSusername.opennds.com" or "OpenDNSusername_networkname.opennds.com"?

 

Thanks a lot!

 

 

Timo

3

Comments

39 comments

Sort by Date Votes
  • Avatar
    dirtyharry_28

    this is also active




    IPv4.jpg
    0
    Comment actions Permalink
  • Avatar
    rotblitz

    The latter picture is the problem.  Again, if you want to make use of content filtering and stats, you must disable IPv6.
    See also https://support.opendns.com/forums/21295462-Community-Help/entries/search?utf8=%E2%9C%93&query=IPv6+disable&for_search=1

    "My OpenDNS dashboard shows the correct IPv4 address and the FritzBox uses the IPv4 DNS 208.67.222.222 as standard server so this should be fine, right?"

    Fine for IPv4, not fine if IPv6 is enabled and being used for DNS traffic.  We're all waiting for OpenDNS to allow registering also an IPv6 address at https://dashboard.opendns.com/settings/ ...

    You can check if your system uses IPv6 for DNS queries while executing a command like this:

       nslookup -type=txt debug.opendns.com.
       Server:  resolver1.ipv6-sandbox.opendns.com
       Address:  2620:0:ccc::2

    If the Server address being returned is an IPv6 address as shown above, then you're impacted, and you do not use content filtering and stats, although you may still be using OpenDNS if you configured OpenDNS IPv6 sandbox resolver addresses as you have demonstrated.

    Instead of using the OpenDNS IPv6 sandbox resolvers, you can also use the normal OpenDNS IPv4 resolver equivalents:

       ::ffff:d043:dede
       ::ffff:d043:dcdc
       ::ffff:d043:dedc
       ::ffff:d043:dcde

    Unlike the sandbox addresses, these addresses make use of the default OpenDNS settings like blocking phishing and some malware domains.  But these still do not allow you to use your individual dashboard settings.

    If you want to go further to at least block Adult content and Proxy/Anonymizer domains, you could use the OpenDNS FamilyShield equivalents:

       ::ffff:d043:de7b
       ::ffff:d043:dc7b

    That's all you can do.  Still not using your dashboard settings.  This has been discussed lengthy here: https://support.opendns.com/entries/21786344

    0
    Comment actions Permalink
  • Avatar
    dirtyharry_28

    Many thanks for the great explanation. Sad that OpenDNS does not support IPv6 yet with regards to filtering & blocking :( 

    For the time being I disabled IPv6 as I don´t really see any disadvantage. Did not have IPv6 since end of December and no issues without it before.

    0
    Comment actions Permalink
  • Avatar
    dirtyharry_28

    But at least the part of my guide should work if you do not use IPv6 then :)

    0
    Comment actions Permalink
  • Avatar
    mattwilson9090

    .The recent traffic in this thread got me to thinking about OpenDNS and IPv6. I'll post more details in the IPv6, but basically it will take more than registering a single IPv6 address. Basically, you'll need to register an IPv6 address for each device that is making a DNS request. Depending on how the network is configured that could mean just the router, or it could mean every single device on a network.

    0
    Comment actions Permalink
  • Avatar
    munrobasher

    >Try with the following in the domain name field:  myip.opendns.com 

    Ahh that's the little gem of information I was looking for. My client has three sites which because the DNS-O-Matic updater can't handle multiple hostnames as in this example, I was considering three OpenDNS/DNS-O-Matic accounts.

    https://updates.dnsomatic.com/nic/update?myip=82.22.226.206&hostname=name1.freedyn.de,name2.freedyn.de

    (This comes back with error "nohost")

    However, that means you have to whitelist each site individually by logging onto each of the three accounts in sequence.

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    Never ever enter myip.opendns.com in the domain field of a FRITZ!Box!  The box will not update then at all, because this domain points at your current IP address already, so no reason to perform an update.

    Also, DNS-O-Matic does not support a comma separated hostlist in the update request.  You can use all.dnsomatic.com to cover all your services defined at DNS-O-Matic.

    0
    Comment actions Permalink
  • Avatar
    munrobasher (Edited )

    Hi Rotblitz - yes, appreciate the problem now having just try to set it up at a client and reading this thread in detail. So I've put a legal but unresolvable domain in there - and we'll just put up with the error log. I assume this means that the Fritzbox will keep doing the DDNS update at whatever frequency it runs which is a bit of load on the OpenDNS network but what the heck. I know one could use DNS-O-Matic with an OpenDNS and another DDNS entry but my client has three sites and we'd prefer to use the "Update all domains" when unblocking sites. The switch to DNS-O-Matic would require three separate OpenDNS/DNS-O-Matic accounts and the unblocking would have to be done three times. It's a shame that OpenDNS doesn't offer a normal DDNS domain feature as well heck, it's free.

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    It seems you are confused.  Updating your OpenDNS dashboard network with your IP address information has nothing to do with "unblocking".  That is the reason why I'm far from understanding what you wrote last.  Try to understand what is what, and do the right things.  Using a non-existent domain is not one of them.  Also not sure why OpenDNS should offer a DDNS service.  It wouldn't look and behave any differently from other DDNS services like the ones listed here.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post