guid based dns name not registered

Discussion in 'Active Directory' started by aks, Feb 17, 2005.

  1. aks

    aks Guest

    Hi Paul:

    I' inserted my answers below. There's some progress. Thanks again.

    aks>> Box is not yet promoted to a DC, so as suggested I used
    system->computer name to add FQDN. Its now as: serv1.orange.com
    aks>> hmmm, you are right. I removed the dns role and re-added dns role
    using the wizard. In one of the steps it prompted me to check a box (create
    associated record) - i checked it this time, last time it was left unchecked.
    I got a msg - record successfully created - thats good.

    Now "nslookup serv1" says this:
    C:\nslookup serv1
    Server: orange.com
    Address: 192.168.0.1

    *** orange.com can't find serv1: Server failed

    Run ipconfig /registerdns on the DC/ DNS server.
    aks>> I tried running ipconfig /registerdns on this box(called serv1), no
    errors reported in Event viewer.
    aks>> wizard
     
    aks, Feb 24, 2005
    #21
    1. Advertisements

  2. aks

    aks Guest

    aks>> answers below.

    aks>> no multiple NICs. Was a long day yesterday, could be a typo am
    believing. Its okay now, I reused the wizard to start clean this morning - IP
    is correct.
    aks>> zones (forward and reverse are configured to accept dynamic updates)
    aks>> am using just the wizard, not editing any tabs. However, for forward
    zones I have given the IP of another box (serv2) which will eventually have a
    DNS running there. Currently am making serv1 work properly. Then will do the
    same on serv2 and serv3. Once dns is ok, will install AD on all three.
    As i mentioned in my last post, I removed the dns role, and added it on
    serv1, added IP address of another box(serv2) for forwarder, hence did not
    get error msg "cannot create forwarder" - last night I was getting an error
    here as I was adding the IP of itself(serv1), i guess it didn't like it :)

    aks>> lots of trial and error as you can see :) Am glad am seeing
    progress...
     
    aks, Feb 24, 2005
    #22
    1. Advertisements

  3. aks

    aks Guest

    Paul:

    I configured the DHCP which I believe was never configured properly. Now,
    this is what I get:

    C:>nslookup serv1 // errors still
    Server: orange.com
    Address: 192.168.0.1
    *** orange.com can't find serv1: Server failed

    C:\>nslookup 192.168.0.1 // no errors, but it displays domain name only, no
    mention of hostname anywhere. Any
    thoughts ?
    Server: orange.com
    Address: 192.168.0.1

    Name: orange.com
    Address: 192.168.0.1


     
    aks, Feb 24, 2005
    #23
  4. aks

    aks Guest

    never mind Paul, DNS & DHCP issue looks to be **FINALLY** resolved. The
    domain name addition under system->computername required a reboot :)

    will try to make the above work on serv2 and serv3 - confirm DNS success.
    Then move on to AD on the three DC's in the forest. Will keep you posted (not
    to say have not bugged you enough over the past days :)) )

    Much thanks for all the pointers so far - 've been great !
     
    aks, Feb 24, 2005
    #24
  5. aks

    ptwilliams Guest

    The DHCP Client service needs to be set to automatically start, and should
    be running. However, the soon-to-be DC **SHOULD NOT BE** a DHCP client.
    You still have to use a static IP address. The DHCP client service
    registers records in DNS - it is told to do so by NETLOGON.

    The results below are because there's not an A record registered.
    Configure a static IP address and Windows will register the new A record.

    Re-registering DNS should add a PTR record too; this will fix the nslookup
    error.

    --

    Paul Williams

    http://www.msresource.net/
    http://forums.msresource.net/

    Paul:

    I configured the DHCP which I believe was never configured properly. Now,
    this is what I get:

    C:>nslookup serv1 // errors still
    Server: orange.com
    Address: 192.168.0.1
    *** orange.com can't find serv1: Server failed

    C:\>nslookup 192.168.0.1 // no errors, but it displays domain name only,
    no
    mention of hostname anywhere. Any
    thoughts ?
    Server: orange.com
    Address: 192.168.0.1

    Name: orange.com
    Address: 192.168.0.1


     
    ptwilliams, Feb 24, 2005
    #25
  6. aks

    ptwilliams Guest

    We got there finally!!!

    Glad to have helped...


    DNS is vital. Get it working properly and you wont have many other
    problems. Now that you know what you're doing, you might want to do a bit
    of background reading.

    MS do some good whitepapers on the subject.

    If you fancy a book, buy Mark Minasi's Mastering Windows 2003 Server.


    --

    Paul Williams

    http://www.msresource.net/
    http://forums.msresource.net/

    never mind Paul, DNS & DHCP issue looks to be **FINALLY** resolved. The
    domain name addition under system->computername required a reboot :)

    will try to make the above work on serv2 and serv3 - confirm DNS success.
    Then move on to AD on the three DC's in the forest. Will keep you posted
    (not
    to say have not bugged you enough over the past days :)) )

    Much thanks for all the pointers so far - 've been great !
     
    ptwilliams, Feb 24, 2005
    #26
  7. Hi Paul,
    I faced the same problem in my clients environment and resolved with the
    same resolution that you suggested here. My problem comes due to the Island
    problem as described by Microsoft Documentations.
    Thanks in advance foe such a long and descriptive reply.
    Warm regards,
    Charly
     
    Charly P Cheriyan, Feb 25, 2005
    #27
  8. aks

    ptwilliams Guest

    No Problem!!! Thanks for the feedback.

    The Island problem was made a lot more difficult to get yourself into in
    2003, by delegating the _msdcs and making it's scope forest-wide. However,
    as we've seen here, it's still not impossible to get into it.

    This is the first time I've seen it in 2003.

    In 2000, the main thing that would cause it was an IP address change, when
    the box was pointing to itself. Which spurred me to write a brief article
    on how to move DCs across subnets (change IP address).


    --

    Paul Williams

    http://www.msresource.net/
    http://forums.msresource.net/

    message Hi Paul,
    I faced the same problem in my clients environment and resolved with the
    same resolution that you suggested here. My problem comes due to the Island
    problem as described by Microsoft Documentations.
    Thanks in advance foe such a long and descriptive reply.
    Warm regards,
    Charly
     
    ptwilliams, Feb 26, 2005
    #28
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.