AD Integ Zone Conversion Problem

  • Thread starter Thread starter Skidmore
  • Start date Start date
S

Skidmore

I've created an AD Integrated Zone on one of my DCs and
the information has replicated to AD on my other DC which
is also running DNS. However, the zone only appears in
the DNS mmc as running on the first server. The second DC
is pointing to the first for DNS and registered itself
correctly. Should I now "create" the AD Integrated Zone
on the second DC as well? or should this have happened on
its own.

Thanks for your help.
 
In
Skidmore said:
I've created an AD Integrated Zone on one of my DCs and
the information has replicated to AD on my other DC which
is also running DNS. However, the zone only appears in
the DNS mmc as running on the first server. The second DC
is pointing to the first for DNS and registered itself
correctly. Should I now "create" the AD Integrated Zone
on the second DC as well? or should this have happened on
its own.

Thanks for your help.
Click to expand...

Did you add the NS record for the second DC to the zone properties?
 
Also, the working DNS server is reporting event ID 9999
saying errors were experienced and that there are related
messages in the logs, but there are no related error
messages in the logs. I'm assuming that this is because
the second DC is not responding to requests for
communication about the zone. I'm really stumped.
 
In
Skidmore said:
Also, the working DNS server is reporting event ID 9999
saying errors were experienced and that there are related
messages in the logs, but there are no related error
messages in the logs. I'm assuming that this is because
the second DC is not responding to requests for
communication about the zone. I'm really stumped.
Click to expand...

What events are being logged immediately preceding and following the 9999?
 
Just an Evnet ID 6001 saying the zone transfer to an old
NT 40 secondary that I'm running was successful. There
are no other warnings or error messages and I only get the
9999 every few hours.
 
In
Skidmore said:
Just an Evnet ID 6001 saying the zone transfer to an old
NT 40 secondary that I'm running was successful. There
are no other warnings or error messages and I only get the
9999 every few hours.
Click to expand...
They may not be errors or warning they could be just information events.
I will get one if I'm making a lot of changes in a zone and DNS will log a
runtime event warning if I make a lot of changes in a short time.
 
In (e-mail address removed) <[email protected]>
posted a question
Then Kevin replied below:
So, back to my original problem, any idea what I've done
wrong?
Click to expand...
That is why I wanted to see the events, if you have done as you said, which
is create an AD integrated zone in DNS on one DC, then added an NS record
for the second DC, the zone should have replicated and just "appeared" in
the second DC within about 15 minutes.
And to verify it the time it took I created an AD zone on one of my DCs
added the NS record for the second DC, without any further action on my part
other than hitting refresh it took almost exactly 15 minutes for the zone to
appear on my other DC.

So if you did just as I said you did every thing right. You really cannot do
it wrong, it is sorta like riding a bike, it just happens, you turn the
pedals and if the chain is connected, you go.
That does not mean that your DCs are configured right or that something is
not blocking replication, I cannot say because I cannot see your monitor or
your setup.
I would need to see an ipconfig /all from both machines.
You need to run dcdiag /e /v from both machines and look for an error
somewhere.
 
In
Skidmore said:
Also, the working DNS server is reporting event ID 9999
saying errors were experienced and that there are related
messages in the logs, but there are no related error
messages in the logs. I'm assuming that this is because
the second DC is not responding to requests for
communication about the zone. I'm really stumped.
Click to expand...

If you delete the zone on the second DC/DNS server, then recreate it, then
make it AD Integrated, the zone should appear immediately because it's
already stored in the AD database, hence the term AD Integrated. I don't see
why the second DNS server does not show you the same exact zone data the
first one has, since the data is exactly the same and being replicated by
AD's replication topology, provided both DCs are in the same domain (W2k
only).


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
In
Skidmore said:
So any ideas on why my second DC/DNS won't service the
zone?
Click to expand...

See my reply above.

Also,
Even though NT4 is supposedly able to support SRV records, I've seen issues
with this. If possible, suggest to retire the NT4 DNS server.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top