Dhcp not updating on dns
Why are only the XP machines added and not the rest ?
I will forward your tips to our system administrators and hope they NOW are able to solve our problem... Kind regards, Tobias Olofsson ONLY if you don't use "Update Credentials" (a regulary user account with non-expiring password).
- 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.
Once your wireless DHCP server drops the address, it should remove it from the DNS server, thus allowing the DNS ADD request from the wired VLAN DHCP server to succeed -- and your name recognition should work (at least most of the time). Dan IT4SOHO This course will help prep you to earn the Comp TIA Healthcare IT Technician certification showing that you have the knowledge and skills needed to succeed in installing, managing, and troubleshooting IT systems in medical and clinical settings. You have kept very tight refresh and no refresh interval Ensure that your domain DNS zone srv records are updating as appropriate Other wise scavenging process will eventually delete all those srv records as well under _msdcs.zone and zone (_TCP, _UDP, _MSDCS folders etc.) I'd keep refresh interval 8 HRS and No refresh interval 4 HRS as a precautionary measure so that you will get sufficient time to update all relevant SRV records on domain controller Remember, scavenging need to be enabled on only one DNS server and changes will get replicated to all other DNS servers (which are also domain controllers) Mahesh I have made the suggestion to set the refresh intervals to the times above.
I noticed this morning that I now have 2 entries in DNS for most of the machines that switch between wireless and wired connections. Earlier today I reverted the scavenging times to no-refresh 4 hours, refresh 8 hours.