none
How to add sucessfully add yourdomain.com to domain controller

    Question

  • I am new to Windows Server 2008, and have a small network setup of 5 servers and 3 workstations/laptops. 

    I want 2 of the 5 servers to be domain controllers.

    I have already ran DC promo and set up the first server with AD DS. I used net.kevinkarimu.com as the DC FQDN. The domain kevinkarimu.com is registered with powweb.com. There is an interface at powweb where I can manage DNS for the domain (A Name, CNAME, MX, etc). 

    The network that the servers and workstations run from are under a AT&T u-verse router that has DHCP. AT&T has provided 5 static public IPs (at my request). However, I think that the IPs for the DCs should be local or private.

    When attempting to add the 2nd DC, I get this error:

    An error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain "net.kevinkarimu.com".

    The error was: "No records found for given DNS query."
    (error code 0x0000251D DNS_INFO_NO_RECORDS)

    The query was for the SRV record for _ldap._tcp.dc._msdcs.net.kevinkarimu.com

    How do I got about adding net.kevinkarimu.com as the FQDN for my DC? How do I configure DNS for kevinkarimu.com since it is registered with powweb (a web hosting company)?

    Sunday, April 06, 2014 3:57 AM

Answers

  • external dns will have nothing do with your setup. The most important thing is your internal dns I precisely mean your local dns should be configured for PERFECTLY. 

    If its configured good then you should be able to create the additional domain controller without any issues.

    Please read this links 

    Checklist for creating the first domain controller

    http://technet.microsoft.com/en-us/library/cc772558(v=ws.10).aspx

    Installing the Dns on the First domain controller 

    http://www.oucs.ox.ac.uk/windows/active/dns/internaldomain/index.xml?ID=dns-configure

    Note: Please turn of the firewall when creating the additional domain controller.


    http://www.arabitpro.com

    Sunday, April 06, 2014 6:34 AM
  • Sorry to say: Your configuration is wrong. Follow these rules and read something that will shed the more light into AD design:

    1. There are few reasons for using FQDN in internal network (see split brain configuration). In majority of cases there is local private domain, something like kevin.local

    2. DNS and DHCP SHOULD sit on internal server, which is in majority of cases domain controller.

    3. On client computers the DNS  IP settings points to internal DNS server only (no public DNS)

    4. For services like MX, ports are forwarded to internal server.

    5. If you want have public DNS in your network, put it into demilitarized zone.

    6. Local DNS that belong to AD resolves public FQDN (description how is beyong the scope of this forum - look into Technet)

    7. IP of DNS in DC is configured in the following way. Preferred value points to local server and Alternate value points to other DC.

    Regards

    Milos


    Sunday, April 06, 2014 6:34 AM

All replies

  • external dns will have nothing do with your setup. The most important thing is your internal dns I precisely mean your local dns should be configured for PERFECTLY. 

    If its configured good then you should be able to create the additional domain controller without any issues.

    Please read this links 

    Checklist for creating the first domain controller

    http://technet.microsoft.com/en-us/library/cc772558(v=ws.10).aspx

    Installing the Dns on the First domain controller 

    http://www.oucs.ox.ac.uk/windows/active/dns/internaldomain/index.xml?ID=dns-configure

    Note: Please turn of the firewall when creating the additional domain controller.


    http://www.arabitpro.com

    Sunday, April 06, 2014 6:34 AM
  • Sorry to say: Your configuration is wrong. Follow these rules and read something that will shed the more light into AD design:

    1. There are few reasons for using FQDN in internal network (see split brain configuration). In majority of cases there is local private domain, something like kevin.local

    2. DNS and DHCP SHOULD sit on internal server, which is in majority of cases domain controller.

    3. On client computers the DNS  IP settings points to internal DNS server only (no public DNS)

    4. For services like MX, ports are forwarded to internal server.

    5. If you want have public DNS in your network, put it into demilitarized zone.

    6. Local DNS that belong to AD resolves public FQDN (description how is beyong the scope of this forum - look into Technet)

    7. IP of DNS in DC is configured in the following way. Preferred value points to local server and Alternate value points to other DC.

    Regards

    Milos


    Sunday, April 06, 2014 6:34 AM