DNS problem ?

October 20, 2011 at 11:48:11
Specs: Windows Vista
When I try to have a new computer join the domain I get this message:

"The following 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 "SFNG.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.SFNG.LOCAL

Common causes of this error include the following:

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

12.127.17.71
12.127.16.64

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

SFNG.LOCAL
LOCAL
. (the root zone)"

We changed the Internet provider, the old DNS was 192.168.1.200
66.0.175.148

our server has the dns, do I have to edit the dns server ? an how ?

Thanks for any input, Alex


See More: DNS problem ?

Report •

#1
October 20, 2011 at 12:31:14
what ip is the domain controller?
is this the ip the workstation is pointing to for dns?

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#2
October 20, 2011 at 13:03:27
192.168.5.1

Thank you.


Report •

#3
October 20, 2011 at 13:10:22
second questions answer?

lets see a ipconfig /all from a workstation that cant' join the domain

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

Related Solutions

#4
October 20, 2011 at 13:18:21
Sorry, 192.168.5.55

Report •

#5
October 20, 2011 at 13:21:31
C:\Users\victor>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : fernandez
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe FE Family Controller
Physical Address. . . . . . . . . : 00-0A-CD-1D-DB-B4
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::a44a:e780:4062:cd03%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.5.55(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.252.0
Default Gateway . . . . . . . . . : 192.168.4.1
DHCPv6 IAID . . . . . . . . . . . : 234883789
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-1F-8C-D4-00-0A-CD-1D-DB-B4

DNS Servers . . . . . . . . . . . : 12.127.16.64
12.127.17.71
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{FD781C66-608E-483D-A187-7F0A211925F8}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:1457:1e4f:3f57:fac8(Pref
erred)
Link-local IPv6 Address . . . . . : fe80::1457:1e4f:3f57:fac8%13(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled


Report •

#6
October 20, 2011 at 14:05:33
As mentioned earlier, you need to use your internal DNS server, on the server, to resolve all queries from computers on your network. You are pointing to some external DNS servers which will know nothing about your Windows domain.

Report •

#7
October 20, 2011 at 15:32:25
exactly right. workstation dns entry should be 192.168.5.1

understanding how AD dns works is key. This is a basic.

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

Ask Question