Announcement

Collapse
No announcement yet.

problems with a one word domain?

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • problems with a one word domain?

    windows 2003 , creating a forest, with the top level just called "domain" for example

    when trying to add child domains to that, it can never pick it up, and gives DNS errors, but can ping and nslookup the host

    just wondering if you do need to specify the domain to have a .com etc ? thought that was for the old days of authenticating.

    help appreciated.

    getting this error when trying to add child to domain

    An Active Directory domain controller for the domain DOMAIN could not be contacted
    Ensure that DNS domain is typed correctly
    Last edited by Maxwell Shivers; 11th October 2005, 01:57.

  • #2
    Re: problems with a one word domain?

    > just wondering if you do need to specify the domain to have a .com etc ?

    You do. Although the wizard does not enforce it, a domain with at least two components is pretty much a requirement.

    > thought that was for the old days of authenticating.

    Nope. You are confusing the NetBIOS with the DNS name. We have _both_ nowadays, in the sense that an AD domain has two names. Example:

    DNS: your.domain.com
    NetBIOS: YOUR

    Usually, the NetBIOS name is the first component of the DNS name. If fact, this is what the dcpromo wizard suggests.

    Comment


    • #3
      Re: problems with a one word domain?

      hey , though that was the case,
      although have just added a.something to the end to test
      still same DNS issue
      anyawy done any major work with bin9 and win dns, having them work nicely together?
      have bind set a slave of the windows DNS box at present

      Comment

      Working...
      X