My DNS is Really Confused stiill

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

James W. Long

Dear All:


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 anymore.
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 the 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:


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..
Click to expand...
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?
Click to expand...

I can see that you are really worried about this, sorry I've been really
busy the last few days and was unable to read the groups.

That said, don't confuse FSMO roles with what is on the SOA record as the
primary name server.
All Active Directory integrated zones have themselves as Primary name
servers on the SOA tab.
 
Dear Kevin:

Great, thank you once again. I won't worry about it.
I demoted the first dc out and removed active directory
from it and it went away like a charm.

An interesting side effect - network neightborhood
then became slow on all clients and the server dc and
the (now)member server. I even went as far as to
disjoin the member server from the domain and the
problem remained until I unshared and reshared
all network shares.

Everything is working as expected and been running
clean since. Slick.

Thank you for you help again Kevin,
Always a pleasure.

James W. Long
 
Back
Top