Is it possible to exclude one or more DHCP servers from the dhcp-to-dns?

[MarkLFT]

Firstly, thanks for a great set of scripts. I had some very basic ones, but yours are so much better, so I ditched all of mine. ;-)

My router has five DHCP servers, one per VLAN. I only require DHCP-to-DNS entries for three of the VLANs. In the DHCP server scripts, I can comment out the lease-script, but I am afraid it may come back. Also, the scheduled job still seems to create the entries.

Maybe there is a comment I can apply, or something I can do on the server, to disable its use altogether?

[eworm-de]

Currently it is not possible. You can influence the domain name used, but there is no way to ignore a server completely.

With oldest RouterOS supported by my scripts (currently 7.19) it would be a huge change implementing this... I would have to move all the code into just another :if block. 🥴

However this will become a lot easier with RouterOS 7.22. Are you running that already? I could prepare the change in staging already I think... Would have to take a look.

[eworm-de]

Hmm, would it be ok to have the setting on notwork (/ip/dhcp-server/network/), not on server?

[MarkLFT]

@eworm-de On the server would be fine. I have a one-to-one relationship between the server and the network, so it would not matter which one it went on.

Thanks for looking at this.

[eworm-de]

Well, you did not give the RouterOS version you are running. With 7.22 you could give the code from staging a try. Should be sufficient to switch just that script (use staging instead of next):
https://rsc.eworm.de/BRANCHES.md

The updated documentation is here:
https://rsc.eworm.de/staging/doc/dhcp-to-dns.html#configuration

[MarkLFT]

We are currently on 7.21.3, but as long as there are no breaking changes, we should be able ot move to 7.22. I will do some testing.

[eworm-de]

Please do, and keep me updated.

[MarkLFT]

I upgraded one of our routers to version 7.22 and switched the DHCP-to-DNS script to the staging branch. What I observed was that the scheduled job did not remove the existing static DNS entries for the guest networks. However, I manually deleted all managed static entries, and the scheduled job created only new entries for non-guest networks.

I hope this feedback is useful for you. Many thanks for your prompt action on this.

[eworm-de]

What I observed was that the scheduled job did not remove the existing static DNS entries for the guest networks.

That is kind of expected. The code does not expect the entries to be there in the first place, so it does not check for the ignored network. After all the leases are still valid...

However, I manually deleted all managed static entries, and the scheduled job created only new entries for non-guest networks.

That's what it should work like. 👍

I hope this feedback is useful for you. Many thanks for your prompt action on this.

Thanks!