Right now the nios appliances are not managing the DHCP, so I want to do GSS-TSIG updates from Clients to Infoblox dns servers.The nios version is: 6.7.1-204398 I already have my dns zone (authoritative) with AD integration (svc entries & co.) and all works just fine.Layered on top of those connections is a virtual adapter implemented by a Net Motion VPN client.The wifi and Net Motion connections employ Infoblox DHCP scopes to obtain their IP and network settings (the Verizon connections are managed separately via a private IP setup with Verizon, and don't come into play in this issue).
The thought process was that yes once every 4 days, the wifi lease would expire and yes, DNS might get updated to the wifi IP temporarily, but within an hour at most, the Net Motion lease would expire/renew, and the IP would be updated back to the Net Motion IP for the device.
The wifi scope has a lease length of 8 days; the Net Motion client scope has a lease length of 2 hours.
Both have IPv4 DDNS settings "The network adapters in Windows are set with "Update DNS" unchecked for the wifi adapter, and "Update DNS" checked for the Net Motion virtual adapter (that's a carryover from before we transitioned the DHCP to Infoblox, when we wanted the Windows DNS client enacting the DNS change - though we don't think it should be needed, since the Infoblox DHCP range should be updating it anyway).
Hi all, i'm trying to integrate my AD environment with the infoblox DNS.
I would like to let my AD clients to dynamically update the dns name on the nios appliance.