Dhcp not updating on dns Lostgoddess web cam
Was trying that on a larger network with a lot of vlans without success. The goal is, everything that get's IP from the DHCP, is registered in the DNS. - Bjarni "Saibot75" wrote: Without option 015, DHCP cannot register in a Forward zone, it can only register in the reverse zone, even the the PTR will point to 'host' instead of 'host.domain.com' DHCP uses the domain name to know where to register A records. DHCP also, registers in the DNS servers in TCP/IP properties of the machine it is running on. Why are only the XP machines added and not the rest ?As a side info perhaps helpful, when examining the audit log in the dhcp subdirectory, for a complete week, not a single DNS update is made. Best regards, Tobias Olofsson Tip: If you add you own problems to someone else's thread there is a lower probability of receiving help.It seems the wireless DNS entry is the predominant one which is held in DNS which makes name resolution fail often. When I came in today I hard wired (and have been all morning).I performed a cold boot of my machine and obtained a wired DHCP address."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.If the Update Credentials works PREVIOUSLY then consider that this account may need an non-expiring password. DHCP server is NOT a member of the DNSUpdate Proxy group, should it be ?
most locations with lots of wireless users set a DHCP lease time of 15 minutes (vs. The issue being, with a 1-day lease, assuming a 24-bit netmask, you can only allow connections from 253 users per day -- regardless of how many at once. The main point you mention though is setting the wireless lease time to 15 minutes. I modified the DNS scavenging to No-refresh = 1 hour Refresh interval = 2 hours I will keep you posted on the results as I am still experiencing the issue but just made this change.- 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.I am running a Windows 2008 R2 domain with Active Directory integrated DNS.All users have laptops and frequently switch from wired to wireless connections (these are on separate VLAN's).