Bringing a Win2K DNS server into a Win2003 Domain ?

  • Thread starter Thread starter Bubba Thomas
  • Start date Start date
B

Bubba Thomas

I have just created a new domain using Win2K3 servers. I have 3 DCs ALL
running DNS (needed because 2 of the DCs are MSMQ servers). My OLD domain
received its DNS services from a Win2K DNS server. How can I bring / get the
DNS information from the Win2K machine into the Win2K3 domain ?



Bubba !
 
Probably the easiest way is to do a zone transfer between the two machines.
Once the zone has transfered onto the new W2k3 DNS server, you can then make
the zone AD Integrated or Primary, whichever you choose.

--
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
 
I set the new Win2003 Server up as a secondary DNS server and allowed the
Win2000 DNS server to transfer the zone over to the secondary. I am now
trying to promote the Win2K machine but it will not let me. I get the
following error:

The Domain MyDomain.com cannot be contacted. Ensure that the DNS domain name
is typed correctly..........

I found a MS Win2000 web page that describes how to troubleshoot this
problem. The have a few issues with what they want me to do .... for the
following reasons.


They say to look for MisMatched (disjointed) Namespace
I have checked this and found that the Win2K machine has the following:
FULL COMPUTER MANE: DNSSERVER . (the period was spaced out so you can see
it)
DOMAIN NAME: OLDDOMAINNAME

One thing is the Win2K machine still holds the OLD Domain name. Should I
drop this from the old domain and then re-add it ? I am afraid if I do
this I will create problems with all the current client machines that are
pointing to the OLDDOMAINNAME domain. I did not disconnect and reconnect
them either. Is tthis something I will need to do before I can get this mess
fixed ?


ThanX for your help !

Bubba !





"Ace Fekay [MVP]"
 
Inline below...

In
Bubba Thomas said:
I set the new Win2003 Server up as a secondary DNS server and allowed
the Win2000 DNS server to transfer the zone over to the secondary. I
am now trying to promote the Win2K machine but it will not let me. I
get the following error:

The Domain MyDomain.com cannot be contacted. Ensure that the DNS
domain name is typed correctly..........
Click to expand...

Normally a DNS issue. Using your ISP's DNS addresses in your machine's IP
properties is usually the culprit unless this along with other issues, can
compound your problems.
I found a MS Win2000 web page that describes how to troubleshoot this
problem. The have a few issues with what they want me to do .... for
the following reasons.

They say to look for MisMatched (disjointed) Namespace
I have checked this and found that the Win2K machine has the
following: FULL COMPUTER MANE: DNSSERVER . (the period was spaced
out so you can see it)
DOMAIN NAME: OLDDOMAINNAME
Click to expand...

You've got more than a zone transfer problem. The single label DNS domain
name is a big problem, but can be fixed by reading this link:
http://support.microsoft.com/?id=300684

A Disjointed Namespace is where the Primary DNS Suffix does not match the AD
DNS Domain name.
An ipconfig /all will show you the Primary DNS Suffix. Check your Acticve
Directory Users and Computers console. What name shows up in the top of the
tree? That is your AD DNS Domain name. That MUST match the Primary DNS
Suffix.
One thing is the Win2K machine still holds the OLD Domain name.
Should I drop this from the old domain and then re-add it ?
Click to expand...

Not sure because I do not know you;re whole scenario and your intentions.
Your post is hinting at certain issues and what your results are, but I do
not know what you are trying to do.
I am
afraid if I do this I will create problems with all the current
client machines that are pointing to the OLDDOMAINNAME domain. I did
not disconnect and reconnect them either.
Click to expand...

I do not understand your terminology here. What do you mean by disconnect
and reconnect?

Is this something I will
need to do before I can get this mess fixed ?
Click to expand...

We will need much more information on what you're trying to achieve.

ThanX for your help !

Bubba !
Click to expand...


--
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
 
Sorry for not being so clear Ace...

Basically I am trying to upgrade our whole domain from an NT4 domain to a
Win2003 Domain.

I did an upgrade to our PDC (from NT4 to Win2K3). The only thing the 2003 DC
does is authentication and Wins. We had another stand alone server that was
doing internal DNS for us which is running Win2K. I have tried to promote
the Win2K server to a DC but I am not able to because of the errors I stated
before. I need to clear up the errors because they are preventing an
application from running. Apparently the application is trying to do
something within AD and or DNS which it is not being allowed to do (funny
thing is this application problem only happens on XP machines and not Win2K
machines). All the errors that are returned indicate DNS issues.



Bubba !





"Ace Fekay [MVP]"
 
Ok, that sounds a little clearer. Basically, the cardinal rule with AD is
only use your internal DNS server(s) that host the AD DNS domain name. Can
you provide an ipconfig /all from the server and one of the clients? That
can help to steer us in the right direction.

Thanks

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

Bubba Thomas said:
Sorry for not being so clear Ace...

Basically I am trying to upgrade our whole domain from an NT4 domain to a
Win2003 Domain.

I did an upgrade to our PDC (from NT4 to Win2K3). The only thing the 2003 DC
does is authentication and Wins. We had another stand alone server that was
doing internal DNS for us which is running Win2K. I have tried to promote
the Win2K server to a DC but I am not able to because of the errors I stated
before. I need to clear up the errors because they are preventing an
application from running. Apparently the application is trying to do
something within AD and or DNS which it is not being allowed to do (funny
thing is this application problem only happens on XP machines and not Win2K
machines). All the errors that are returned indicate DNS issues.



Bubba !





"Ace Fekay [MVP]"
Inline below...

In

Normally a DNS issue. Using your ISP's DNS addresses in your machine's IP
properties is usually the culprit unless this along with other issues, can
compound your problems.


You've got more than a zone transfer problem. The single label DNS domain
name is a big problem, but can be fixed by reading this link:
http://support.microsoft.com/?id=300684

A Disjointed Namespace is where the Primary DNS Suffix does not match
Click to expand...
the
Click to expand...
 
Here you go.... BTW.... IP addresses and domain names have been changed to
protect the innocent ! : )

Bubba !


Client Machine:

Windows IP Configuration

Host Name . . . . . . . . . . . . . . . . .: atn007
Primary Dns Suffix . . . . . . . . . .: mydomain.com
Node Type . . . . . . . . . . . . . . . . .: Hybrid
IP Routing Enabled . . . . . . . . . .: No
Wins Proxy Enabled . . . . . . . . . : No
DNS Suffix Search List . . . . . . . : mydomain.com

Ethernet adapter Local Area COnnection:
Connection-specific DNS Suffix . . :
Description . . . . . . . . . . . . . . . . . . : 3Com Etherlink
10/100 PCI for Complete PC Management NIC (3C905C-TX)
Physical Address . . . . . . . . . . . . . : 00-01-03-1A-CC-DC
DHCP Enabled . . . . . . . . . . . . . . . : No
IP Address . . . . . . . . . . . . . . . . . . . : 129.110.204.7
Subnet Mask . . . . . . . . . . . . . . . . . .: 255.255.0.0
Default Gateway . . . . . . . . . . . . . . : 129.110.100.150
DNS Servers . . . . . . . . . . . . . . . . . . : 129.110.0.4
Primary WINS Server . . . . . . . . . . . : 129.110.0.5



DNS Server / Domain Controller

Windows IP Configuration

Host Name . . . . . . . . . . . . . . . . .: atndc1
Primary Dns Suffix . . . . . . . . . .: mydomain.com
Node Type . . . . . . . . . . . . . . . . .: Hybrid
IP Routing Enabled . . . . . . . . . .: No
Wins Proxy Enabled . . . . . . . . . : No
DNS Suffix Search List . . . . . . . : mydomain.com

Ethernet adapter Local Area COnnection:
Connection-specific DNS Suffix . . :
Description . . . . . . . . . . . . . . . . . . : 3Com Etherlink
10/100 PCI for Complete PC Management NIC (3C905C-TX)
Physical Address . . . . . . . . . . . . . : 00-50-8B-10-CA-0C
DHCP Enabled . . . . . . . . . . . . . . . : No
IP Address . . . . . . . . . . . . . . . . . . . : 129.110.0.4
Subnet Mask . . . . . . . . . . . . . . . . . .: 255.255.0.0
Default Gateway . . . . . . . . . . . . . . : 129.110.100.150
DNS Servers . . . . . . . . . . . . . . . . . . : 127.0.0.1
Primary WINS Server . . . . . . . . . . . : 129.110.0.5



"Ace Fekay [MVP]"
Ok, that sounds a little clearer. Basically, the cardinal rule with AD is
only use your internal DNS server(s) that host the AD DNS domain name. Can
you provide an ipconfig /all from the server and one of the clients? That
can help to steer us in the right direction.

Thanks

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

Bubba Thomas said:
Sorry for not being so clear Ace...

Basically I am trying to upgrade our whole domain from an NT4 domain to a
Win2003 Domain.

I did an upgrade to our PDC (from NT4 to Win2K3). The only thing the
Click to expand...
2003
DC
does is authentication and Wins. We had another stand alone server that was
doing internal DNS for us which is running Win2K. I have tried to promote
the Win2K server to a DC but I am not able to because of the errors I stated
before. I need to clear up the errors because they are preventing an
application from running. Apparently the application is trying to do
something within AD and or DNS which it is not being allowed to do (funny
thing is this application problem only happens on XP machines and not Win2K
machines). All the errors that are returned indicate DNS issues.



Bubba !





"Ace Fekay [MVP]"
the of
the
Click to expand...
I
Click to expand...
 
Just to insert a note, a good idea is to always use a non-internet name
space internally

example - mycompany.local

it's not always needed but generally a good idea. :)

--

Brian Oakes

This posting is provided "AS IS" with no warranties and confers no rights.
Please reply to the newsgroup so that others may benefit.
"Ace Fekay [MVP]"
Ok, that sounds a little clearer. Basically, the cardinal rule with AD is
only use your internal DNS server(s) that host the AD DNS domain name. Can
you provide an ipconfig /all from the server and one of the clients? That
can help to steer us in the right direction.

Thanks

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

Bubba Thomas said:
Sorry for not being so clear Ace...

Basically I am trying to upgrade our whole domain from an NT4 domain to a
Win2003 Domain.

I did an upgrade to our PDC (from NT4 to Win2K3). The only thing the
Click to expand...
2003
DC
does is authentication and Wins. We had another stand alone server that was
doing internal DNS for us which is running Win2K. I have tried to promote
the Win2K server to a DC but I am not able to because of the errors I stated
before. I need to clear up the errors because they are preventing an
application from running. Apparently the application is trying to do
something within AD and or DNS which it is not being allowed to do (funny
thing is this application problem only happens on XP machines and not Win2K
machines). All the errors that are returned indicate DNS issues.



Bubba !





"Ace Fekay [MVP]"
the of
the
Click to expand...
I
Click to expand...
 
In
Bubba Thomas said:
Here you go.... BTW.... IP addresses and domain names have been
changed to protect the innocent ! : )
Click to expand...

If you are changing the IP address to protect the innocent then why did you
use an IP address that belongs to the University of Dallas?
Or if this is actually the internal IP addresses you are using, then that in
itself will cause problems.
That being said your DC should use its own IP for DNS not the 127.0.0.1
loopback address.
Does the actual DNS name for the Primary DNS suffix match the name in ADUC?
Do you have a forward lookup zone in DNS for that name?
 
Why do you feel this way ? Nothing personal but just telling me something
counts for nothing without reasoning.


Bubba !
 
the reason is..... :)

Otherwise you "could" have a conflicting namespace. Example....

at your ISP they host mycompany.com. You host mycompany.com. As far as your
local users are concerned your internal mycompany.com is authoritative for
the real (external) mycompany.com hence they would never query external
records. So you would have to maintain additional static external records in
your internal zone of mycompany.com

If one is .com the other is .local then you don't have this conflict.

Better? :)
--

Brian Oakes

This posting is provided "AS IS" with no warranties and confers no rights.
Please reply to the newsgroup so that others may benefit.
 
Hence, also called, if inadvertenly created the same name zone, an
unintentional Split Horizon Namespace!
:-)

--
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
 
Also to add, after the 127.0.0.1 is changed to 129.110.0.4 (going by the
numbers that were given), and verifying that mydomain.com is the name of
AD's DNS domain name, then we need to verify that the SRV records have been
created. When joining, it looks for these records to "Find" the domain.

241515 - How to Verify the Creation of SRV Records for a Domain Controller:
http://support.microsoft.com/?id=241515

--
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
 
OK.. Makes sense... I hope you were not thinking I am questioning your
abilities here... I am just a noobie and I did not really know the REASON
why one should do that !


ThanX

Bubba !
 
Back
Top