DNS Problem

[Guest]

Hi

We have installed a new windows 2000 server on our network. Download all the patches. We made sure that the Dns was set up correctly. We then ran "configure your server" The ad replicated the accounts ok? But then it disables the Dns which we had configured prior to the wizard. Saw the "AllowSIngleLAbelDomainDNS" reg entry; we did that on both servers and no help. We went this route to save time because we are upgrading to sbs 2003. At that point I think you can use the rename tool to solve the problem. Any help or advice is greatly appreciated
Best Regards
David Swan

 

[SaltPeter]

Hi.

We have installed a new windows 2000 server on our network. Download all

the patches. We made sure that the Dns was set up correctly. We then ran
"configure your server" The ad replicated the accounts ok? But then it
disables the Dns which we had configured prior to the wizard. Saw the
"AllowSIngleLAbelDomainDNS" reg entry; we did that on both servers and no
help. We went this route to save time because we are upgrading to sbs 2003.
At that point I think you can use the rename tool to solve the problem. Any
help or advice is greatly appreciated.

Best Regards.
David Swann

DNS implies a hierarchy. If you choose to use a single-named domain, you
forfeit the ability to use DNS as a name resolution service. You therefore
agree to depend on a flat 2-dimensional domain which is based on netbios
name resolution (like NT4). Now you know one of the reasons why a W2K DC can
only participate in an NT4 environment as a PDC emulator.

You should have installed domain with a "domain.local" naming convention.
Also, note that once an NT4 PDC is upgraded to a W2K PDC emulator, both the
netbios name AND an fqdn name are associated with the rootDC.

 

[Michael Bednarek]

We have installed a new windows 2000 server on our network. Download all the patches. We made sure that the Dns was set up correctly. We then ran "configure your server" The ad replicated the accounts ok? But then it disables the Dns which we had configured prior to the wizard. Saw the "AllowSIngleLAbelDomainDNS" reg entry; we did that on both servers and no help. We went this route to save time because we are upgrading to sbs 2003. At that point I think you can use the rename tool to solve the problem. Any help or advice is greatly appreciated.

[Please hit the Return/Enter key after about 72 characters]

Here's what Mark Minasi said recently on this subject:

"Active Directories Do Not Like One-Part Names"

"Once an Active Directory designer understands the nature of DNS and
split-brain DNS in particular then she soon realizes that it's
theoretically possible to have a domain name without a period in it.
For example, while most of us think that domain names look like
"minasi.com" it is quite possible to have a domain named "com," and of
course such a domain exists on the public Internet DNS hierarchy -- it's
the one that Network Solutions controls and that my domain is a child
domain of. (And that every other domain whose name ends in "com" is a
child of.)"

"But Windows DNS code isn't really built to handle one-part, no-period
DNS names. Apparently the dynamic DNS client is the culprit -- it
doesn't register names correctly for systems whose DNS suffix is just
one part like "com" or "local" instead of multi-part DNS suffixes like
"minasi.com" or "eastcoast.bigfirm.biz." So, the bottom line is: make
sure there's at least one period in your DNS suffixes."

This sounds like you should rebuild your server with a proper domain
name.

 

[J.C. Hornbeck [MSFT]]

If you're running into an issue where DNS registrations are failing due to
the use of a single labeled domain, you'll also need to use the
UpdateTopLevelDomainZones registry entry. See knowledge base article
300684 - Information about configuring Windows for domains with single-label
DNS names (http://support.microsoft.com/default.aspx?scid=kb;en-us;300684).

--
J.C. Hornbeck, MCSE
Microsoft Product Support

NOTE: Please reply to the newsgroup and not directly to me. This allows
others to add to and benefit from these threads and also helps to ensure a
more timely response. Thank you!

This posting is provided "AS IS" without warranty either expressed or
implied, including, but not limited to, the implied warranties of
merchantability or fitness for a particular purpose.

Hi.

We have installed a new windows 2000 server on our network. Download all

the patches. We made sure that the Dns was set up correctly. We then ran
"configure your server" The ad replicated the accounts ok? But then it
disables the Dns which we had configured prior to the wizard. Saw the
"AllowSIngleLAbelDomainDNS" reg entry; we did that on both servers and no
help. We went this route to save time because we are upgrading to sbs 2003.
At that point I think you can use the rename tool to solve the problem. Any
help or advice is greatly appreciated.