Windows Server 2000/2003 Thread, Some machines not getting dns in Technical; Hey guys,
Sorry i'm getting a sore head from this one.... So here goes... Server that does DHCP decided to ...
-
28th September 2011, 12:17 PM #1 Some machines not getting dns
Hey guys,
Sorry i'm getting a sore head from this one.... So here goes... Server that does DHCP decided to crash out monday night, So came in tuesday restarted it, wasn't giving out ip addresses, Turned off the old wds that was on it, then bound the ip address so it could then give out ip addresses, then everywhere is getting IP addresses again... but now some machines are getting a usable dns and some arn't, We have 2 dns servers both seem to be happy(Can use nslookup on both of them and seems to resolve fine)
Some of the machines (Doesn't seem to be a pattern what so ever) and when i say some we have 3 IT rooms that have 30 machines each that are doing as they should, where as some of them only get 3 working out of the 30(Whose that arn't working are receiving "there are currently no logon servers available to service the logon request")
Now doing dcdiag /test
NS does give me:
Code:
C:\Program Files\Support Tools>dcdiag /test:dns
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\STAFF-SERVER
Starting test: Connectivity
......................... STAFF-SERVER passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\STAFF-SERVER
DNS Tests are running and not hung. Please wait a few minutes...
Running partition tests on : DomainDnsZones
Running partition tests on : ForestDnsZones
Running partition tests on : Schema
Running partition tests on : Configuration
Running partition tests on : nsnet
Running enterprise tests on : nsnet.net
Starting test: DNS
Test results for domain controllers:
DC: Staff-Server.nsnet.net
Domain: nsnet.net
TEST: Forwarders/Root hints (Forw)
Error: Root hints list has invalid root hint server: a.root-se
rvers.net. (198.41.0.4)
Error: Root hints list has invalid root hint server: b.root-se
rvers.net. (192.228.79.201)
Error: Root hints list has invalid root hint server: c.root-se
rvers.net. (192.33.4.12)
Error: Root hints list has invalid root hint server: d.root-se
rvers.net. (128.8.10.90)
Error: Root hints list has invalid root hint server: e.root-se
rvers.net. (192.203.230.10)
Error: Root hints list has invalid root hint server: f.root-se
rvers.net. (192.5.5.241)
Error: Root hints list has invalid root hint server: g.root-se
rvers.net. (192.112.36.4)
Error: Root hints list has invalid root hint server: h.root-se
rvers.net. (128.63.2.53)
Error: Root hints list has invalid root hint server: i.root-se
rvers.net. (192.36.148.17)
Error: Root hints list has invalid root hint server: j.root-se
rvers.net. (192.58.128.30)
Error: Root hints list has invalid root hint server: k.root-se
rvers.net. (193.0.14.129)
Error: Root hints list has invalid root hint server: l.root-se
rvers.net. (199.7.83.42)
Error: Root hints list has invalid root hint server: m.root-se
rvers.net. (202.12.27.33)
TEST: Dynamic update (Dyn)
Warning: Dynamic update is enabled on the zone but not secure
nsnet.net.
Summary of test results for DNS servers used by the above domain contro
llers:
DNS server: 128.63.2.53 (h.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 128.63.2.53
DNS server: 128.8.10.90 (d.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 128.8.10.90
DNS server: 192.112.36.4 (g.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 192.112.36.4
DNS server: 192.203.230.10 (e.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 192.203.230.10
DNS server: 192.228.79.201 (b.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 192.228.79.201
DNS server: 192.33.4.12 (c.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 192.33.4.12
DNS server: 192.36.148.17 (i.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 192.36.148.17
DNS server: 192.5.5.241 (f.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 192.5.5.241
DNS server: 192.58.128.30 (j.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 192.58.128.30
DNS server: 193.0.14.129 (k.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 193.0.14.129
DNS server: 198.41.0.4 (a.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 198.41.0.4
DNS server: 199.7.83.42 (l.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 199.7.83.42
DNS server: 202.12.27.33 (m.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 202.12.27.33
Summary of DNS test results:
Auth Basc Forw Del Dyn RReg Ext
________________________________________________________________
Domain: nsnet.net
Staff-Server PASS PASS FAIL PASS WARN PASS n/a
......................... nsnet.net failed test DNS
Now i'm not exactly sure where to go from here.... Any help would be much appreciated!
-
-
IDG Tech News
-
28th September 2011, 12:26 PM #2 What does just dcdiag give?
Ben
-
-
28th September 2011, 12:32 PM #3 Code:
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\STUDENT-SERVER
Starting test: Connectivity
......................... STUDENT-SERVER passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\STUDENT-SERVER
Starting test: Replications
......................... STUDENT-SERVER passed test Replications
Starting test: NCSecDesc
......................... STUDENT-SERVER passed test NCSecDesc
Starting test: NetLogons
......................... STUDENT-SERVER passed test NetLogons
Starting test: Advertising
......................... STUDENT-SERVER passed test Advertising
Starting test: KnowsOfRoleHolders
......................... STUDENT-SERVER passed test KnowsOfRoleHolders
Starting test: RidManager
......................... STUDENT-SERVER passed test RidManager
Starting test: MachineAccount
......................... STUDENT-SERVER passed test MachineAccount
Starting test: Services
......................... STUDENT-SERVER passed test Services
Starting test: ObjectsReplicated
......................... STUDENT-SERVER passed test ObjectsReplicated
Starting test: frssysvol
......................... STUDENT-SERVER passed test frssysvol
Starting test: frsevent
......................... STUDENT-SERVER passed test frsevent
Starting test: kccevent
......................... STUDENT-SERVER passed test kccevent
Starting test: systemlog
......................... STUDENT-SERVER passed test systemlog
Starting test: VerifyReferences
......................... STUDENT-SERVER passed test VerifyReferences
Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Running partition tests on : nsnet
Starting test: CrossRefValidation
......................... nsnet passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... nsnet passed test CheckSDRefDom
Running enterprise tests on : nsnet.net
Starting test: Intersite
......................... nsnet.net passed test Intersite
Starting test: FsmoCheck
......................... nsnet.net passed test FsmoCheck 2 DC's give that... One is giving an error about systemlog
Just to add something i noticed odd... on one of the clients that isn't playing ball i ran nslookup and i get Code:
Default Server: Unknown
Address: 172.16.0.10
> student-server
Server: Unknown
Address 172.16.0.10
Name: Student-server.nsnet.net
Address: 172.16.0.10
Last edited by Azhibberd; 28th September 2011 at 12:43 PM.
-
-
28th September 2011, 03:02 PM #4 Just been playing for abit and one machine we had working fine, with the machine next to it (on the same switch and vlan) refusing to see anything not on the same vlan could ping machines on its vlan and nothing outside its vlan, then 5 minutes later the one that was fine has stopped being able to see anything not on its vlan, Hence i'm guessings its not dns related, looked at the logs on the switch there on doesn't seem to be any problems... And well its not just that switch its happening on, Anyone got any bright ideas i should be looking at? Think next step is wait till end of the day and restart the core switch.. ?
**Looks like it was something really odd going on with the core switch, As a restart off that seems to have resolved the issues, Although we shall find out tomorrow**
Last edited by Azhibberd; 28th September 2011 at 06:39 PM.
-
-
29th September 2011, 03:32 PM #5 Corrupted Routing Table on the core switch due to the DHCP failing?
Clutching at straws really, ill let the more experienced networking people correct my above statement
-
SHARE: 
Similar Threads
-
By Clockworks in forum Windows
Replies: 2
Last Post: 9th September 2010, 03:58 PM
-
By marsdenprimary in forum Windows Server 2000/2003
Replies: 7
Last Post: 19th July 2010, 10:55 AM
-
By reprised in forum Windows
Replies: 3
Last Post: 28th May 2010, 03:38 PM
-
By Kyle in forum MIS Systems
Replies: 8
Last Post: 14th June 2007, 01:47 PM
-
Replies: 8
Last Post: 8th June 2007, 09:32 PM
Thread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules