Updating bind serial numbers automatically
I liken it to the days when automobiles had carburetors; a mechanic could fix most engine performance problems by fiddling with the choke—spritz a little WD-40 into the throttle body, charge and retire in the suburbs after a few years. Check the TCP/IP settings, run a few utilities to verify the zone records, charge 0 (correcting for inflation) and retire to Arizona.You’ll learn to identify the most common domain name system issues that cause problems for AD and Exchange and how to avoid them in the first place or isolate and resolve them if they occur in production.Also, the more experience you have, the more likely you are to make your DNS infrastructure complex, inviting the attention of Mr.Murphy and other elements of chaotic cosmic calamity.If your DNS TTL setting is 12 hours, your DNS records will be cached for 12 hours before they expire and the new information takes effect.TTL on 1&1 domains is set for up to 1 hour for all A, AAA, MX, TXT, and CNAME records. The typical default value is usually 12 hours (43200 seconds) or 24 hours (86400 seconds).You let DCPromo configure a zone file that matches the DNS name you selected for AD. Once you enter the correct DNS entries in TCP/IP settings at the DC, populate the zone with SRV records by stopping and starting the Netlogon service.You’re so pleased with the ease of the upgrade that you forget to reconfigure the TCP/IP settings of the newly upgraded DC to point at itself for DNS. (If you’ve installed the Support Tools, you can run Netdiag /fix.) Now change the DHCP scope option to point clients at the new DC for DNS, then chase down any statically mapped servers and desktops and correct their DNS entries.
It takes 12-24 hours for the new DNS changes to take effect.
Don’t forget to include the FQDN of the local domain as the first option on the list.
Learn about DNS TTL settings, and best practices for setting DNS TTL for your domain names.
If the TCP/IP settings for a member computer specify the IP address of a public DNS server—perhaps at an ISP or DNS vendor or the company’s public-facing name server—the TCP/IP resolver won’t find Service Locator (SRV) records that advertise domain controller services, LDAP, Kerberos and Global Catalog.
Without these records, a member computer can’t authenticate and get the information it needs to operate in the domain.