| Author |
Message |
Cris
Guest
|
 Posted:
Thu Nov 10, 2005 5:50 pm Post subject:
Mess in my root namespace after promoting zone to AD Integra |
|
|
Hi,
I'm having trouble after migrating a primary dns zone to active directory
integrated.
Before: private namespace is mycompany.local
DC1 - W2K SP4 - DNS (primary) - DHCP - all FSMO roles
DC2 - W2K SP4 - DNS (secondary) - DHCP (different scope from DC1)
No errors in DNS eventlog.
--> I upgraded mycompany.local zone to active directory integrated to get
benefists of multimaster replication:
everything went fine on DC1, so I had a fresh copy of text dns file
transformed into system\MicrosoftDNS\mycompany.local branch of AD.
--> I forced AD replication in AD Sites And Services to DC2.
Still good, but DNS on DC2 was still saying "secondary" as its own
description after1h.
--> I ended up to change secondary zone to active dir integrated on 2nd DC
(I know, this is nonsense), and DNS Mgmt Tool prompted "a zone
mycompany.local already exist in AD, what you want to do: delete zone in AD
and populate with source or take existing": I opted for the second choice.
Panic: zone mycompany.local disappeared from DC2; after restarting DNS on
DC1, even the first one was gone(!)
Panic2: what can I do?
I restored text file and create zone as before (primary on DC1 and secondary
on DC2).
now
----
0) everything works fine (DHCP, name resolution, recursion, forwarding, ecc)
1) records still exist in AD;
2) I rebooted DC2 and once again zone mycompany.local was gone; I recreated
the zone as secondary and "tranfer from master" works;
3) I'm scared of rebooting DC1.
After all, can I still make a clean reliable DDNS implementation of
mycompany.local in both servers?
AD Integrated would be preferred. Article Q294328 was not so clear to me.
I Need help.
Thank you in advance |
|
| Back to top |
|
 |
Ace Fekay [MVP]
Guest
|
| Posted:
Fri Nov 11, 2005 9:50 am Post subject:
Re: Mess in my root namespace after promoting zone to AD Int |
|
|
In news:D2F3D8B2-969D-42C9-910E-1A475DD11455@microsoft.com,
Cris <cris@discussion.microsoft.com> made this post, which I then commented
about below:
| Quote: | Hi,
I'm having trouble after migrating a primary dns zone to active
directory integrated.
Before: private namespace is mycompany.local
DC1 - W2K SP4 - DNS (primary) - DHCP - all FSMO roles
DC2 - W2K SP4 - DNS (secondary) - DHCP (different scope from DC1)
No errors in DNS eventlog.
--> I upgraded mycompany.local zone to active directory integrated to
get benefists of multimaster replication:
everything went fine on DC1, so I had a fresh copy of text dns file
transformed into system\MicrosoftDNS\mycompany.local branch of AD.
--> I forced AD replication in AD Sites And Services to DC2.
Still good, but DNS on DC2 was still saying "secondary" as its own
description after1h.
--> I ended up to change secondary zone to active dir integrated on
2nd DC (I know, this is nonsense), and DNS Mgmt Tool prompted "a zone
mycompany.local already exist in AD, what you want to do: delete zone
in AD and populate with source or take existing": I opted for the
second choice.
Panic: zone mycompany.local disappeared from DC2; after restarting
DNS on DC1, even the first one was gone(!)
Panic2: what can I do?
I restored text file and create zone as before (primary on DC1 and
secondary on DC2).
now
----
0) everything works fine (DHCP, name resolution, recursion,
forwarding, ecc) 1) records still exist in AD;
2) I rebooted DC2 and once again zone mycompany.local was gone; I
recreated the zone as secondary and "tranfer from master" works;
3) I'm scared of rebooting DC1.
After all, can I still make a clean reliable DDNS implementation of
mycompany.local in both servers?
AD Integrated would be preferred. Article Q294328 was not so clear to
me.
I Need help.
Thank you in advance
|
After making the first zone on DC1 AD Integrated, all you had to do was go
to DC2, delete the secondary zone, wait and be patient and the AD zone would
magically appear.
If it's a secondary, delete that zone from DC2. Then change the zone on DC1
to AD Integrated. Then wait...
--
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
If this post is viewed at a non-Microsoft community website, and you were to
respond to it through that community's website, I may not see your reply
unless that website posts replies back to the original Microsoft forum.
Therefore, please direct all replies ONLY to the Microsoft public newsgroup
this thread originated in so all can benefit or ensure the web community
posts it back to the original forum.
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Windows Server Directory Services
Microsoft Certified Trainer
Infinite Diversities in Infinite Combinations.
================================= |
|
| Back to top |
|
|
Cris
Guest
|
| Posted:
Fri Nov 11, 2005 1:50 pm Post subject:
Re: Mess in my root namespace after promoting zone to AD Int |
|
|
Just to be sure I'll do the right thing:
promoting zone in DC1 to AD Integrated will probably ask me:
"A zone already exists in AD with name mycompany.local. Keep existing or
delete and reload from text file?"
I thing that the second choice is the right one. Am I wrong?
Thank you.
"Ace Fekay [MVP]" wrote:
| Quote: | In news:D2F3D8B2-969D-42C9-910E-1A475DD11455@microsoft.com,
Cris <cris@discussion.microsoft.com> made this post, which I then commented
about below:
Hi,
I'm having trouble after migrating a primary dns zone to active
directory integrated.
Before: private namespace is mycompany.local
DC1 - W2K SP4 - DNS (primary) - DHCP - all FSMO roles
DC2 - W2K SP4 - DNS (secondary) - DHCP (different scope from DC1)
No errors in DNS eventlog.
--> I upgraded mycompany.local zone to active directory integrated to
get benefists of multimaster replication:
everything went fine on DC1, so I had a fresh copy of text dns file
transformed into system\MicrosoftDNS\mycompany.local branch of AD.
--> I forced AD replication in AD Sites And Services to DC2.
Still good, but DNS on DC2 was still saying "secondary" as its own
description after1h.
--> I ended up to change secondary zone to active dir integrated on
2nd DC (I know, this is nonsense), and DNS Mgmt Tool prompted "a zone
mycompany.local already exist in AD, what you want to do: delete zone
in AD and populate with source or take existing": I opted for the
second choice.
Panic: zone mycompany.local disappeared from DC2; after restarting
DNS on DC1, even the first one was gone(!)
Panic2: what can I do?
I restored text file and create zone as before (primary on DC1 and
secondary on DC2).
now
----
0) everything works fine (DHCP, name resolution, recursion,
forwarding, ecc) 1) records still exist in AD;
2) I rebooted DC2 and once again zone mycompany.local was gone; I
recreated the zone as secondary and "tranfer from master" works;
3) I'm scared of rebooting DC1.
After all, can I still make a clean reliable DDNS implementation of
mycompany.local in both servers?
AD Integrated would be preferred. Article Q294328 was not so clear to
me.
I Need help.
Thank you in advance
After making the first zone on DC1 AD Integrated, all you had to do was go
to DC2, delete the secondary zone, wait and be patient and the AD zone would
magically appear.
If it's a secondary, delete that zone from DC2. Then change the zone on DC1
to AD Integrated. Then wait...
--
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
If this post is viewed at a non-Microsoft community website, and you were to
respond to it through that community's website, I may not see your reply
unless that website posts replies back to the original Microsoft forum.
Therefore, please direct all replies ONLY to the Microsoft public newsgroup
this thread originated in so all can benefit or ensure the web community
posts it back to the original forum.
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Windows Server Directory Services
Microsoft Certified Trainer
Infinite Diversities in Infinite Combinations.
=================================
|
|
|
| Back to top |
|
|
Ace Fekay [MVP]
Guest
|
| Posted:
Sat Nov 12, 2005 1:50 am Post subject:
Re: Mess in my root namespace after promoting zone to AD Int |
|
|
In news:58BE107F-D524-4B29-9C52-2DCCC2096C1A@microsoft.com,
Cris <cris@discussion.microsoft.com> made this post, which I then commented
about below:
| Quote: | Just to be sure I'll do the right thing:
promoting zone in DC1 to AD Integrated will probably ask me:
"A zone already exists in AD with name mycompany.local. Keep existing
or delete and reload from text file?"
I thing that the second choice is the right one. Am I wrong?
Thank you.
|
You had it reversed in the original post. If DC2 is already hosting the zone
as AD Integrated, then just delete the secondary on DC1 and wait. If DC2 is
hosting the secondary zone, then delete the zone on DC2, then wait.
If you are getting that message, then tell it to keep the existing zone in
AD.
Ace |
|
| Back to top |
|
|
Cris
Guest
|
| Posted:
Sat Nov 12, 2005 1:50 pm Post subject:
Re: Mess in my root namespace after promoting zone to AD Int |
|
|
What I did was:
1) DNS network properties of DC2 switched to DC1
2) delete sec zone mycompany.local of DC2
3) switch primary DC1 to AD integrated (reload zone from fresh data)
4) wait...
5) everything was and is ok
6) reverted network properties of DC2 to point to itself.
Thank you for you clean and quick help.
Cris
"Ace Fekay [MVP]" wrote:
| Quote: | In news:58BE107F-D524-4B29-9C52-2DCCC2096C1A@microsoft.com,
Cris <cris@discussion.microsoft.com> made this post, which I then commented
about below:
Just to be sure I'll do the right thing:
promoting zone in DC1 to AD Integrated will probably ask me:
"A zone already exists in AD with name mycompany.local. Keep existing
or delete and reload from text file?"
I thing that the second choice is the right one. Am I wrong?
Thank you.
You had it reversed in the original post. If DC2 is already hosting the zone
as AD Integrated, then just delete the secondary on DC1 and wait. If DC2 is
hosting the secondary zone, then delete the zone on DC2, then wait.
If you are getting that message, then tell it to keep the existing zone in
AD.
Ace
|
|
|
| Back to top |
|
|
Ace Fekay [MVP]
Guest
|
| Posted:
Sat Nov 12, 2005 5:50 pm Post subject:
Re: Mess in my root namespace after promoting zone to AD Int |
|
|
In news:4139880B-3D9C-4039-9068-423D13C3E756@microsoft.com,
Cris <cris@discussion.microsoft.com> made this post, which I then commented
about below:
| Quote: | What I did was:
1) DNS network properties of DC2 switched to DC1
2) delete sec zone mycompany.local of DC2
3) switch primary DC1 to AD integrated (reload zone from fresh data)
4) wait...
5) everything was and is ok
6) reverted network properties of DC2 to point to itself.
Thank you for you clean and quick help.
Cris
|
You are welcome. Good to hear you got it straightened out!
Ace |
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in