[Cialug] Off topic - Windows Help

[Kevin Smith]

I appears there's a A record in the DNS, but this test fails. Oddly, our
working Windows server fails with with the same error, so probably not
related?

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Users\Administrator>dcdiag /test:dns

Directory Server Diagnosis

Performing initial setup:
   Trying to find home server...
   Home Server = Ames-Server
   * Identified AD Forest.
   Done gathering initial info.

Doing initial required tests

   Testing server: Default-First-Site-Name\AMES-SERVER
      Starting test: Connectivity
         ......................... AMES-SERVER passed test Connectivity

Doing primary tests

   Testing server: Default-First-Site-Name\AMES-SERVER

      Starting test: DNS

         DNS Tests are running and not hung. Please wait a few minutes...
         ......................... AMES-SERVER passed test DNS

   Running partition tests on : ForestDnsZones

   Running partition tests on : DomainDnsZones

   Running partition tests on : Schema

   Running partition tests on : Configuration

   Running partition tests on : msl

   Running enterprise tests on : msl.local
      Starting test: DNS
         Test results for domain controllers:

            DC: Ames-Server
            Domain: msl.local


               TEST: Basic (Basc)
                  Warning: The A record for this DC was not found
                  No host records (A or AAAA) were found for this DC

On Sat, Dec 6, 2014 at 1:43 PM, Kevin Smith <kevin at linuxsmith.com> wrote:

> Did this to test:
>
> nslookup
> set type=srv
> _ldap._tcp.dc._msdcs.msl.local
>
> It returned
>
> _ldap._tcp.dc._msdcs.msl.local  SRV service location:
>           priority       = 0
>           weight         = 100
>           port           = 389
>           svr hostname   = ames-server.msl.local
> ames-server.msl.local   internet address = 10.0.11.1
>
>
>
> On Sat, Dec 6, 2014 at 12:56 PM, Josh More <jmore at starmind.org> wrote:
>
>> Does nslookup for the DC work against the DC?
>>
>> On Sat, Dec 6, 2014 at 12:50 PM, Kevin Smith <kevin at linuxsmith.com>
>> wrote:
>> > Ran into something odd and the Internets isn't much help. Need to  fix
>> this
>> > by Monday, so any suggestions would be great. I may be willing to hire a
>> > Windows server guru if I don't get this figured out by today.
>> >
>> > When trying to add a computer to the new Windows Domain Controller we
>> are
>> > getting the error a the bottom. We've tried the common answers from
>> Google
>> > searches, I think something is bad with the DNS? We can ping the DC
>> > hostname and FQDN. So, I'm confused. Any ideas.
>> >
>> > ---------------------------
>> > Computer Name/Domain Changes
>> > ---------------------------
>> > The following error occurred attempting to join the domain "msl":
>> >
>> > An attempt to resolve the DNS name of a domain controller in the domain
>> > being joined has failed.  Please verify this client is configured to
>> reach
>> > a DNS server that can resolve DNS names in the target domain. For
>> > information about network troubleshooting, see Windows Help.
>> > ---------------------------
>> > _______________________________________________
>> > Cialug mailing list
>> > Cialug at cialug.org
>> > http://cialug.org/mailman/listinfo/cialug
>> _______________________________________________
>> Cialug mailing list
>> Cialug at cialug.org
>> http://cialug.org/mailman/listinfo/cialug
>>
>
>