Project

General

Profile

Bug #15790

In MS DHCP provider disabling ddns should be done on subnet scope, not per record.

Added by Dmitri Dolguikh almost 3 years ago. Updated over 2 years ago.

Status:
Rejected
Priority:
Normal
Category:
DHCP
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

Disabling of ddns per record isn't supported.


Related issues

Related to Smart Proxy - Feature #15452: DIsable Dynamic DNS for Microsoft DHCP <-> DNS interoperationClosed2016-06-17

History

#1 Updated by Dmitri Dolguikh almost 3 years ago

  • Related to Feature #15452: DIsable Dynamic DNS for Microsoft DHCP <-> DNS interoperation added

#2 Updated by Paul Kelly over 2 years ago

  • Status changed from New to Feedback
  • Assignee set to Dmitri Dolguikh

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?

#3 Updated by Dmitri Dolguikh over 2 years ago

You are right, I followed the docs which turned out to be lacking/misleading. Thanks for the correction!

#4 Updated by Dmitri Dolguikh over 2 years ago

  • Status changed from Feedback to Rejected

Also available in: Atom PDF