2008 R2 - Active Directory Site Rename

Hello,

I installed two domain controller in two different subnets connected with a
router (no firewall rules). Both domain controllers are members of the first
default ad site. When I change the name of the default ad site and restart
the dc-b everything is ok. Then i restart dc-a, the dc takes forever to start
and the ad and the depending services have trouble to start. I did the
procedure in two different test environments. In both cases the same result
on dc-a.

What did i do wront?

Best,
René

Hello Rene,

Are both DCs also DNS server? If not install it also on the second one, use
AD integrated zones and configure both of them to use the other DNS server
as secondary on the NIC. Use the real ip addresses and not the loopback ip
address 127.0.0.1

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Hello,
>
> I installed two domain controller in two different subnets connected
> with a router (no firewall rules). Both domain controllers are members
> of the first default ad site. When I change the name of the default ad
> site and restart the dc-b everything is ok. Then i restart dc-a, the
> dc takes forever to start and the ad and the depending services have
> trouble to start. I did the procedure in two different test
> environments. In both cases the same result on dc-a.
>
> What did i do wront?
>
> Best,
> René

Hello Meinolf,

yes both DCs are also DNS servers (AD Integrated). I configured only the
loopback up address 127.0.0.1 on each server. I will try the DNS
configuration you sugested.
I will try that and report back.

Thanks for the support.

Best regards
René Heinze

"Meinolf Weber [MVP-DS]" wrote:

> Hello Rene,
>
> Are both DCs also DNS server? If not install it also on the second one, use
> AD integrated zones and configure both of them to use the other DNS server
> as secondary on the NIC. Use the real ip addresses and not the loopback ip
> address 127.0.0.1
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>
> > Hello,
> >
> > I installed two domain controller in two different subnets connected
> > with a router (no firewall rules). Both domain controllers are members
> > of the first default ad site. When I change the name of the default ad
> > site and restart the dc-b everything is ok. Then i restart dc-a, the
> > dc takes forever to start and the ad and the depending services have
> > trouble to start. I did the procedure in two different test
> > environments. In both cases the same result on dc-a.
> >
> > What did i do wront?
> >
> > Best,
> > René
>
>
> .
>

"Rene Heinze" <ReneHeinze@discussions.microsoft.com> wrote in message
news:F8DAD59B-D585-41C7-AA04-E578878A1D08@microsoft.com...
> Hello Meinolf,
>
> yes both DCs are also DNS servers (AD Integrated). I configured only the
> loopback up address 127.0.0.1 on each server. I will try the DNS
> configuration you sugested.
> I will try that and report back.
>
> Thanks for the support.
>
> Best regards
> René Heinze
>

In addition, I would suggest to not to restart a DC directly after you
change Site configuration. The best suggestion is to re-start the netlogon
service and AD services. This way the change will go into DNS sooner. If you
restarted a DC after such a change, and the one DC registered it on itself,
AD may have not replicated the change yet to the other DC that's restarting,
so upon restart, it's view of DNS hasn't been updated yet. Of course this
all depends on timing and how fast you restarted it.

As Meinolf said, let's not use the loopback. :-)


--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

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

If you feel this is an urgent issue and require immediate assistance, please
contact Microsoft PSS directly. Please check http://support.microsoft.com
for regional support phone numbers.

Everything is working now. Thanks for you quick support!

Best,
René Heinze

"Rene Heinze" wrote:

> Hello Meinolf,
>
> yes both DCs are also DNS servers (AD Integrated). I configured only the
> loopback up address 127.0.0.1 on each server. I will try the DNS
> configuration you sugested.
> I will try that and report back.
>
> Thanks for the support.
>
> Best regards
> René Heinze
>
> "Meinolf Weber [MVP-DS]" wrote:
>
> > Hello Rene,
> >
> > Are both DCs also DNS server? If not install it also on the second one, use
> > AD integrated zones and configure both of them to use the other DNS server
> > as secondary on the NIC. Use the real ip addresses and not the loopback ip
> > address 127.0.0.1
> >
> > Best regards
> >
> > Meinolf Weber
> > Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> > no rights.
> > ** Please do NOT email, only reply to Newsgroups
> > ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
> >
> >
> > > Hello,
> > >
> > > I installed two domain controller in two different subnets connected
> > > with a router (no firewall rules). Both domain controllers are members
> > > of the first default ad site. When I change the name of the default ad
> > > site and restart the dc-b everything is ok. Then i restart dc-a, the
> > > dc takes forever to start and the ad and the depending services have
> > > trouble to start. I did the procedure in two different test
> > > environments. In both cases the same result on dc-a.
> > >
> > > What did i do wront?
> > >
> > > Best,
> > > René
> >
> >
> > .
> >

"Rene Heinze" <ReneHeinze@discussions.microsoft.com> wrote in message
news:9403DEA1-D084-4F4E-9D3E-3C3BDD889C33@microsoft.com...
> Everything is working now. Thanks for you quick support!
>
> Best,
> René Heinze
>

Good to hear. :-)

Ace