12-12-2017 05:24 PM
We have a network environment with 2 AD domain names(such as abc.com and efg.com), and we wish to allow DHCP to able to updates DDNS whenever the user obtained DHCP from Infoblox.
The problem is that under "DDNS domain name" option in IPv4 DDNS inside DHCP network, it seems only allow single domain name for DDNS updates. When I put one of the domain name, the another user domain which get DHCP under same network segment does not updates DDNS; when I did not put any domain name under that option, none of the domains will update DDNS.
Just wonder if anyone has faced similar issue before? How do you managed to populate DDNS updates for a network that consists of multiple AD domains?
12-14-2017 10:15 AM
If you leave that option blank in the DDNS portion of the DHCP options, the DHCP server will update DNS with the suffix given to it by the device in DHCP option 81.
If devices do not know \ provide a DNS suffix then Infoblox will add the DNS suffix listed in DHCP option 15, Domain Name, to the "short name" provided in the DHCP conversation by the client.
Windows boxes do a pretty good job providing the DNS zone that matches their AD Domain in option 81 allowing this to work well even in environments with many AD zones. If you have a miss match between a AD Domain and its DNS zone, where the AD Domain has some portion of its NetBIOS name that is different from its DNS zone FQDN, then you can run into problems depending on the client OS level.
If you leave that same DDNS suffix blank and create some well written DHCP filters, you can also do things like identify all your printers and have them dynamically added to *.printers.domain.com, separate from *.AD1.domain.com and *.AD2.domain.com by handing a different Option 15 to different clients.
12-15-2017 04:45 AM
Thansk for your answer, I just go through manual and discover "Option 81 Support" under DHCP advance option to allow DHCP clients to perform DDNS updates on DNS records. It works well in a multi AD domains environment of a single DHCP network.