AD integrated - different SOA.

[Jason]

Hello,

I have a simple network set up comprised of one domain,
DOMAIN.com, that has two AD servers - SERVER1 and
SERVER2. When I installed Win2K server I allwoed setup
to automatically install and configure DNS. When I went
into the DNS MMC and had a look at the configuration I
noticed that the SOA for SERVER1 was SERVER1 and the SOA
on SERVER2 was SERVER2. Why? I thought that there is
only one SOA for a domain.

Thanks in advance.

 

[Ace Fekay [MVP]]

Hello,

I have a simple network set up comprised of one domain,
DOMAIN.com, that has two AD servers - SERVER1 and
SERVER2. When I installed Win2K server I allwoed setup
to automatically install and configure DNS. When I went
into the DNS MMC and had a look at the configuration I
noticed that the SOA for SERVER1 was SERVER1 and the SOA
on SERVER2 was SERVER2. Why? I thought that there is
only one SOA for a domain.

Thanks in advance.

That is default SOA and serial number behavior with using AD Integrated
zones. When a machine will update itself (assuming you are pointing
toyourself, which is what it looks like based on your description) then the
update made into that server will make it now the SOA. When an update goes
to the other, then that's the SOA and so forth. This is especially true
since AD Integrated zones follow a mutli master design.

I wouldn't worry about it. There's an article explaining this, but I do not
have it with me (it's at home) at this time since I'm in the office at the
moment. If you need the article, post back and I can dig it up later.

Otherwise, it's basically the way it works. If you're not comfortable wtih
that, change one of them to a secondary zone and pull zone from the other
one.

--
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