DNS error while trying to connect to AD error 0x0000232B

killmasta93 · 19 May 2015

Hi,

So my issue is when a computer tries to connect to the domain it says domain could not be contacted. So my server ip is 192.168.3.253 it has DNS and DHCP with AD and my gateway is 192.168.3.254. So i ran a ipconfig/all everything seems to be good. I then ran nslookup and was good too. But then i ran dcdiag /test:dns and i got an error. I also notice when i connect to WIFI it connect but shows the SSID then below says private network. Usually when i connect to clients that have AD it should show SSID then below the domain.local part. Im not sure maybe that might be the issue. If anyone could guide me or tell me if i missed something.

heres the link to see the error photos

************** / gallery - Clipboarder 2015 05 18 010, Clipboarder 2015 05 18 021, Clipboarder 2015 05 18 022

Thank you

Testing server: Default-First-Site-Name\ZEUS
Starting test: Connectivity
The host 8dd8e9a2-e109-46d3-9978-1f085bac3f8d._msdcs.casa.local 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.

TEST: Basic (Basc)
Error: No LDAP connectivity
Warning: adapter
[00000010] NVIDIA nForce Networking Controller has invalid
DNS server: 192.168.3.253 (ZEUS)
Error: all DNS servers are invalid
No host records (A or AAAA) were found for this DC

TEST: Records registration (RReg)
Error: Record registrations cannot be found for all the network
adapters

Summary of test results for DNS servers used by the above domain
controllers:

DNS server: 192.168.3.253 (ZEUS)
1 test failure on this DNS server
Name resolution is not functional. _ldap._tcp.casa.local. failed
on the DNS server 192.168.3.253

Summary of DNS test results:

Auth Basc Forw Del Dyn RReg Ext
_________________________________________________________________
Domain: casa.local
Zeus PASS FAIL PASS PASS WARN FAIL n/a

......................... casa.local failed test DNS

EDIT: allright so something happened really weird..When I put on the client computer in the domain section to connect casa.local it wont work but if i only put the casa and not the.local it connects Soo odd. Then WIFI now shows connected to the local domain not sure what happened.

Could anyone explain why it didn't work with casa.local instead with casa?

also i run dcdiag on the server and get everything passed besides this error

Testing server: Default-First-Site-Name\ZEUS
Starting test: Connectivity
The host 8dd8e9a2-e109-46d3-9978-1f085bac3f8d._msdcs.casa.local 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.
......................... ZEUS failed test Connectivity

GokAy · 20 May 2015

Haven't worked in domain environment for a long time so just guessing here.

Go to advanced properties of IP v4, DNS tab, check the suffix settings. It is possible that another suffix is added tocasa.local so it becomes (say) casa.local.local, but it works with just casa since it becomes casa.local transparently.

As I said it has been long time, but wont hurt to try those settings. Experiment. And sorry if this is nonsense! :)

killmasta93 · 20 May 2015

Hi thank you for your response. I ended up starting clean again my mistake at the beginning was installing DNS first. The order in installing is crucial. First install Active directory domain services (which it also installs DNS) as soon as it finishes a yellow flag icon will appear and you need to promote the computer to the directory. After promoting (adding the domain name) you need to restart so when it start it should show domain\administrator log back in and install DHCP then reboot. After that configure the DNS server which now shows the missing files i had the issue with after configuring the DNS then configure the DHCP server and if your router is handling the DHCP turn if off so windows can handle it.
Hope this helps someone else

Thank you again