RFC2136 dynamic dns update (bind-nsupdate)

NETWORKING SOLUTIONS
1

Hello

I have a use case for updating a dynamic IPv6 address for the mob1s1a1 interface. Since it is behind CGNAT, the V6 remains externally accessible and is a good way to remotely connect with the device. I previously used a custom script to update my DNS server (BIND) using TSIG key.

I don’t see any example of how to configure the bind-nsupdate method in the builtin Dynamic DNS config area. Is it documented anywhere?

2

Hello,

I use a direct freedns.afraid.org entry and a crontabs command for that:

15 3 * * * sleep 14; curl https://v6.sync.afraid.org/u/xxxxxxxx/

xxxxxxxx is the key assigned when you register a free name.

Works fine.
Regards,

3

Thanks as always @flebourse for your tips. I didn’t want to rely on another 3rd party (I already have my own BIND infra set up) so I just went back to my hand-rolled script + crontab.

At some point nsupdate was removed from the base RUTOS build so I did have to opkg -e /etc/opkg/openwrt/distfeeds.conf install ddns-scripts-nsupdate --force-overwrite (yes the force was needed for some reason…)

A little hairy but all good for now.

4

I noticed that there is a preinstalled package named ddns-scripts_nsupdate which conflicts with the needed ddns-scripts-nsupdate package (note the subtle difference: _ vs -).

The conflicting file is /usr/lib/ddns/update_nsupdate.sh

This should be corrected (or better yet, put nsupdate back in the base build, since out of the box the rfc2136 dyndns update choice is completely non-functional, with no visual indication of such)

5

Hello,

Apologies for the delayed response.

Could you please confirm whether the issue has been resolved or if you still need assistance?
If you do need help, it would be helpful if you could share your setup and provide more details about what you’re trying to achieve.

Best regards,

7

Hi thanks for asking. No, it’s not resolved. I filed a VIP case #448930 but that case was put on hold, it is not resolved yet. It was suggested to use snsupdate but that was not a viable solution for me because it does not support IPv6, which is critical for this case.

So, please consider this as “not resolved” still…

8

Thank you for the information. I can see that a ticket has been created for our R&D team regarding your issue, and the necessary implementations are most likely planned for the RutOS 7.15 firmware release.

I recommend continuing the discussion via Helpdesk with your assigned engineer, as they have more detailed information about the case.

I appreciate your understanding.

Best regards,

9

This topic was automatically closed after 60 days. New replies are no longer allowed.