Dhcp not updating dns on domain controller
Does anyone have the steps to change from an Active Directory DNS to just infoblox.
I have followed the white papers but the domain controller will not write the AD DNS information to the infoblox system.
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.
You also forget to reconfigure the DHCP scope options so the clients still point at the ISP’s DNS server instead of the new DC. The DC doesn’t register SRV records in the new DNS zone and the clients wouldn’t be able to find them, even if it did. Read the rest of the column for suggestions about resolving Internet names. It accepts the flat name from the user then appends a suffix to form a FQDN it can send to a DNS server.
The member computers don’t know that the domain has been upgraded to AD unless they just happen to authenticate at the PDC. Users treat additional keystrokes as if they were penalties visited upon them by uncaring IT bureaucrats. The resolver obtains this DNS suffix from one of several places.
It’s best to leave this field empty in deference to the Primary Suffix.The TCP/IP Settings window calls this the Primary Suffix.If a query using the primary suffix fails, and the Append Parent Suffixes option is checked, the resolver strips the leftmost element from the primary suffix and tries again. The TCP/IP settings for each network interface can have a unique DNS suffix, populated either statically or with DHCP.The other computers get no group policies, so you can forget about any carefully-orchestrated centralized management scheme. Imagine what would happen if you asked your users to type Fully Qualified Domain Names (FQDNs) rather than simple flat names to connect to internal servers. Users are willing to type com to buy a used wristwatch, but they don’t want to type \w2k3s102school.edu\ freshman_zclass to map a drive. The domain to which the desktop or server belongs has a DNS name as well as a flat name.DNS servers, however, stubbornly insist that every query specify a target domain. You can see this suffix in the Properties of the local system (Figure 1).
The servers use static mappings to the same external DNS servers.