Dynamic DNS not wollowing 'web-options'

General questions
5

AHHHH - okay, so each record needs to be associated under web if I want that to work, I see how that works now, and it is working as I would expect it to, given the syntax you provided.

I’ll go update my pull request and try and add some detail, that didn’t intuitive with how I read the documents. Perhaps I can make it better for the next person.

Awesome, thank you!

One question, if I may - given the new syntax/design, is it not possible then to use the web based IP discovery to tie it to the IP of a specific nic?

Good point! This is, unfortunately, a limitation of ddclient’s web based IP Address lookup. There are two possibilities that I can think of:

  • Configure dns dynamic as usual and then use event handler to force a ddclient refresh by runing op-mode command restart dns dynamic after the WAN connection fails over to the secondary WAN
  • Select a different routing path to reach the remote host of the web URL that provides the IP address and make that host routable only via the secondary WAN

For example, I can curl --interface eth3 http://dynamicdns.park-your-domain.com/getip (I’ll work on moving to an HTTPS provider, this is my first attempt at setup.) and get the IP that I actually want DDNS to set.

This is another possibility - exposing cmd based IP Address lookup (like curl, dig, wget, ip etc.). This might be too powerful to expose as a CLI configuration because of the inherent risk of ending up being misconfigured. I did consider implementing this (cmd based IP lookup) during the big dns dynamic rewrite but held back because of this.