DNS _msdcs problem on localhost

Toggle sidebar Toggle sidebar
H

hugopt

Honorable
Sep 27, 2013
4
0
10,510
Hello.

I'm with a problem at a few weeks and until now didn't find a answer.
We have a Windows Server 2008 R2.
I'm trying to add new PC to my domain but i'm getting an error "an attempt to resolve dns name of a domain controller in the domain being joined has failed..."

I made many test on the machine and here some information's:

##################################################################################
1) Test with dcdiag
>dcdiag /q
The host 8ec2e337-08e4-41d7-bb1f-e7724dd7e3c6._msdcs.dir.lusobasto.com
could not be resolved to an IP address. Check the DNS server, DHCP,
server name, etc.
Got error while checking LDAP and RPC connectivity. Please check your
firewall settings.
......................... WIN-T7IGTSGDJ64 failed test Connectivity

##################################################################################

2) Test with dnslint (localhost)
> dnslint /ad /t /s localhost
DNSLint Report

System Date: Fri Sep 27 16:04:10 2013

Command run:

dnslint /ad /t /s localhost

Root of Active Directory Forest:

dir.lusobasto.com
Active Directory Forest Replication GUIDs Found:

DC: WIN-T7IGTSGDJ64
GUID: 8ec2e337-08e4-41d7-bb1f-e7724dd7e3c6


Total GUIDs found: 1

--------------------------------------------------------------------------------

Results from querying the locally configured DNS server(s):



Alias (CNAME) and glue (A) records for forest GUIDs from server:

Total number of CNAME records found by local system: 0

Total number of CNAME records local system could not find: 1

Total number of glue (A) records local system could not find: 0

CNAME records for forest GUIDs not found:
GUID: 8ec2e337-08e4-41d7-bb1f-e7724dd7e3c6._msdcs.dir.lusobasto.com
DC: WIN-T7IGTSGDJ64

##################################################################################

3) Test with dnslint with IP (192.168.100.100)
> dnslint /ad /t /s 192.168.100.100
DNSLint Report

System Date: Fri Sep 27 16:04:36 2013

Command run:

dnslint /ad /t /s 192.168.100.100

Root of Active Directory Forest:

dir.lusobasto.com
Active Directory Forest Replication GUIDs Found:

DC: WIN-T7IGTSGDJ64
GUID: 8ec2e337-08e4-41d7-bb1f-e7724dd7e3c6


Total GUIDs found: 1

--------------------------------------------------------------------------------

The following 2 DNS servers were checked for records related to AD forest replication:

DNS server: win-t7igtsgdj64.dir.lusobasto.com
IP Address: 192.168.100.100
UDP port 53 responding to queries: YES
TCP port 53 responding to queries: Not tested
Answering authoritatively for domain: YES

SOA record data from server:
Authoritative name server: win-t7igtsgdj64.dir.lusobasto.com
Hostmaster: hostmaster.dir.lusobasto.com
Zone serial number: 37
Zone expires in: 1.00 day(s)
Refresh period: 900 seconds
Retry delay: 600 seconds
Default (minimum) TTL: 3600 seconds


Additional authoritative (NS) records from server:
win-t7igtsgdj64 Unknown
win-t7igtsgdj64.dir.lusobasto.com Unknown




Alias (CNAME) and glue (A) records for forest GUIDs from server:
CNAME: 8ec2e337-08e4-41d7-bb1f-e7724dd7e3c6._msdcs.dir.lusobasto.com
Alias: win-t7igtsgdj64.dir.lusobasto.com
Glue: 192.168.100.50


Total number of CNAME records found on this server: 1

Total number of CNAME records missing on this server: 0

Total number of glue (A) records this server could not find: 0



--------------------------------------------------------------------------------

DNS server: win-t7igtsgdj64
IP Address: 192.168.100.100
UDP port 53 responding to queries: YES
TCP port 53 responding to queries: Not tested
Answering authoritatively for domain: YES

SOA record data from server:
Authoritative name server: win-t7igtsgdj64.dir.lusobasto.com
Hostmaster: hostmaster.dir.lusobasto.com
Zone serial number: 37
Zone expires in: 1.00 day(s)
Refresh period: 900 seconds
Retry delay: 600 seconds
Default (minimum) TTL: 3600 seconds


Additional authoritative (NS) records from server:
win-t7igtsgdj64.dir.lusobasto.com Unknown
win-t7igtsgdj64 Unknown




Alias (CNAME) and glue (A) records for forest GUIDs from server:
CNAME: 8ec2e337-08e4-41d7-bb1f-e7724dd7e3c6._msdcs.dir.lusobasto.com
Alias: win-t7igtsgdj64.dir.lusobasto.com
Glue: 192.168.100.100


Total number of CNAME records found on this server: 1

Total number of CNAME records missing on this server: 0

Total number of glue (A) records this server could not find: 0

##################################################################################

4) Test with Port Query (localhost)
> portqry.exe -n localhost -e 389 -p UDP
=============================================

Starting portqry.exe -n localhost -e 389 -p UDP ...


Querying target system called:

localhost

Attempting to resolve name to IP address...


Name resolved to 127.0.0.1

querying...

UDP port 389 (unknown service): NOT LISTENING
portqry.exe -n localhost -e 389 -p UDP exits with return code 0x00000001.

##################################################################################

5) Test with Port Query (IP)
> portqry.exe -n 192.168.100.100 -e 389 -p UDP
=============================================

Starting portqry.exe -n 192.168.100.100 -e 389 -p UDP ...


Querying target system called:

192.168.100.100

Attempting to resolve IP address to a name...


IP address resolved to WIN-T7IGTSGDJ64.dir.lusobasto.com

querying...

UDP port 389 (unknown service): LISTENING or FILTERED

Using ephemeral source port
Sending LDAP query to UDP port 389...

LDAP query response:


currentdate: 09/27/2013 16:16:49 (unadjusted GMT)
subschemaSubentry: CN=Aggregate,CN=Schema,CN=Configuration,DC=dir,DC=lusobasto,DC=com
dsServiceName: CN=NTDS Settings,CN=WIN-T7IGTSGDJ64,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=dir,DC=lusobasto,DC=com
namingContexts: DC=dir,DC=lusobasto,DC=com
defaultNamingContext: DC=dir,DC=lusobasto,DC=com
schemaNamingContext: CN=Schema,CN=Configuration,DC=dir,DC=lusobasto,DC=com
configurationNamingContext: CN=Configuration,DC=dir,DC=lusobasto,DC=com
rootDomainNamingContext: DC=dir,DC=lusobasto,DC=com
supportedControl: 1.2.840.113556.1.4.319
supportedLDAPVersion: 3
supportedLDAPPolicies: MaxPoolThreads
highestCommittedUSN: 1192559
supportedSASLMechanisms: GSSAPI
dnsHostName: WIN-T7IGTSGDJ64.dir.lusobasto.com
ldapServiceName: dir.lusobasto.com:win-t7igtsgdj64$@DIR.LUSOBASTO.COM
serverName: CN=WIN-T7IGTSGDJ64,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=dir,DC=lusobasto,DC=com
supportedCapabilities: 1.2.840.113556.1.4.800
isSynchronized: TRUE
isGlobalCatalogReady: TRUE
domainFunctionality: 4
forestFunctionality: 4
domainControllerFunctionality: 4


======== End of LDAP query response ========

UDP port 389 is LISTENING

portqry.exe -n 192.168.100.100 -e 389 -p UDP exits with return code 0x00000000.

##################################################################################

MY SETTINGS:

##################################################################################
>ipconfig /all
Windows IP Configuration

Host Name . . . . . . . . . . . . : WIN-T7IGTSGDJ64
Primary Dns Suffix . . . . . . . : dir.lusobasto.com
Node Type . . . . . . . . . . . . : Mixed
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : dir.lusobasto.com

PPP adapter RAS (Dial In) Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : RAS (Dial In) Interface
Physical Address. . . . . . . . . :
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.100.50(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 6C-F0-49-50-E3-8F
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::bc29:5596:e65b:92bf%10(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.100.100(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.100.253
DHCPv6 IAID . . . . . . . . . . . : 242020425
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-3B-CB-43-6C-F0-49-50-E3-8F

DNS Servers . . . . . . . . . . . : fe80::a6b1:e9ff:fe9f:b69b%10
192.168.100.100
NetBIOS over Tcpip. . . . . . . . : Enabled
##################################################################################

So for what I understand is that the problem is with the localhost connections since with the IP everything is ok.
I already try many things and until now nothing work.

Anyone have any idea?

Thank you
 
Sort by date Sort by votes
skit75

skit75

Splendid
Oct 7, 2008
2,684
1
21,460
I may be in over my head. Can you not just enter the AD/DC/DNS server IP address into your PC's network adapter window and then join the domain with Domain Admin credentials? Is your DNS server different than your AD/DC Server? Are forward & reverse lookup zones created?

Do you have a router running DHCP or is your network all static?
 
Upvote 0 Downvote
H

hugopt

Honorable
Sep 27, 2013
4
0
10,510
Hello.

I just have one server with AD/DC, DNS and DHCP roles. The informations I had post are from my server. Also my server have static IP 192.168.100.100

When I try to add any new PC to the domain I get that error.

When I run that commands on cmd I get the errors, but only using localhost as name. With the IP 192.168.100.100 everything works fine.

:-(
 
Upvote 0 Downvote
skit75

skit75

Splendid
Oct 7, 2008
2,684
1
21,460
It sounds like you just need to create a reverse lookup zone on your DNS server. There are youtube tutorials on how to do this and it isn't very difficult.

I would guess it is either that or you just need to create an A record saying your FQDN = 192.168.100.100
 
Upvote 0 Downvote
H

hugopt

Honorable
Sep 27, 2013
4
0
10,510


Hello,

I already have that informations on DNS Server
dns01.jpg

dns02.jpg

dns03.jpg


I think that is correct.

Any more ideas?

 
Upvote 0 Downvote
H

hugopt

Honorable
Sep 27, 2013
4
0
10,510

Hello.

I found the problem.
It was because the IP on IPV6.
I have on server with dhcp role for ipv6 and the dns server settings was incorrect.
I change the ip to a manual ip and force the dns server on ipv6. Also disable the ipv6 property on my clients to avoid this problem.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom