And the answer is that INADYN in RC1 of TrueNAS Core, is version 2.2.
Updating INADYN to v2.7 fixed the issue.
Seems to work well with the first run.
The second run generates this cryptic error:
“Failed to get IP address for firstname.lastname@example.org”
Now, that should be fixed under TrueNAS Bug Ticket NAS-103353.
Not for me (or do I have a different issue?)
Things to check out:
- Do I need to manually change the inadyn.conf file as per this DNS-O-Matic sample config?
- What does extra logging tell me?
- Do I need do delete the cache file, and test?
- Explicitly specify all.dnsomatic.com?
inadyn.conf – /usr/local/etc
log file – /var/log/