DNS Server setup

  • Thread starter Thread starter Donatas Grasys
  • Start date Start date
D

Donatas Grasys

Hello,

We have three W2000 DC's on a single domain. My aim is to bring in a
new 2003 server, make it a DC (and promote two other 2003 servers we
already have) AND somewhere in the process demote the W2k DC's to
member servers.

I've done adprep /forestprep adprep /domainprep
I've promoted my Windows 2003 server.
Installed DNS server from add/remove programs in control panel.
Now am stucked with DNS. I tried to run netdiag command. and I got warning
in the middle of the log :

[WARNING] Cannot find a primary authoritative DNS server for the name
'Typhon.burgessfurniture.com.'. [ERROR_TIMEOUT]
The name 'Typhon.burgessfurniture.com.' may not be registered in
DNS

I am trying to sort it out, but I am not sure where to start. Maybe I have
to trasfer all the DNS records from my old windows 2000 server to windows
2003 or I have to setup secondary zone.
I tried doing that http://support.microsoft.com/kb/323383, but I got
error - The zone cannot be created. The zone allready exists.


If you could possibly give me any directions about DNS setup.

Regards
 
In
Donatas Grasys said:
Hello,

We have three W2000 DC's on a single domain. My aim is to bring in a
new 2003 server, make it a DC (and promote two other 2003 servers we
already have) AND somewhere in the process demote the W2k DC's to
member servers.

I've done adprep /forestprep adprep /domainprep
I've promoted my Windows 2003 server.
Installed DNS server from add/remove programs in control panel.
Now am stucked with DNS. I tried to run netdiag command. and I got warning
in the middle of the log :

[WARNING] Cannot find a primary authoritative DNS server for the name
'Typhon.burgessfurniture.com.'. [ERROR_TIMEOUT]
The name 'Typhon.burgessfurniture.com.' may not be
registered in DNS

I am trying to sort it out, but I am not sure where to start. Maybe I have
to trasfer all the DNS records from my old windows 2000 server
to windows 2003 or I have to setup secondary zone.
I tried doing that http://support.microsoft.com/kb/323383, but I got
error - The zone cannot be created. The zone allready exists.


If you could possibly give me any directions about DNS setup.

Regards

First, can you provide us an ipconfig /all of this DC and of another DC
please? That will give us a greater understanding of your infrastructure.

Also, if the zone is already created and it's AD Integrated, and you are
trying to create it on a DC that you've just installed DNS, you must be
patient and allow the zone to auto-appear. This is because the zone does
already exist iin the eyes of the DC because it is already in the AD
database. Also, if you are tyring to create it and put it in the wrong
replication scope, eg. the origfinal is in the DomainNC and the one you are
trying tocreate in the DOmainDnsZones partition, or even in the
ForestDnsZOnes partitiion, then I can see where you are havind difficulty.

Please elaborate on exactly what steps and options you chose during your
attempt to create the zone so we can figure out exactly what you did, along
with that ipconfig /all please.

Thanks


--
Regards,
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT,
MVP Microsoft MVP - Directory Services
Microsoft Certified Trainer

Infinite Diversities in Infinite Combinations

Having difficulty reading or finding responses to your post?
Try using Outlook Express or any other newsreader, configure a news
account, and point it to news.microsoft.com. Anonymous access. It's
easy and it's free:

How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

"Life isn't like a box of chocolates or a bowl of cherries or
peaches... Life is more like a jar of jalapenos. What you do today
may burn your butt tomorrow." - Garfield
 
Hello

My new DC ipconfig gives that

C:\Documents and Settings\Typhon>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Typhon
Primary Dns Suffix . . . . . . . : burgessfurniture.com
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : burgessfurniture.com

Ethernet adapter Local Area Connection 3:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : 00-10-18-2F-2D-0B
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.221.236
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

Ethernet adapter Local Area Connection 4:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
#2
Physical Address. . . . . . . . . : 00-10-18-2F-2D-08
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.139.39
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom BCM5708C NetXtreme II GigE
(NDIS
VBD Client)
Physical Address. . . . . . . . . : 00-1C-23-BC-91-90
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.1.1.176
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.1.1.176
DNS Servers . . . . . . . . . . . : 192.1.1.156

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom BCM5708C NetXtreme II GigE
(NDIS
VBD Client) #2
Physical Address. . . . . . . . . : 00-1C-23-BC-91-92
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.151.211
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

C:\Documents and Settings\Typhon>

My old DC ipconfig gives


Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

C:\Documents and Settings\morpheus>ipconfig /all

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : MORPHEUS
Primary DNS Suffix . . . . . . . : burgessfurniture.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : burgessfurniture.com

Ethernet adapter Burgess:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100+ Server Adapter
(PI
LA8470B)
Physical Address. . . . . . . . . : 00-02-B3-5B-47-BF
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.1.1.156
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.1.1.113
DNS Servers . . . . . . . . . . . : 192.1.1.156
Primary WINS Server . . . . . . . : 192.1.1.156

C:\Documents and Settings\morpheus>

Thanks


Ace Fekay said:
In
Donatas Grasys said:
Hello,

We have three W2000 DC's on a single domain. My aim is to bring in a
new 2003 server, make it a DC (and promote two other 2003 servers we
already have) AND somewhere in the process demote the W2k DC's to
member servers.

I've done adprep /forestprep adprep /domainprep
I've promoted my Windows 2003 server.
Installed DNS server from add/remove programs in control panel.
Now am stucked with DNS. I tried to run netdiag command. and I got
warning in the middle of the log :

[WARNING] Cannot find a primary authoritative DNS server for the name
'Typhon.burgessfurniture.com.'. [ERROR_TIMEOUT]
The name 'Typhon.burgessfurniture.com.' may not be
registered in DNS

I am trying to sort it out, but I am not sure where to start. Maybe I
have to trasfer all the DNS records from my old windows 2000 server
to windows 2003 or I have to setup secondary zone.
I tried doing that http://support.microsoft.com/kb/323383, but I got
error - The zone cannot be created. The zone allready exists.


If you could possibly give me any directions about DNS setup.

Regards

First, can you provide us an ipconfig /all of this DC and of another DC
please? That will give us a greater understanding of your infrastructure.

Also, if the zone is already created and it's AD Integrated, and you are
trying to create it on a DC that you've just installed DNS, you must be
patient and allow the zone to auto-appear. This is because the zone does
already exist iin the eyes of the DC because it is already in the AD
database. Also, if you are tyring to create it and put it in the wrong
replication scope, eg. the origfinal is in the DomainNC and the one you
are trying tocreate in the DOmainDnsZones partition, or even in the
ForestDnsZOnes partitiion, then I can see where you are havind difficulty.

Please elaborate on exactly what steps and options you chose during your
attempt to create the zone so we can figure out exactly what you did,
along with that ipconfig /all please.

Thanks


--
Regards,
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT,
MVP Microsoft MVP - Directory Services
Microsoft Certified Trainer

Infinite Diversities in Infinite Combinations

Having difficulty reading or finding responses to your post?
Try using Outlook Express or any other newsreader, configure a news
account, and point it to news.microsoft.com. Anonymous access. It's
easy and it's free:

How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

"Life isn't like a box of chocolates or a bowl of cherries or
peaches... Life is more like a jar of jalapenos. What you do today
may burn your butt tomorrow." - Garfield
 
Hello Donatas,

On Typhon you have the server itself as DG. Why not your router?

On Morpeus you have another DG address. x.x.x.113 Is that a router or another
server?

Better disable the NIC's that are not used on your servers.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
Hello

My new DC ipconfig gives that

C:\Documents and Settings\Typhon>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Typhon
Primary Dns Suffix . . . . . . . : burgessfurniture.com
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : burgessfurniture.com
Ethernet adapter Local Area Connection 3:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
Ethernet
Physical Address. . . . . . . . . : 00-10-18-2F-2D-0B
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.221.236
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
Ethernet adapter Local Area Connection 4:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
Ethernet
#2
Physical Address. . . . . . . . . : 00-10-18-2F-2D-08
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.139.39
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom BCM5708C NetXtreme II
GigE
(NDIS
VBD Client)
Physical Address. . . . . . . . . : 00-1C-23-BC-91-90
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.1.1.176
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.1.1.176
DNS Servers . . . . . . . . . . . : 192.1.1.156
Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom BCM5708C NetXtreme II
GigE
(NDIS
VBD Client) #2
Physical Address. . . . . . . . . : 00-1C-23-BC-91-92
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.151.211
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
C:\Documents and Settings\Typhon>

My old DC ipconfig gives

Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.
C:\Documents and Settings\morpheus>ipconfig /all

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : MORPHEUS
Primary DNS Suffix . . . . . . . : burgessfurniture.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : burgessfurniture.com
Ethernet adapter Burgess:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100+ Server
Adapter
(PI
LA8470B)
Physical Address. . . . . . . . . : 00-02-B3-5B-47-BF
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.1.1.156
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.1.1.113
DNS Servers . . . . . . . . . . . : 192.1.1.156
Primary WINS Server . . . . . . . : 192.1.1.156
C:\Documents and Settings\morpheus>

Thanks

In
Donatas Grasys said:
Hello,

We have three W2000 DC's on a single domain. My aim is to bring in a

new 2003 server, make it a DC (and promote two other 2003 servers
we already have) AND somewhere in the process demote the W2k DC's
to member servers.

I've done adprep /forestprep adprep /domainprep
I've promoted my Windows 2003 server.
Installed DNS server from add/remove programs in control panel.
Now am stucked with DNS. I tried to run netdiag command. and I got
warning in the middle of the log :
[WARNING] Cannot find a primary authoritative DNS server for the
name
'Typhon.burgessfurniture.com.'. [ERROR_TIMEOUT]
The name 'Typhon.burgessfurniture.com.' may not be
registered in DNS
I am trying to sort it out, but I am not sure where to start. Maybe
I
have to trasfer all the DNS records from my old windows 2000 server
to windows 2003 or I have to setup secondary zone.
I tried doing that http://support.microsoft.com/kb/323383, but I
got
error - The zone cannot be created. The zone allready exists.
If you could possibly give me any directions about DNS setup.

Regards
First, can you provide us an ipconfig /all of this DC and of another
DC please? That will give us a greater understanding of your
infrastructure.

Also, if the zone is already created and it's AD Integrated, and you
are trying to create it on a DC that you've just installed DNS, you
must be patient and allow the zone to auto-appear. This is because
the zone does already exist iin the eyes of the DC because it is
already in the AD database. Also, if you are tyring to create it and
put it in the wrong replication scope, eg. the origfinal is in the
DomainNC and the one you are trying tocreate in the DOmainDnsZones
partition, or even in the ForestDnsZOnes partitiion, then I can see
where you are havind difficulty.

Please elaborate on exactly what steps and options you chose during
your attempt to create the zone so we can figure out exactly what you
did, along with that ipconfig /all please.

Thanks

--
Regards,
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT,
MVP Microsoft MVP - Directory Services
Microsoft Certified Trainer
Infinite Diversities in Infinite Combinations

Having difficulty reading or finding responses to your post?
Try using Outlook Express or any other newsreader, configure a news
account, and point it to news.microsoft.com. Anonymous access. It's
easy and it's free:
How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164
"Life isn't like a box of chocolates or a bowl of cherries or
peaches... Life is more like a jar of jalapenos. What you do today
may burn your butt tomorrow." - Garfield
 
In
Meinolf Weber said:
Hello Donatas,

On Typhon you have the server itself as DG. Why not your router?

On Morpeus you have another DG address. x.x.x.113 Is that a router or
another server?

Better disable the NIC's that are not used on your servers.

Best regards

Meinolf Weber


I agree. Disable the additional NICs on Typhon. Multihomed DCs are very
problematic and is probably the cause of the problem.

Donatas, if you would like to have multiple NICs on the DC, I can provide
you instructions to assist in configuring the DC to work with the multiple
NICs. The instructions involve registry mods. But I believe and recommend to
only use one NIC on a domain controller to minimize domain controller
problems.

Ace
 
Back
Top