My DNS is confused

  • Thread starter Thread starter James W. Long
  • Start date Start date
J

James W. Long

Dear All
recently I Added a win2k3 dc to my win2k dc in order
to dcpromo the win2k dc out.

I tranferred all the roles to the win2k3 dc.

now when I look in dns,

the win2k dc is the SOA again.

the "dc" folder under _msdcs is the win2k3 dc.
the "gc" folder under _msdcs is the win2k3 dc

I want the "primary server" to be the win2k3 machine,
so I can dcpromo the win2k server gone.


do I need to edit the SOA record and fix this up manually?

Thank you,

James Long
 
Dear All:

ok, let me clarify better.

I'm trying to dcpromo the first win2k dc out and
have added a new win2k3 dc to replace it with,
so I have win2k.domain.org and win2k3.domain.org.


I transfered six roles to a new win2k3 dc,
rid,pdc,infrastructure,domain naming,
schema master and global catalog.
both dc's can still look into active directory
and both agree on all 6 roles
being on the new win2k3 dc.

but. DNS is not correct because,
running dns manager on the first win2k
dc, the SOA is himself;

and running dns manger on the new win2k3
shows the SOA is HIMSelf... err..

which HIMSELF is it?
its supposed to be the new win2k3 now,
thats how I hope(ed) to see it on either DC.

so DNS is NOT identical on both DC's.
its like active directory localized dns for each dc.
it's like the old win2k dc does not want to give it up,
and will only see himself as SOA;
the win2k dc does have the win2k3 dc as "pdc" and "gc" under _msdcs.

(gosh a screen shot would be nice here eh???)



more info:

the dns servers in thier respective dns managers, ( there are two unique
versions as I said above)
see all clients ip's and thier own ip's correctly in both the forward and
reverse zones for the domain. there is only one domain.


The old win2k dc has 0.0.10.in-addr.arpa, 0.in-addr.arpa, 127.in-addr.arpa
and 255.in-addr.arpa zones, and after selecting "view advanced" these zones
were then visable in the win2k3 dc dns manager. the difference being this:
on win2k the 0.0.10.in-addr.arpa zone has both dc's but win2k is SOA.
on win2k3 the 0.0.10.in-addr.arpa zone has both dc's but win2k3 is SOA.
in all remaining reverse lookup zones the SOA is the DC that DNS runs on
respectively.


The new win2k3 dc has itself as the only dns server in tcpip properties,
and the old win2k dc has the new win2k3 dc as its only dns server in tcpip
properties. forwarders are defined only on the new win2k3 dc. the clients
all have the new win2k3 dc as thier only dns server.


a simple and a recursive dns query passes on both dc's.

They have been running side by side replicating like rabbits with no
problem.

what have I done wrong and why is there a difference seen in the DNS manger
on the two
DNS servers, especially where the SOA record is concerned?


do I have to dcpromo the old one out to clear this up,
- or I hope - can I straighten DNS out before this is done?

am I in the right forum or should I be in a frs forum?
or active directory... .. not sure. you guys are really sharp
in here and thats why I came here.

Thank you again,

James W. Long
 
James said:
Dear All:

ok, let me clarify better.

I'm trying to dcpromo the first win2k dc out and
have added a new win2k3 dc to replace it with,
so I have win2k.domain.org and win2k3.domain.org.


I transfered six roles to a new win2k3 dc,
rid,pdc,infrastructure,domain naming,
schema master and global catalog.
both dc's can still look into active directory
and both agree on all 6 roles
being on the new win2k3 dc.

but. DNS is not correct because,
running dns manager on the first win2k
dc, the SOA is himself;

and running dns manger on the new win2k3
shows the SOA is HIMSelf... err..

which HIMSELF is it?
its supposed to be the new win2k3 now,
thats how I hope(ed) to see it on either DC.

so DNS is NOT identical on both DC's.
its like active directory localized dns for each dc.
it's like the old win2k dc does not want to give it up,
and will only see himself as SOA;
the win2k dc does have the win2k3 dc as "pdc" and "gc" under _msdcs.

(gosh a screen shot would be nice here eh???)



more info:

the dns servers in thier respective dns managers, ( there are two
unique versions as I said above)
see all clients ip's and thier own ip's correctly in both the forward
and reverse zones for the domain. there is only one domain.


The old win2k dc has 0.0.10.in-addr.arpa, 0.in-addr.arpa,
127.in-addr.arpa and 255.in-addr.arpa zones, and after selecting
"view advanced" these zones were then visable in the win2k3 dc dns
manager. the difference being this: on win2k the 0.0.10.in-addr.arpa
zone has both dc's but win2k is SOA.
on win2k3 the 0.0.10.in-addr.arpa zone has both dc's but win2k3 is
SOA.
in all remaining reverse lookup zones the SOA is the DC that DNS runs
on respectively.


The new win2k3 dc has itself as the only dns server in tcpip
properties, and the old win2k dc has the new win2k3 dc as its only
dns server in tcpip properties. forwarders are defined only on the
new win2k3 dc. the clients all have the new win2k3 dc as thier only
dns server.


a simple and a recursive dns query passes on both dc's.

They have been running side by side replicating like rabbits with no
problem.

what have I done wrong and why is there a difference seen in the DNS
manger on the two
DNS servers, especially where the SOA record is concerned?


do I have to dcpromo the old one out to clear this up,
- or I hope - can I straighten DNS out before this is done?

am I in the right forum or should I be in a frs forum?
or active directory... .. not sure. you guys are really sharp
in here and thats why I came here.

Thank you again,

James W. Long
Click to expand...
No.

An Active Directory integrated zone will always show itself as the SOA
Primary, this has more to do with where dynamic updates go than anything
else. When a dynamic update is sent to DNS, it goes to the Primary Name
server (MNAME) listed on the SOA record.
 
Back
Top