[SOLVED] nsupdate with key to a BIND server

Started by yannix, April 03, 2019, 10:58:16 PM

Previous topic - Next topic
April 03, 2019, 10:58:16 PM Last Edit: April 09, 2019, 07:56:11 AM by franco
Hello,

I'm new to opnsense.

I'm asking if it's possible to run 'nsupdate' (using keys) to a bind server as a custom dyndns option. I looked into the custom settings but it seems it prefers to do the update using HTTP authentication instead.

If it's not an option, I am okay writing a custom startup? script but how does one reference the WAN IP?

I envision nsupdate running everytime my WAN IP changes and during router startup.

Thanks in advance


It sounds like you are looking for the RFC 2136 plugin....


Cheers,
Franco

That was it.

I ran into a minor issue adding a new entry, it kept complaining about invalid characters in my DNS key name. Turns out it didn't like the fact that my key name has a trailing dot. I removed it from both opnsense and my named.conf and it went through fine.

Just wanted to bring this to your attention in case it's an issue. I can't seem to find anything that indicates it would cause an issue (or noncompliance with RFC) one way or another. Just an old habit of mine from years of dealing with bind.

Thanks for pointing me to the right direction.

We could remove the trailing dot, but I'm not sure about the impact then. Let's leave this thread here for future users to stumble upon. If there are 1-2 more reporters we can surely look into it more closely. :)


Cheers,
Franco