drdanskin
asked on
dns on sbs 2011
I have a new install of sbs2011. my dns is not working correctly. I've added 3 forwarders and it shows me the fqdn but i get timed out validating. i've increased the timeout from 3 to 5, i've removed the ipv6 adapters and only have the ipv4 assigned. when i launch nslookup from the dns console i get the ip address of the server and server name is unknown. I can receive einternet emails and workstations with a secondary internet dns server have access. us root hints are unchecked. there are no conditional forwarders and there is nothing in my reverse lookup zone.
First, don't remove IPv6. One of the most common problems with SBS is that people start digging into the system and break more than they fix. Run the Fix My Network Wizard and at least get things as close to original as possible.
then, please post a full output or screenshot of an nslookup exampel that you've tried. your post left a few ambiguities that, instead of playing 20 questions, I can get an answer to just from the output. Finally, please post an ipconfig /all from the server.
-Cliff
then, please post a full output or screenshot of an nslookup exampel that you've tried. your post left a few ambiguities that, instead of playing 20 questions, I can get an answer to just from the output. Finally, please post an ipconfig /all from the server.
-Cliff
ASKER
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Administrator>nsl ookup www.google.com
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: ::1
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
C:\Users\Administrator>dcd iag /test:dns
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
Home Server = BONASYS
* Identified AD Forest.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\BO NASYS
Starting test: Connectivity
......................... BONASYS passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\BO NASYS
Starting test: DNS
DNS Tests are running and not hung. Please wait a few minutes...
......................... BONASYS 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 : bonafidesystems
Running enterprise tests on : bonafidesystems.local
Starting test: DNS
Test results for domain controllers:
DC: BONASYS.bonafidesystems.lo cal
Domain: bonafidesystems.local
TEST: Basic (Basc)
Warning: adapter
[00000007] Broadcom NetXtreme Gigabit Ethernet has invalid
DNS server: 4.2.2.2 (<name unavailable>)
TEST: Forwarders/Root hints (Forw)
Error: All forwarders in the forwarder list are invalid.
TEST: Records registration (RReg)
Network Adapter
[00000007] Broadcom NetXtreme Gigabit Ethernet:
Warning:
Missing CNAME record at DNS server 4.2.2.2:
33649bf9-fa66-458d-bcd9-f8 6a74e6249d ._msdcs.bo nafidesyst ems
.local
Warning:
Missing A record at DNS server 4.2.2.2:
BONASYS.bonafidesystems.lo cal
Error:
Missing SRV record at DNS server 4.2.2.2:
_ldap._tcp.bonafidesystems .local
Error:
Missing SRV record at DNS server 4.2.2.2:
_ldap._tcp.4584f099-4f18-4 b41-9d37-2 493eaf5818 7.domains. _ms
dcs.bonafidesystems.local
Error:
Missing SRV record at DNS server 4.2.2.2:
_kerberos._tcp.dc._msdcs.b onafidesys tems.local
Error:
Missing SRV record at DNS server 4.2.2.2:
_ldap._tcp.dc._msdcs.bonaf idesystems .local
Error:
Missing SRV record at DNS server 4.2.2.2:
_kerberos._tcp.bonafidesys tems.local
Error:
Missing SRV record at DNS server 4.2.2.2:
_kerberos._udp.bonafidesys tems.local
Error:
Missing SRV record at DNS server 4.2.2.2:
_kpasswd._tcp.bonafidesyst ems.local
Error:
Missing SRV record at DNS server 4.2.2.2:
_ldap._tcp.Default-First-S ite-Name._ sites.bona fidesystem s.l
ocal
Error:
Missing SRV record at DNS server 4.2.2.2:
_kerberos._tcp.Default-Fir st-Site-Na me._sites. dc._msdcs. bon
afidesystems.local
Error:
Missing SRV record at DNS server 4.2.2.2:
_ldap._tcp.Default-First-S ite-Name._ sites.dc._ msdcs.bona fid
esystems.local
Error:
Missing SRV record at DNS server 4.2.2.2:
_kerberos._tcp.Default-Fir st-Site-Na me._sites. bonafidesy ste
ms.local
Error:
Missing SRV record at DNS server 4.2.2.2:
_ldap._tcp.gc._msdcs.bonaf idesystems .local
Warning:
Missing A record at DNS server 4.2.2.2:
gc._msdcs.bonafidesystems. local
Error:
Missing SRV record at DNS server 4.2.2.2:
_gc._tcp.Default-First-Sit e-Name._si tes.bonafi desystems. loc
al
Error:
Missing SRV record at DNS server 4.2.2.2:
_ldap._tcp.Default-First-S ite-Name._ sites.gc._ msdcs.bona fid
esystems.local
Error:
Missing SRV record at DNS server 4.2.2.2:
_ldap._tcp.pdc._msdcs.bona fidesystem s.local
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: 4.2.2.2 (<name unavailable>)
1 test failure on this DNS server
Name resolution is not functional. _ldap._tcp.bonafidesystems .loc
al. failed on the DNS server 4.2.2.2
DNS server: 65.24.0.168 (<name unavailable>)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DN
S server 65.24.0.168
DNS server: 68.237.161.12 (<name unavailable>)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DN
S server 68.237.161.12
DNS server: 71.250.0.12 (<name unavailable>)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DN
S server 71.250.0.12
Summary of DNS test results:
Auth Basc Forw Del Dyn RReg Ext
__________________________ __________ __________ __________ _________
Domain: bonafidesystems.local
BONASYS PASS WARN FAIL PASS PASS FAIL n/a
......................... bonafidesystems.local failed test DNS
4.2.2.2 is the secondary dns in the adapters tcp settings
C:\Users\Administrator>net diag /q
'netdiag' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\Administrator>
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Administrator>nsl
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: ::1
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
C:\Users\Administrator>dcd
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
Home Server = BONASYS
* Identified AD Forest.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\BO
Starting test: Connectivity
......................... BONASYS passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\BO
Starting test: DNS
DNS Tests are running and not hung. Please wait a few minutes...
......................... BONASYS 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 : bonafidesystems
Running enterprise tests on : bonafidesystems.local
Starting test: DNS
Test results for domain controllers:
DC: BONASYS.bonafidesystems.lo
Domain: bonafidesystems.local
TEST: Basic (Basc)
Warning: adapter
[00000007] Broadcom NetXtreme Gigabit Ethernet has invalid
DNS server: 4.2.2.2 (<name unavailable>)
TEST: Forwarders/Root hints (Forw)
Error: All forwarders in the forwarder list are invalid.
TEST: Records registration (RReg)
Network Adapter
[00000007] Broadcom NetXtreme Gigabit Ethernet:
Warning:
Missing CNAME record at DNS server 4.2.2.2:
33649bf9-fa66-458d-bcd9-f8
.local
Warning:
Missing A record at DNS server 4.2.2.2:
BONASYS.bonafidesystems.lo
Error:
Missing SRV record at DNS server 4.2.2.2:
_ldap._tcp.bonafidesystems
Error:
Missing SRV record at DNS server 4.2.2.2:
_ldap._tcp.4584f099-4f18-4
dcs.bonafidesystems.local
Error:
Missing SRV record at DNS server 4.2.2.2:
_kerberos._tcp.dc._msdcs.b
Error:
Missing SRV record at DNS server 4.2.2.2:
_ldap._tcp.dc._msdcs.bonaf
Error:
Missing SRV record at DNS server 4.2.2.2:
_kerberos._tcp.bonafidesys
Error:
Missing SRV record at DNS server 4.2.2.2:
_kerberos._udp.bonafidesys
Error:
Missing SRV record at DNS server 4.2.2.2:
_kpasswd._tcp.bonafidesyst
Error:
Missing SRV record at DNS server 4.2.2.2:
_ldap._tcp.Default-First-S
ocal
Error:
Missing SRV record at DNS server 4.2.2.2:
_kerberos._tcp.Default-Fir
afidesystems.local
Error:
Missing SRV record at DNS server 4.2.2.2:
_ldap._tcp.Default-First-S
esystems.local
Error:
Missing SRV record at DNS server 4.2.2.2:
_kerberos._tcp.Default-Fir
ms.local
Error:
Missing SRV record at DNS server 4.2.2.2:
_ldap._tcp.gc._msdcs.bonaf
Warning:
Missing A record at DNS server 4.2.2.2:
gc._msdcs.bonafidesystems.
Error:
Missing SRV record at DNS server 4.2.2.2:
_gc._tcp.Default-First-Sit
al
Error:
Missing SRV record at DNS server 4.2.2.2:
_ldap._tcp.Default-First-S
esystems.local
Error:
Missing SRV record at DNS server 4.2.2.2:
_ldap._tcp.pdc._msdcs.bona
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: 4.2.2.2 (<name unavailable>)
1 test failure on this DNS server
Name resolution is not functional. _ldap._tcp.bonafidesystems
al. failed on the DNS server 4.2.2.2
DNS server: 65.24.0.168 (<name unavailable>)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DN
S server 65.24.0.168
DNS server: 68.237.161.12 (<name unavailable>)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DN
S server 68.237.161.12
DNS server: 71.250.0.12 (<name unavailable>)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DN
S server 71.250.0.12
Summary of DNS test results:
Auth Basc Forw Del Dyn RReg Ext
__________________________
Domain: bonafidesystems.local
BONASYS PASS WARN FAIL PASS PASS FAIL n/a
......................... bonafidesystems.local failed test DNS
4.2.2.2 is the secondary dns in the adapters tcp settings
C:\Users\Administrator>net
'netdiag' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\Administrator>
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I agree with abhijitwaikar but if you set up the server properly using the "connect to the internet" and "configure my internet address" wizards that should have been properly set originally. If you haven't run the wizards to set up the server please do so. If you have please remove and run the "fix my network" wizard that cgaliher suggested.
In a Windows domain the server must point ONLY to its' internal DNS servers, in this case the SBS, and all PC's must point ONLY to the SBS. Also as pointed out IPv6 must be left enabled, and SBS must be the DHCP server, though there are workarounds for that if you must do so.
Always use the wizards with SBS.
In a Windows domain the server must point ONLY to its' internal DNS servers, in this case the SBS, and all PC's must point ONLY to the SBS. Also as pointed out IPv6 must be left enabled, and SBS must be the DHCP server, though there are workarounds for that if you must do so.
Always use the wizards with SBS.
ASKER
removed the 4.2.2.2 still had issues. isp is verizon. put in 4 verizon dns servers that i use for another customer with his 85 stores and none could validate. finally added a paetec, at&t and roadrunner dns server and only the paetec came back ok. removed the others and added a second paetec and all is well.
I assume you added as a forwarders and not to the NIC. If you added to the NIC I guarantee you will have further issues.
ASKER
correct. as a forwarder
Its not a problem, It shows the "unknown" because the reverse lookup zone is not configured or pointer record of the DNS server is missing.
My dns is not working correctly.
To check the health of DNS and DC run the dcdiag /test:dns and netdiag /q command and post the result if there is any issue.
Also make sure that server pointing itself as a primary/preferred DNS server in NIC.
Regards,