• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1698
  • Last Modified:

DNS Name does not Exist - when migrating from Server 2003 to Server 2008R2

Hi Experts,

I have installed Windows 2008 R2 on a new HP Proliant server with a plan to transition a 2003 AD domain to the new server. So far I have carried out the following:

2003 machine - I have carried out the adprep32 /forestprep; adprep32 /domainprep and adprep32 /domainprep /gpprep. The ip address of this DC is 10.71.104.2, default gateway is 10.71.104.1 and preferred DNS is 10.7.25.131.

The domain is called RMNETNT

NEW HP Machine - I have installed Windows 2008R2 O/S and given this server a static IP address of 10.71.104.3. Since I want to promote this server to a DC I have given it a default gateway of 10.71.104.2 and a preferrred DNS entry of 10.71.104.2 - ie the 2003 server.

The new server, at this point, is still part of WORKGROUP. I ran dcpromo and selected options as follows:

pic1
I actually tick the box "use advanced mode installation".

On the Deployment Configuration I choose "Existing Forest" and "Add domain controller to existing domain".

On the Network Credentials page I enter the domain name as NMNETNT and set the Alternate Credentials to NMNETNT\administrator with the admin password used to connect to the NMNETNT domain. I click NEXT.

Then within the SELECT A DOMAIN page I am shown the domain NMNETNT.LOCAL (forest root domain). So far so good.

Now when I click NEXT to continue I receive the following error:

======================================================================
The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain "RMNETNT.LOCAL"

The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)

The query was for the SRV record for _ldap._tcp.dc._msdcs.RENETNT.LOCAL

Common causes of this error include the following:

- The DNS SRV records required to locate a domain controller for the domain are not registered in DNS. These records are registered with a DNS server automatically when a domain controller is added to a domain. They are updated by the domain controller at set intervals. This computer is configured to use DNS servers with following IP addresses:

10.71.104.2

- One or more of the following zones do not include delegation to its child zone:

RMNETNT.LOCAL
LOCAL
. (the root zone)

=========================================================
Also, when I do a nslookup on 2008 machine it returns the following:

> Default Server: unknown
> Address : 10.71.104.2


What am I missing?? I have looked at some other solutions within EE but none work for my situation.

Have I forgotten to do something within DNS on 2003 Server?? I am at a loss and would really appreciate some help.

Thanks in advance.
0
gcgnjalc
Asked:
gcgnjalc
  • 2
  • 2
1 Solution
 
Sushil SonawaneCommented:
First add your new server Windows 2008 R2  in domain then run the command dcpromo


For more information, please refer to the following link: Verify DNS registration for domain controllers using the nslookup command
 
http://technet.microsoft.com/en-us/library/cc738991(WS.10).aspx   


For more troubleshooting please refer below link.

(http://social.technet.microsoft.com/Forums/en-US/winserverDS/thread/ede7e119-0d61-49db-9442-3610dfbf6971)
0
 
gcgnjalcAuthor Commented:
Thanks sushil84.

I have since made the change that you suggested, but the problem still exists. However, I have also run the netdiag.exe application on the 2003 server and found the following errors:

DNS Test................... failed
[WARNING] Cannot find a primary authoritative DNS server for the name 'vigserver.RMNETNT.local' [TIME OUT]
The name 'vigserver.RMNETNT.local' may not be registered in DNS.

Are you able to help me resolve this issue??
0
 
Sushil SonawaneCommented:
Run the command dcdiag /q and check the result.

If the you didn't get any error then try make  your 2008 server as ADC.
0
 
SandeshdubeyCommented:
It seems that Windows firewall is causing the issue.Disable local windows firewall service, by default it is enabled in vista/windows 2008 and above. Check the network connectivity by pinging the server.
Disable Windows Firewall: http://technet.microsoft.com/en-us/library/cc766337(WS.10).aspx

If multiple Nic are present diabled the unrequired NIC.Check the NIC binding as well,the NIC which is online and has ip details should be in first order.If multiple NIC are present then disabled the unrequired NIC.http://theregime.wordpress.com/2008/03/04/how-to-setview-the-nic-bind-order-in-windows/

Also make sure the IPv6 is configured to dynamic (Automatically).Join the server to domain and then try to pormote the server.

If still the issue persist post the Win2003 ipconfig /all details and dcdiag /q output.Alos post the Win2008 ipconfi /all details.

Since the servers are placed in different network ensure that required port are open for AD comminictation.
http://msmvps.com/blogs/acefekay/archive/2011/11/01/active-directory-firewall-ports-let-s-try-to-make-this-simple.aspx 

Also temporary diable the AV.It could be due to AV or 3rd party security application which act as firewall and block AD communuctaion.AV like Symantec,trend,etc have new features to "protect network traffic".Please check AV setting and disable the same if defined.
0
 
gcgnjalcAuthor Commented:
Thanks Sandeshdubey.

There is a second NIC but I won't be able to check out your potential solution until I am back on site tomorrow morning (24hours). I will update the forum then.
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now