Discussions

DNS SRV records required to locate domain controller ?

+
0 Votes
Locked

DNS SRV records required to locate domain controller ?

jalfonso
I KEEP RECEIVING THE ERROR MESSAGE BELOW FROM A STANDALONE SERVER THAT I WISH TO JOIN INTO THE DOMAIN CONTROLLER <AS A MEMBER SERVER>.

THE MESSAGE STATES THAT THEIR IS A SRV RECORD THAT IS MISSING FROM THE SERVER.LOCAL MACHINE (WHERE SERVER.LOCAL IS THE qualified domain name).

THE 207.231.208.150 IP address that it refers to is simply a web dns server that our LAN does lookups to, outside of our internal network (it is a DNS server from our ISP)!

Please HLEP !!!!!


--------------------------------------------
The following error occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain bentrust.local:

The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)

The query was for the SRV record for _ldap._tcp.dc._msdcs.bentrust.local

Common causes of this error include the following:

- The DNS SRV records required to locate a domain controller for the domain are not registered in DNS. These records are registered with a DNS server automatically when a domain controller is added to a domain. They are updated by the domain controller at set intervals. This computer is configured to use DNS servers with following IP addresses:

207.231.208.150 (EXTERNAL NAME OF WEB DNS SERVER)

- One or more of the following zones do not include delegation to its child zone:

bentrust.local
local
. (the root zone)

-------------------------------------------
  • +
    0 Votes
    Why Me Worry?

    Do you guys have AD integrated DNS set up? If not, I strongly recommend that you do. Also, when joining a standalone server to a domain to make a member server, the primary and secondary DNS server addresses should be pointing to the domain controllers, assuming that DNS is AD integrated.

    Another issue you may have is that one of your servers hosting the Infrastructure and RID FSMO roles is malfunctioning. Check to see if you have issues with the servers hosting those FSMO roles. Also, if this is a Windows 2003 environment, your internal DNS servers should be setup to forward non-resolved DNS queries to your ISP DNS server. You should never point your internal servers and clients directly to your external ISP DNS servers. Internal DNS should always forward non-resolved queries to an upstream public ISP hosted DNS server.

    +
    0 Votes
    jalfonso

    If in fact this is causing some problems, how do I go about setting my Internal DNS server(s) to always forward non-resolved queries to an upstream public ISP hosted DNS server ?

    Is there a step-by-step way that I can follow a procedure that will allow me to change my internal DNS unresolved queries, so that my workstations/servers always point to a single internal DNS server ?

    +
    0 Votes
    jalfonso

    OK - but what steps do I follow in order to find out what the current FSMO role is set to ?

    Are there any command prompt command(s) to display what a given role looks like?
    No DNS is ever perfect, not one that I have come across so far, but I used the Windows Wizard when I first set up my server as the PDC (Domain Controller, using Windows Server 2003 - Std. Edition) in addition to the same server running DNS (for Active Directory) role.

    So, what else should I keep in mind in order to correct this given SRV Record lookup problem?

    Jose'

  • +
    0 Votes
    Why Me Worry?

    Do you guys have AD integrated DNS set up? If not, I strongly recommend that you do. Also, when joining a standalone server to a domain to make a member server, the primary and secondary DNS server addresses should be pointing to the domain controllers, assuming that DNS is AD integrated.

    Another issue you may have is that one of your servers hosting the Infrastructure and RID FSMO roles is malfunctioning. Check to see if you have issues with the servers hosting those FSMO roles. Also, if this is a Windows 2003 environment, your internal DNS servers should be setup to forward non-resolved DNS queries to your ISP DNS server. You should never point your internal servers and clients directly to your external ISP DNS servers. Internal DNS should always forward non-resolved queries to an upstream public ISP hosted DNS server.

    +
    0 Votes
    jalfonso

    If in fact this is causing some problems, how do I go about setting my Internal DNS server(s) to always forward non-resolved queries to an upstream public ISP hosted DNS server ?

    Is there a step-by-step way that I can follow a procedure that will allow me to change my internal DNS unresolved queries, so that my workstations/servers always point to a single internal DNS server ?

    +
    0 Votes
    jalfonso

    OK - but what steps do I follow in order to find out what the current FSMO role is set to ?

    Are there any command prompt command(s) to display what a given role looks like?
    No DNS is ever perfect, not one that I have come across so far, but I used the Windows Wizard when I first set up my server as the PDC (Domain Controller, using Windows Server 2003 - Std. Edition) in addition to the same server running DNS (for Active Directory) role.

    So, what else should I keep in mind in order to correct this given SRV Record lookup problem?

    Jose'