I am having troubles with DNS getting updated when a new DHCP lease is handed out.
The actual time of propagation may vary in some locations based on your network setup.
When you make a DNS change, it takes time for the changes to take effect. It is the time it takes for the domain DNS to refresh the cache on the network.
The I'm willing to bet that the System Administrator running your Windows DHCP server is requiring secure Dynamic DNS updates.
This means that you need to have a valid Active Directory account in the appropriate group in order to add or update DNS records in that zone.
From what I understand, the servers should update their own DNS records every 24 hours, but like I said, I have many that are over 24 hours old.
If I log on to the server and reboot, or run ipconfig /registerdns, it will update the timestamp just fine.
All of the systems are using DHCP with default settings. The Sys Admin who runs the DNS servers (Windows Server something) says that everything is fine, and any issues I'm having must be my fault. This problem today prevents my team from being able to access our subversion server, and the (Linux) workstations can't connect to LDAP for user authentication. However, the LDAP and Subversion servers are up with valid IPs, and can access other network resources and the Internet, but don't have an associated DNS entry.
Besides from running my own separate DNS server, what's a Linux Sys Admin to do?
Use Azure DNS to host your Domain Name System (DNS) domains in Azure.
Manage your DNS records using the same credentials, and billing and support contract, as your other Azure services.
When a domain is newly registered, the nameservers are changed, or DNS changes are made, you can expect a propagation time up to 24 hours.