Hi,
Last weekend I migrated most of our DC's from Windows Server 2008R2 to Windows 2012. The 2008R2 servers were also DHCP servers. This role was migrated to a non DC Windows 2008R2 server during the migration. Most of the 2008R2 DC's were demoted, replication took place, then new Windows 2012 servers were promoted using the old name/IP address.
At headquarters, we previously had two Windows Server 2008R2. Ill call them Headquarter-DC1 and Headquarter-DC2. Headquarter-DC2 was demoted but never shutdown or had DNS service stopped (a mistake on my part) which means it was configured with no zones. Headquarter-DC1 was demoted and then a Windows Server 2012 server was promoted with the same name/ip address as Headquarter-DC1.
When users came in Monday morning, they couldn't resolve hostnames. After checking DNS, I realized I hadn't removed Headquarters-DC2 which was the tertiary DNS server (and also had no DNS zones configured)given out from DHCP. After replacing the tertiary address, the clients started resolving the hostnames again. I also restarted DNS during this time. Some things to note is before the tertiary was replaced and DNS restarted, some clients just started resolving on their own while other clients logging in couldn't resolve hostnames until I made the changes noted above (about 15 minutes from when they booted up).
My question is did the tertiary DNS server with no zones entry affect the clients ability to resolve the name even though the first to DNS servers were resolving names properly (which doesn't make sense to me). Or is there another likely scenario I am missing?
Last weekend I migrated most of our DC's from Windows Server 2008R2 to Windows 2012. The 2008R2 servers were also DHCP servers. This role was migrated to a non DC Windows 2008R2 server during the migration. Most of the 2008R2 DC's were demoted, replication took place, then new Windows 2012 servers were promoted using the old name/IP address.
At headquarters, we previously had two Windows Server 2008R2. Ill call them Headquarter-DC1 and Headquarter-DC2. Headquarter-DC2 was demoted but never shutdown or had DNS service stopped (a mistake on my part) which means it was configured with no zones. Headquarter-DC1 was demoted and then a Windows Server 2012 server was promoted with the same name/ip address as Headquarter-DC1.
When users came in Monday morning, they couldn't resolve hostnames. After checking DNS, I realized I hadn't removed Headquarters-DC2 which was the tertiary DNS server (and also had no DNS zones configured)given out from DHCP. After replacing the tertiary address, the clients started resolving the hostnames again. I also restarted DNS during this time. Some things to note is before the tertiary was replaced and DNS restarted, some clients just started resolving on their own while other clients logging in couldn't resolve hostnames until I made the changes noted above (about 15 minutes from when they booted up).
My question is did the tertiary DNS server with no zones entry affect the clients ability to resolve the name even though the first to DNS servers were resolving names properly (which doesn't make sense to me). Or is there another likely scenario I am missing?