Bug #15790
closed
In MS DHCP provider disabling ddns should be done on subnet scope, not per record.
Added by Anonymous over 8 years ago.
Updated over 8 years ago.
Description
Disabling of ddns per record isn't supported.
- Related to Feature #15452: DIsable Dynamic DNS for Microsoft DHCP <-> DNS interoperation added
- Status changed from New to Feedback
- Assignee set to Anonymous
Why do you say this? Which version of the DHCP server are you using. I admit that I have only used W2K8 DHCP and higher so maybe this will not work for earlier releases but that is why I added it as an configurable feature. If is possible to set this on a per-scope level then this is certainly more efficient but that is not always possible.
I admit the documentation is poor and does not show the exact per-host syntax but if you configure this parameter in the GUI and then do a dump of the server you will see that it writes out a line like
Dhcp server \\192.168.192.168 Scope 192.168.0.0 Set DnsConfig 192.168.0.1 0 0 0 0
for hosts that have DDNS disabled.
It is possible that this is not a general solution as my experience is limited and I am no Window expert but this appears to have worked for a couple of years now.
What is you experiencing that makes you think that this feature is not working?
You are right, I followed the docs which turned out to be lacking/misleading. Thanks for the correction!
- Status changed from Feedback to Rejected
Also available in: Atom
PDF
Updated by