DNS Issue
The company im working right now just migrated our windows server 2000 to windows server 2008 R2.
But currently we have a problem in our DNS , our current Active DNS is the DNS that was running on windows server 2000.
So our Server 2008 R2 DNS's is actually pointing at the old DNS server.
The problem is my new server and my clients cannot resolve our intranet sites.
May 11th, 2012 7:52am
Hello,
Please install DNS on your new DCs and make sure that your domain zones are AD-Integrated. Once done, check that there is no issues with AD replication by running
dcdiag /v on DCs you have.
Once replicated, your new DCs will hold primary copies of your DNS zones. In this case, you can switch your servers / client computers to point to them for DNS resolution. You can use
nslookup for testing purposes.
Please note that Windows Server 2000 is no longer supported so please remove it. Another thing is that it is recommended to have at least two DC / DNS / GC servers per AD domain.
Check also that you have one IP address in use and one NIC card enabled on DCs (All other ones should be disabled;
This
posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Microsoft
Student Partner 2010 / 2011
Microsoft
Certified Professional
Microsoft
Certified Systems Administrator: Security
Microsoft
Certified Systems Engineer: Security
Microsoft
Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft
Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
Microsoft
Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
Microsoft
Certified Technology Specialist: Windows 7, Configuring
Microsoft
Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
Microsoft Certified IT Professional: Enterprise Administrator
Microsoft Certified IT Professional: Server Administrator
Microsoft Certified Trainer
Free Windows Admin Tool Kit Click here and download it now
May 11th, 2012 8:17am
Hello,
Please install DNS on your new DCs and make sure that your domain zones are AD-Integrated. Once done, check that there is no issues with AD replication by running
dcdiag /v on DCs you have.
Once replicated, your new DCs will hold primary copies of your DNS zones. In this case, you can switch your servers / client computers to point to them for DNS resolution. You can use
nslookup for testing purposes.
Please note that Windows Server 2000 is no longer supported so please remove it. Another thing is that it is recommended to have at least two DC / DNS / GC servers per AD domain.
Check also that you have one IP address in use and one NIC card enabled on DCs (All other ones should be disabled;
This
posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Microsoft
Student Partner 2010 / 2011
Microsoft
Certified Professional
Microsoft
Certified Systems Administrator: Security
Microsoft
Certified Systems Engineer: Security
Microsoft
Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft
Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
Microsoft
Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
Microsoft
Certified Technology Specialist: Windows 7, Configuring
Microsoft
Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
Microsoft Certified IT Professional: Enterprise Administrator
Microsoft Certified IT Professional: Server Administrator
Microsoft Certified Trainer
May 11th, 2012 8:17am
Unfortunately the description of situation is NOT clear.
1. How have you migrated? Would you give more information on migration process?
2. It is not clear what is the current status of Active Directory (AD). Does old server have any domain controller role?
3. It is not clear what DNS roles are in old and new AD. Why is new DNS pointing to old DNS?
4. Whenever you do any changes in DNS settings, it is helpful to delete DNS cache (ipconfig /flushdns and analogous change is needed when DHCP configuration change is the case....)
Regards
Milos
Free Windows Admin Tool Kit Click here and download it now
May 11th, 2012 2:36pm
Hello,
for starting please post an uneditred ipconfig /all from the old/new DC and a client with problems.
Additional install, if NOT done during dcpromo, DNS server role on the new OS DC also. BEFORE i suggest to enable AD integrated DNS zones on the old DC/DNS server, so DNS zone information is replicated automatically between the DCs.
Assure that you use FORWARDERS on the DNS server properties in the DNS management console with the ISPs DNS servers.Best regards
Meinolf Weber
MVP, MCP, MCTS
Microsoft MVP - Directory Services
My Blog: http://msmvps.com/blogs/mweber/
Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.
May 14th, 2012 5:06am
Hello,
for starting please post an uneditred ipconfig /all from the old/new DC and a client with problems.
Additional install, if NOT done during dcpromo, DNS server role on the new OS DC also. BEFORE i suggest to enable AD integrated DNS zones on the old DC/DNS server, so DNS zone information is replicated automatically between the DCs.
Assure that you use FORWARDERS on the DNS server properties in the DNS management console with the ISPs DNS servers.Best regards
Meinolf Weber
MVP, MCP, MCTS
Microsoft MVP - Directory Services
My Blog: http://msmvps.com/blogs/mweber/
Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.
Free Windows Admin Tool Kit Click here and download it now
May 14th, 2012 5:06am