Dhcp not updating on dns
I will monitor the issue for a few days and update status as it progresses Sounds like you may have stumbled onto your issue -- that is, your AD integration means that your DHCP server is letting your DNS server know each time it assigns a lease.
Since when you log off the wireless, you're NOT actually releasing the address, the DNS server is keeping that address -- as you have pointed out, for the term of the DHCP lease, or 7 days.
"Saibot75" If "Secure only Updates" are being used (they should be) the DHCP server might not be authenticating, or it might not be using the correct DNS server set (ONLY), or it might not be a member of the DNSUpdate Proxy groups, or better be using the correct DNS Update credentials with a valid and current password.
Both our equipment and the network printers use FQDN option 81 and requests the DHCP server to update the DNS and support for this option is also enabled in the DHCP server.
- Scavenge set to 7 days I don't have the FQDN option 81 in the DHCP. to=296095728 =================================== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue, to respond directly to me remove the nospam. =================================== =================================== Use Outlook Express? Get OE_Quotefix: It will strip signature out and more =================================== Keep a back up of your OE settings and folders with OEBackup: Hi, that's the strange thing.
On a small network, It did work to exclude DHCP option 15 (DNS Domain name), and printers started to register in the DNS. On the small network(one subnet), after taking the Option 15 of the Scope and restarting printers they registered in DNS. I assign the IP's that the printers had to another devices and tried to let them reregister in dns without a success, they got new ip's but didn't register in DNS.
Update Credentials are set to the same account on all (competing) DHCP servers so that the secure updates will not conflict.
Check the command line set command for logonserver: set logonserver ....ensure this is set to a replciated DC -- or use NLTest and Net Diag for definitive tests.
I am not running out of DHCP addresses so that is not a concern.