Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Monday, February 21, 2011 5:00 PM
Hi
I don't know much about DNS but suppose it must be something to do with the problem. We have one main DC1 and an emergency machine, DC2, which has some errors in its DNS (some incorrect root servers for some reason) which will be cleared up hopefully when we wipe the machine and reinstall (for other reasons). We're using Windows Server 2003.
The active directory on DC2 is out of date due to undetected replication problems going back to before my time here resulting in user logon problems and more (hence the wipe/reinstall plan), but in the meantime I've noticed that when I ping the local domain (ping ourplace.local), it returns the IP address of DC2 rather than DC1 as we would expect (DC1 having always been the authoritative DC around here).
I take it the DNS settings are going to be wrong somewhere and may account for this (and fixing it may make logons more reliable while the other repairs are in progress)? Where should I be looking? Forward Lookup Zones? In the DNS settings under DomainDNSZones, DC2 is listed first (and indeed anywhere else in the settings where it appears). Would that be a problem? Either way, any suggestions as to how to fix this (if it even needs fixing)?
TIA!
All replies (23)
Monday, February 21, 2011 6:17 PM ✅Answered
Hello,
pinging the domain name will just result in one DNS server answering. There is no option that you have influcence of which one reacts, ping is also not site aware. So no worry about that and not a problem with DNS for this.
Do you use AD integrated DNS zones and have _msdcs.ourplace.local and ourplace.local already listed? If not please follow CASE2 in: http://support.microsoft.com/kb/817470/
As you are talking about problems with DC2 and you think about reomving it then make sure to run dcpromo on it to remove it correct from the domain. If this is not possible, becuase it is already outdated, over the tombstone lifetime, then disconnect it from the network and run at least dcpromo /forceremoval better make a reinstall including a full format.
After the removal of the problem DC you MUST run metadata cleanup on DC1 according to:
http://msmvps.com/blogs/mweber/archive/2010/05/16/active-directory-metadata-cleanup.aspx
Please post an unedited ipconfig /all from DC1, which should stay, so we can check some basic but important settings before you add a new DC to the domain.
Additional post an unedited ipconfig /all from a domain machine.
Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Monday, February 21, 2011 10:03 PM ✅Answered
If DC2 has been offline for more than 180 days, Meinolf provided his blog on how to clean it up.
Also, please provide the info he requested.
Keep in mind, the way AD works, AD will register a multitude of records into DNS, one of which is called the LdapIpAddress. Each DC registers one for itself. If you have two DCs, then you will see two LdapIpAddresses. They are under the domain.com zone and are called the "same as parent" record. If you see two, delete the old one.
Also look under gc_msdcs.domain.com. If you see DC2's IP, delete it.
Look in each zone's properties, nameserver tab. Delete DC2's reference.
Make sure you follow Meinolf's blog to clean up AD with the metadata cleanup procedure.
Once you've cleaned it up, you can never bring DC2 back online.
Rebuild from scratch. Do not use an image.
Make sure all internal machines are only using the internal DNS server, in your case, it will be DC1 until you get the new DC2 up and running.
It's recommended to make all DCs a GC, so when you get the new one up and running, make it a GC.
Ace
Ace Fekay
MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
This posting is provided AS-IS with no warranties or guarantees and confers no rights.
Tuesday, February 22, 2011 8:31 PM ✅Answered
Thanks for posting the requested info.
Why does the client machine have two default gateways? There can ONLY be one default gate on any machine.
I don't recommend clustering DCs. It;s recommended to have two DCs for fault tolerance.
You can try to use the dcpromo /forceremoval switch, but at this time, I would just shut it off and leave it off, and run the metadata cleanup process to remove it, that is if it is truly past the TTL. Follow Meinolf's blog on how to do that. Here's another, if you like to take a peek:
Complete Step by Step Guideline to Remove an Orphaned Domain controller
http://msmvps.com/blogs/acefekay/archive/2010/10/05/complete-step-by-step-to-remove-an-orphaned-domain-controller.aspx
As for DNS settings, when there are two DCs, or more, I would recommend pointing the first address to itself using the actual IP address, then the second one to the partner. If there are three or more, choose one of the others as the "standard" one you're going to use a the second entry, preferrably one in the same AD Site, or another if no other is in the same Site.
DC1 has WINS proxy enabled. Not good. Let's disable that and can cause numerous issues:
How to Disable NetBT Proxy on Incoming Connections (How to disable WINS Proxy):
http://support.microsoft.com/kb/319848
And regarding pinging the domain name, bbcosgate.local, as Meinolf said, only one will respond. The record that gets resolved is the LdapIpAddress record, the one in DNS that shows up as "same as parent." Each DC registers one. If you ping the name one after the other, you'll notice it rotates, whcih is Round RObin taking effect. THis is default. It simply doesn't work by unplugging one of them and not expecting it to get resolved by DNS. In any AD infrastructure, you can't simply unplug a DC due to this and numerous other reasons. It also affects the client side resolver service. Here's more on that:
DNS, WINS NetBIOS, Client Side Resolver algorithm, Browser Service, Disabling NetBIOS, Direct Hosted SMB (DirectSMB), If One DC is Down Does a Client logon to Another DC, and DNS Forwarders Algorithm if you have multiple forwarders.
http://msmvps.com/blogs/acefekay/archive/2009/11/29/dns-wins-netbios-amp-the-client-side-resolver-browser-service-disabling-netbios-direct-hosted-smb-directsmb-if-one-dc-is-down-does-a-client-logon-to-another-dc-and-dns-forwarders-algorithm.aspx
And what is "ourplace.local?" Is there another domain involved, or was that just a substitute name?
Ace
Ace Fekay
MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
This posting is provided AS-IS with no warranties or guarantees and confers no rights.
Tuesday, February 22, 2011 2:15 PM
Hi, thanks to both of you for your responses.
Here is an ipconfig /all for what I’ve called DC1:
Windows IP Configuration
Host Name . . . . . . . . . . . . : warehouse-serv
Primary Dns Suffix . . . . . . . : bbcoxgate.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : bbcoxgate.local
Ethernet adapter Local Area Connection
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
Physical Address. . . . . . . . . : 00-04-23-BB-C6-2C
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.10.5
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.10.1
DNS Servers . . . . . . . . . . . : 127.0.0.1
And here, for a client machine logged on to the the local domain via DC1:
Windows IP Configuration
Host Name . . . . . . . . . . . . : chris
Primary Dns Suffix . . . . . . . : bbcoxgate.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : bbcoxgate.local
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82562V-2 10/100 Network Connection
Physical Address. . . . . . . . . : 00-1A-A0-8E-C5-25
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.2.37
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 192.168.10.251
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.10.1
192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.10.1
For DC2 we have:
Host Name . . . . . . . . . . . . : backup-serv
Primary Dns Suffix . . . . . . . : bbcoxgate.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : bbcoxgate.local
Ethernet adapter Local Area Connection
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : 00-1E-C9-FE-75-50
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.10.8
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.10.1
DNS Servers . . . . . . . . . . . : 192.168.10.5
192.168.10.8
We’ve turned off DC2 at the moment because while it is on, logon problems get worse (we get intermittent “target account name is incorrect” and in addition, people’s roaming profiles can’t be used (again, intermittently). While DC2 is off, we tend instead to get “the domain is unavailable” errors. After anything from a few minutes to a couple of hours of messing about achieving nothing, the problem tends to go away... every morning.
On switching off DC2 altogether, when I ping the local domain, it still tries to go to DC2’s IP address, and the pings fail.
Meinolf: To answer your specific questions, we do have _msdcs.ourplace.local and ourplace.local listed in our AD DNS settings. DC2 is past the tombstone lifetime so I guess we’ll do a dcpromo /forceremoval on it, and then just switch it off and, as advised, wipe it and start again after cleaning up DC1.
Ace: For fixing up the DNS on DC1, we will delete the references to DC2 after it has been removed from our network (I am supposing you are saying that is necessary because dcpromo is not going to work - which it won’t because DC2 is past the tombstone period). Then we get the network working properly with the one server, then introduce the second.
I’m thinking we can improve things by having the new DC2 take on all the functions of DC1 as well - logons, profile data, and so on, so that whichever server fails next, the users won’t necessarily notice... When I arrived at this site, it was not doing anything other than interfering with logons and losing people’s profiles... No other data was stored on it. They have a sales and stock control database system here on DC1 that is not replicated anywhere else but which is quite critical and I think should be on both servers somehow. I’ve been reading about cluster servers, but I’m not sure that that is what this is, or if there’s another alternative way of protecting this. Maybe that’s a separate question... ;-)
Thursday, February 24, 2011 2:27 PM
OK Ace, thanks for that... I'll check these matters out. Yes, "ourplace.local" was just a substitute.
Martin
Alphatucana http://www.alphatucana.co.uk/ http://www.websitetavern.com/
Thursday, February 24, 2011 6:11 PM
Hello,
in addition to Ace i am also interested about using 2 ip addresses on the client with different subnets?
Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Friday, February 25, 2011 11:37 AM
Hi,
Apparently it is there for the phone system. I don't think it is needed on any of the PC's in fact.
Martin
Alphatucana http://www.alphatucana.co.uk/ http://www.websitetavern.com/
Friday, February 25, 2011 12:11 PM
Hi
Re: WINS - we have a couple of remote sites that connect to our database using a VPN... I don't know if this may be needed for them (they use Win XP I believe) as I didn't set it up and don't know where to look to check...
Re: pinging local domain: with our DC2 off, the results do seem to be varying, but not in a round-robin style. Instead, each machine I ping from consistently gives the same results, although these results vary from one machine to another. For example, from my PC, I always get 'could not find host' (although everything seems to work OK). Pinging from DC1 it resolves the IP address of DC2; another PC pings DC1; these results are consistent, yet the IP settings on the machines are all the same (apart from their own IP address, plus I'll change the IP address of the DNS server on DC1 from 127.0.0.1 to its own IP address as you suggest as that is indeed a difference).
Martin
Alphatucana http://www.alphatucana.co.uk/ http://www.websitetavern.com/
Friday, February 25, 2011 2:08 PM
Correction: when I try pinging a few hours later, I do get different results. They vary between the three options mentioned earlier: DC1, DC2, or host not found.
Martin
Alphatucana http://www.alphatucana.co.uk/ http://www.websitetavern.com/
Friday, February 25, 2011 3:47 PM
Hi,
Apparently it is there for the phone system. I don't think it is needed on any of the PC's in fact.
Martin
Alphatucana http://www.alphatucana.co.uk/ http://www.websitetavern.com/
The problem I see with the PC ipconfig, is yes, it has two IPs, but it also has two gateways. As I mentioned earlier, any machine can only have ONE default gateway. You can create static routes using the "route" command (which won't show up in an ipconfig), but not directly specifying it in NIC properties.
Did you disable WINS proxy?
Also, just to iterate, when you ping bbcoxgate.local, it will resolve to the LdapIpAddress. That is the record(s) under the bbcoxgate.local zone without a hostname, or also known as the "same as parent" record. This record is used by AD, the client side GetGpoList function, and other functions. Each DC registers one by its netlogon service.
So for example if there are two DCs, then both DCs will register one. When you ping it, it will round robin between the two. Same with nslookup. You can type in nslookup bbcoxgate.local, hit enter, then arrow up, and hit enter again, and you should see it bounce between the different entries.
And no, ping and nslookup are not AD Site aware, so if there are Sites configured, only AD aware apps (such as a joined machine looking for GPOs, DCs, etc), will use that feature.
If you continuously see a record for a DC that is no longer active, it may be that it's reference is still in the AD database causing it.
Ace
Ace Fekay
MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
This posting is provided AS-IS with no warranties or guarantees and confers no rights.
Tuesday, March 1, 2011 11:24 AM
OK, thanks; I'll be disabling WINS proxy today - but as it needs a reboot it'll probably have to be after hours. I'll do a metadata cleanup on the AD database later in the week and hopefully it will clear up the remaining anomalies.
Thanks for the help.
MartinAlphatucana http://www.alphatucana.co.uk/ http://www.websitetavern.com/
Tuesday, March 1, 2011 3:23 PM
You are welcome. Please provide an updated ipconfig /all after you've completed the tasks.
Thanks!
Ace
Ace Fekay
MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
This posting is provided AS-IS with no warranties or guarantees and confers no rights.
Thursday, March 17, 2011 10:19 AM
Just an update. Not quite fixed yet. The tombstoned DC2 was removed, and a brand new secondary DC installed and promoted. Replication was re-enabled between the two servers, and works OK. DC1 was then cleaned up (metadata cleanup to remove the obsolete server from Active Directory) and DNS cleaned up too, and WINS removed.
However: pinging the local domain still sometimes returns the IP address of the extinct and removed server.
I'll post an ipconfig /all from the two servers and a local machine shortly.
Alphatucana http://www.alphatucana.co.uk/ http://www.websitetavern.com/
Thursday, March 17, 2011 10:28 AM
Here are the ipconfigs:
From DC1:
Windows IP Configuration
Host Name . . . . . . . . . . . . : warehouse-serv
Primary Dns Suffix . . . . . . . : bbcoxgate.local
Node Type . . . . . . . . . . . . : Hybri
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : bbcoxgate.local
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
Physical Address. . . . . . . . . : 00-04-23-BB-C6-2C
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.10.5
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.10.1
DNS Servers . . . . . . . . . . . : 192.168.10.5
192.168.10.7
8.8.4.4
From client machine:
Windows IP Configuration
Host Name . . . . . . . . . . . . : chris
Primary Dns Suffix . . . . . . . : bbcoxgate.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : bbcoxgate.local
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82562V-2 10/100 Network Connection
Physical Address. . . . . . . . . : 00-1A-A0-8E-C5-25
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.10.251
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.10.1
DNS Servers . . . . . . . . . . . : 192.168.10.5
192.168.10.7
8.8.4.4
From DC2:
Windows IP Configuration
Host Name . . . . . . . . . . . . : bbcserve2
Primary Dns Suffix . . . . . . . : bbcoxgate.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : bbcoxgate.local
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet #2
Physical Address. . . . . . . . . : 00-1E-C9-FE-75-51
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.10.7
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.10.1
DNS Servers . . . . . . . . . . . : 192.168.10.7
192.168.10.5
8.8.4.4
Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : 00-1E-C9-FE-75-50
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.76.176
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
Alphatucana http://www.alphatucana.co.uk/ http://www.websitetavern.com/
Thursday, March 17, 2011 10:31 AM
My previous post hasn't appeared, yet the ipconfigs have... just in case: pinging the local domain still returns the IP of the now extinct old DC2 sometimes. DC2 was removed, DC1 metadata cleaned up, WINS removed, brand new DC2 installed, replication restored, all working apart from that pinging... which I suppose indicates something wrong still, somewhere.
Alphatucana http://www.alphatucana.co.uk/ http://www.websitetavern.com/
Thursday, March 17, 2011 11:30 AM
Hello,
remove the 8.8.4.4 as DNS server from the NIC on all domain machines. This result in problems.
Instead configure the Forwarders on the DNS server properties in the DNS management console with that ip address.
Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Thursday, March 17, 2011 3:39 PM
Alphatucana ,
I agree with Meinolf, that external DNS MUST BE REMOVED. You can configure that as a Forwarder, as he said.
Also, please disable Ethernet adapter Local Area Connection 2: on DC2 (bbcserve2), because even though it may be unplugged, it is still registering a 169.254.x.x address into DNS. Please check every folder and section in DNS to remove any iterations of this IP.
In addition, please go through every folder and section DNS and check all records, including the "same as parent" record. This record is what will be resolved when you ping "bbcoxgate.local" (without a hostname) which I am assuming is the issue that still exists.
Ace
Ace Fekay
MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007 & Exchange 2010, Exchange 2010 Enterprise Administrator, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
This posting is provided AS-IS with no warranties or guarantees and confers no rights.
Thursday, March 17, 2011 5:05 PM
Hi, OK thanks guys... you were right: there were still some references to the old server in DNS. I've exterminated the lot now, so I guess it won't show up again. I've disabled the spare NICs (I had thought I had done that already), and removed 8.8.4.4 from the remaining NIC DNS settings. Hopefully this will fix things. Now, 8.8.4.4 is just an external DNS server (Google's public DNS) - should I configure this as a secondary forwarding zone? Or just leave it? Our router knows the ISP's DNS anyway, but the Google one seems faster, generally.Alphatucana http://www.alphatucana.co.uk/ http://www.websitetavern.com/
Friday, March 18, 2011 6:09 AM | 1 vote
As previously stated by myself and Meinolf, you will want to configure the Google DNS server 8.8.4.4 as a Forwarder.
PLEASE do not create a zone or anything else for Google DNS or any other external DNS server.
To configure 8.8.4.4 as a Forwarder, please follow these steps:
- Open DNS console
- Right-click the DNS server name
- Choose Properties
- Click on the Forwarders tab
- Enter 8.8.4.4
- Click Ok
- Enter an additional Forwarder as a backup (such as 8.8.8.8, another Google DNS server).
Oh, and make absolutely sure that no internal workstation, laptop or any other machine is using 8.8.4.4 as a DNS address. Check DHCP Option 006 to insure that ONLY the internal DNS servers are being provided to DHCP clients. This is important for client to AD communications.
I hope that helps!
Ace
Ace Fekay
MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007 & Exchange 2010, Exchange 2010 Enterprise Administrator, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
This posting is provided AS-IS with no warranties or guarantees and confers no rights.
Monday, March 21, 2011 9:15 AM
OK, it is configured as described, as a forwarder. We aren't using DHCP so the workstations are manually configured to look at the DC's for their DNS anyway. This morning, when I ping ourdomain.local, I get "Ping request could not find host" so something is still up, I suppose. It has been finding one or other DC, so this morning it is the error's turn... I had no trouble logging on to the network, however, and have received no complaints from any other users so far. I'll double-check the DNS records for signs of the extinct DC. Hmm... my own machine had 8.8.4.4 as one of its DNS targets... on removal, the ping works. OK. QED I suppose! I'll let you know if the problem resurfaces then! Thanks.Alphatucana http://www.alphatucana.co.uk/ http://www.websitetavern.com/
Monday, March 21, 2011 2:41 PM
It sounds like you got it working now! Yes, make sure that 8.8.4.4 doesn't show up on anyone's machine, or you will get problems pinging or accessing any internal resources, especially AD will fail.
Cheers!
Ace
Ace Fekay
MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007 & Exchange 2010, Exchange 2010 Enterprise Administrator, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
This posting is provided AS-IS with no warranties or guarantees and confers no rights.
Sunday, February 3, 2013 7:49 PM
I have a similar bug, I promote Virtual machine as new DC in the domain.
My new DC ping the wrong IP when I ping the domain name, it' s ping the old domain IP.
I Finally found why:
The thing is, I make several test in lab with this VM just promoted as DC and I forget to remove a alias in the host file I add before. That entry are pointing in the old IP of that domain.
I remove that alias in my host file on the DC in problem are back in business now.
Problem resolved! :-D
Eric
Monday, February 4, 2013 5:59 AM
I have a similar bug, I promote Virtual machine as new DC in the domain.
My new DC ping the wrong IP when I ping the domain name, it' s ping the old domain IP.
I Finally found why:
The thing is, I make several test in lab with this VM just promoted as DC and I forget to remove a alias in the host file I add before. That entry are pointing in the old IP of that domain.
I remove that alias in my host file on the DC in problem are back in business now.
Problem resolved! :-D
Eric
So then it wasn't really a "bug," rather a forgotten setting in the hosts file.
Ace Fekay
MVP, MCT, MCITP/EA, MCTS Windows 2008/R2 & Exchange 2007, Exchange 2010 EA, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
Technical Blogs & Videos: http://www.delawarecountycomputerconsulting.com/
This post is provided AS-IS with no warranties or guarantees and confers no rights.