|
|
|
|
||||||
![]() |
|
|
LinkBack | Outils de la discussion |
|
|
#1 |
|
Messages: n/a
Hébergeur: |
I have a couple of DNS servers in a child domain that report the following
when I run DCDIAG /test DNS. 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 2002.12.27.33 ----------- This happens for all the root hint entries. The upstream DNS servers in the parent domain are fine and have the same root hints listed. Any idea what the problem could be here? Thanks, Alex |
|
|
|
#2 |
|
Messages: n/a
Hébergeur: |
Hello Al,
Please post the complete dcdiag from one of the servers. I see also a posting in the AD NG about "Global catalog server communication in Paretn/Child" Are these the same machines? So please do not switch around in the NG's, because i think these all belongs together. If you have so many questions, let's do it step by step to find the good way for solutions. Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. > I have a couple of DNS servers in a child domain that report the > following when I run DCDIAG /test DNS. > > 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 2002.12.27.33 > > ----------- > This happens for all the root hint entries. The upstream DNS servers > in the > parent domain are fine and have the same root hints listed. Any idea > what the problem could be here? > > Thanks, > Alex |
|
|
|
#3 |
|
Messages: n/a
Hébergeur: |
Thanks Meinolf,
Here it is: C:\Documents and Settings\abrown>dcdiag /test:dns Domain Controller Diagnosis Performing initial setup: Done gathering initial info. Doing initial required tests Testing server: Housing\RESCOMP2 Starting test: Connectivity ......................... RESCOMP2 passed test Connectivity Doing primary tests Testing server: Housing\RESCOMP2 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 : rc Running partition tests on : Schema Running partition tests on : Configuration Running enterprise tests on : housing.ucsb.edu Starting test: DNS Test results for domain controllers: DC: rescomp2.rc.housing.ucsb.edu Domain: rc.housing.ucsb.edu TEST: Forwarders/Root hints (Forw) Error: Forwarders list has invalid forwarder: 128.111.1.1 (<na me unavailable>) Error: Forwarders list has invalid forwarder: 128.111.1.2 (<na me unavailable>) 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. (198.32.64.12) Error: Root hints list has invalid root hint server: m.root-se rvers.net. (202.12.27.33) Summary of test results for DNS servers used by the above domain contro llers: 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 Name resolution is not functional. _ldap._tcp.housing.ucsb.edu. f ailed on the DNS server 202.12.27.33 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 Name resolution is not functional. _ldap._tcp.housing.ucsb.edu. f ailed on the DNS server 198.41.0.4 DNS server: 198.32.64.12 (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 198.32.64.12 Name resolution is not functional. _ldap._tcp.housing.ucsb.edu. f ailed on the DNS server 198.32.64.12 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 Name resolution is not functional. _ldap._tcp.housing.ucsb.edu. f ailed on the DNS server 193.0.14.129 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 Name resolution is not functional. _ldap._tcp.housing.ucsb.edu. f ailed on the DNS server 192.58.128.30 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 Name resolution is not functional. _ldap._tcp.housing.ucsb.edu. f ailed on the DNS server 192.5.5.241 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 Name resolution is not functional. _ldap._tcp.housing.ucsb.edu. f ailed on the DNS server 192.36.148.17 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 Name resolution is not functional. _ldap._tcp.housing.ucsb.edu. f ailed on the DNS server 192.33.4.12 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 Name resolution is not functional. _ldap._tcp.housing.ucsb.edu. f ailed on the DNS server 192.228.79.201 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 Name resolution is not functional. _ldap._tcp.housing.ucsb.edu. f ailed on the DNS server 192.203.230.10 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 Name resolution is not functional. _ldap._tcp.housing.ucsb.edu. f ailed on the DNS server 192.112.36.4 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 Name resolution is not functional. _ldap._tcp.housing.ucsb.edu. f ailed on the DNS server 128.8.10.90 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 Name resolution is not functional. _ldap._tcp.housing.ucsb.edu. f ailed on the DNS server 128.63.2.53 DNS server: 128.111.1.2 (<name unavailable>) 1 test failure on this DNS server Name resolution is not functional. _ldap._tcp.housing.ucsb.edu. f ailed on the DNS server 128.111.1.2 DNS server: 128.111.1.1 (<name unavailable>) 1 test failure on this DNS server Name resolution is not functional. _ldap._tcp.housing.ucsb.edu. f ailed on the DNS server 128.111.1.1 Summary of DNS test results: Auth Basc Forw Del Dyn RReg Ext __________________________________________________ ______________ Domain: rc.housing.ucsb.edu rescomp2 PASS PASS FAIL PASS PASS PASS n/a ......................... housing.ucsb.edu failed test DNS I am the same person how posted the issue about GCs. I have a feeling they are different problems but we will see I guess. Thanks, Alex "Meinolf Weber" wrote: > Hello Al, > > Please post the complete dcdiag from one of the servers. I see also a posting > in the AD NG about "Global catalog server communication in Paretn/Child" > Are these the same machines? So please do not switch around in the NG's, > because i think these all belongs together. If you have so many questions, > let's do it step by step to find the good way for solutions. > > Best regards > > Meinolf Weber > Disclaimer: This posting is provided "AS IS" with no warranties, and confers > no rights. > > > I have a couple of DNS servers in a child domain that report the > > following when I run DCDIAG /test DNS. > > > > 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 2002.12.27.33 > > > > ----------- > > This happens for all the root hint entries. The upstream DNS servers > > in the > > parent domain are fine and have the same root hints listed. Any idea > > what the problem could be here? > > > > Thanks, > > Alex > > > |
|
|
|
#4 |
|
Messages: n/a
Hébergeur: |
Hello Al,
How is your domain DNS configured, from this dcdiag i can not see any internal ipconfiguration. Please give some info about the setting in the subdomains and also the level above. Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. > Thanks Meinolf, > > Here it is: > > C:\Documents and Settings\abrown>dcdiag /test:dns > > Domain Controller Diagnosis > > Performing initial setup: > Done gathering initial info. > Doing initial required tests > > Testing server: Housing\RESCOMP2 > Starting test: Connectivity > ......................... RESCOMP2 passed test Connectivity > Doing primary tests > > Testing server: Housing\RESCOMP2 > > 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 : rc > > Running partition tests on : Schema > > Running partition tests on : Configuration > > Running enterprise tests on : housing.ucsb.edu > Starting test: DNS > Test results for domain controllers: > DC: rescomp2.rc.housing.ucsb.edu > Domain: rc.housing.ucsb.edu > TEST: Forwarders/Root hints (Forw) > Error: Forwarders list has invalid forwarder: > 128.111.1.1 > (<na > me unavailable>) > Error: Forwarders list has invalid forwarder: > 128.111.1.2 > (<na > me unavailable>) > 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. (198.32.64.12) > Error: Root hints list has invalid root hint server: > m.root-se > rvers.net. (202.12.27.33) > > Summary of test results for DNS servers used by the above > domain > contro > llers: > 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 > Name resolution is not functional. > _ldap._tcp.housing.ucsb.edu. f > ailed on the DNS server 202.12.27.33 > > 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 > Name resolution is not functional. > _ldap._tcp.housing.ucsb.edu. f > ailed on the DNS server 198.41.0.4 > > DNS server: 198.32.64.12 (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 198.32.64.12 > Name resolution is not functional. > _ldap._tcp.housing.ucsb.edu. f > ailed on the DNS server 198.32.64.12 > > 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 > Name resolution is not functional. > _ldap._tcp.housing.ucsb.edu. f > ailed on the DNS server 193.0.14.129 > > 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 > Name resolution is not functional. > _ldap._tcp.housing.ucsb.edu. f > ailed on the DNS server 192.58.128.30 > > 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 > Name resolution is not functional. > _ldap._tcp.housing.ucsb.edu. f > ailed on the DNS server 192.5.5.241 > > 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 > Name resolution is not functional. > _ldap._tcp.housing.ucsb.edu. f > ailed on the DNS server 192.36.148.17 > > 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 > Name resolution is not functional. > _ldap._tcp.housing.ucsb.edu. f > ailed on the DNS server 192.33.4.12 > > 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 > Name resolution is not functional. > _ldap._tcp.housing.ucsb.edu. f > ailed on the DNS server 192.228.79.201 > > 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 > Name resolution is not functional. > _ldap._tcp.housing.ucsb.edu. f > ailed on the DNS server 192.203.230.10 > > 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 > Name resolution is not functional. > _ldap._tcp.housing.ucsb.edu. f > ailed on the DNS server 192.112.36.4 > > 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 > Name resolution is not functional. > _ldap._tcp.housing.ucsb.edu. f > ailed on the DNS server 128.8.10.90 > > 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 > Name resolution is not functional. > _ldap._tcp.housing.ucsb.edu. f > ailed on the DNS server 128.63.2.53 > > DNS server: 128.111.1.2 (<name unavailable>) > 1 test failure on this DNS server > Name resolution is not functional. > _ldap._tcp.housing.ucsb.edu. f > ailed on the DNS server 128.111.1.2 > > DNS server: 128.111.1.1 (<name unavailable>) > 1 test failure on this DNS server > Name resolution is not functional. > _ldap._tcp.housing.ucsb.edu. f > ailed on the DNS server 128.111.1.1 > > Summary of DNS test results: > > Auth Basc Forw Del Dyn > RReg Ext > > __________________________________________________ ______________ > Domain: rc.housing.ucsb.edu > rescomp2 PASS PASS FAIL PASS PASS > PASS n/a > ......................... housing.ucsb.edu failed test DNS > > I am the same person how posted the issue about GCs. I have a feeling > they are different problems but we will see I guess. > > Thanks, > Alex > "Meinolf Weber" wrote: > >> Hello Al, >> >> Please post the complete dcdiag from one of the servers. I see also a >> posting in the AD NG about "Global catalog server communication in >> Paretn/Child" Are these the same machines? So please do not switch >> around in the NG's, because i think these all belongs together. If >> you have so many questions, let's do it step by step to find the good >> way for solutions. >> >> Best regards >> >> Meinolf Weber >> Disclaimer: This posting is provided "AS IS" with no warranties, and >> confers >> no rights. >>> I have a couple of DNS servers in a child domain that report the >>> following when I run DCDIAG /test DNS. >>> >>> 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 2002.12.27.33 >>> >>> ----------- >>> This happens for all the root hint entries. The upstream DNS servers >>> in the >>> parent domain are fine and have the same root hints listed. Any idea >>> what the problem could be here? >>> Thanks, >>> Alex |
|
|
|
#5 |
|
Messages: n/a
Hébergeur: |
What setting are you looking for?
"Meinolf Weber" wrote: > Hello Al, > > How is your domain DNS configured, from this dcdiag i can not see any internal > ipconfiguration. Please give some info about the setting in the subdomains > and also the level above. > > Best regards > > Meinolf Weber > Disclaimer: This posting is provided "AS IS" with no warranties, and confers > no rights. > > > Thanks Meinolf, > > > > Here it is: > > > > C:\Documents and Settings\abrown>dcdiag /test:dns > > > > Domain Controller Diagnosis > > > > Performing initial setup: > > Done gathering initial info. > > Doing initial required tests > > > > Testing server: Housing\RESCOMP2 > > Starting test: Connectivity > > ......................... RESCOMP2 passed test Connectivity > > Doing primary tests > > > > Testing server: Housing\RESCOMP2 > > > > 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 : rc > > > > Running partition tests on : Schema > > > > Running partition tests on : Configuration > > > > Running enterprise tests on : housing.ucsb.edu > > Starting test: DNS > > Test results for domain controllers: > > DC: rescomp2.rc.housing.ucsb.edu > > Domain: rc.housing.ucsb.edu > > TEST: Forwarders/Root hints (Forw) > > Error: Forwarders list has invalid forwarder: > > 128.111.1.1 > > (<na > > me unavailable>) > > Error: Forwarders list has invalid forwarder: > > 128.111.1.2 > > (<na > > me unavailable>) > > 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. (198.32.64.12) > > Error: Root hints list has invalid root hint server: > > m.root-se > > rvers.net. (202.12.27.33) > > > > Summary of test results for DNS servers used by the above > > domain > > contro > > llers: > > 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 > > Name resolution is not functional. > > _ldap._tcp.housing.ucsb.edu. f > > ailed on the DNS server 202.12.27.33 > > > > 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 > > Name resolution is not functional. > > _ldap._tcp.housing.ucsb.edu. f > > ailed on the DNS server 198.41.0.4 > > > > DNS server: 198.32.64.12 (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 198.32.64.12 > > Name resolution is not functional. > > _ldap._tcp.housing.ucsb.edu. f > > ailed on the DNS server 198.32.64.12 > > > > 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 > > Name resolution is not functional. > > _ldap._tcp.housing.ucsb.edu. f > > ailed on the DNS server 193.0.14.129 > > > > 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 > > Name resolution is not functional. > > _ldap._tcp.housing.ucsb.edu. f > > ailed on the DNS server 192.58.128.30 > > > > 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 > > Name resolution is not functional. > > _ldap._tcp.housing.ucsb.edu. f > > ailed on the DNS server 192.5.5.241 > > > > 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 > > Name resolution is not functional. > > _ldap._tcp.housing.ucsb.edu. f > > ailed on the DNS server 192.36.148.17 > > > > 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 > > Name resolution is not functional. > > _ldap._tcp.housing.ucsb.edu. f > > ailed on the DNS server 192.33.4.12 > > > > 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 > > Name resolution is not functional. > > _ldap._tcp.housing.ucsb.edu. f > > ailed on the DNS server 192.228.79.201 > > > > 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 > > Name resolution is not functional. > > _ldap._tcp.housing.ucsb.edu. f > > ailed on the DNS server 192.203.230.10 > > > > 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 > > Name resolution is not functional. > > _ldap._tcp.housing.ucsb.edu. f > > ailed on the DNS server 192.112.36.4 > > > > 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 > > Name resolution is not functional. > > _ldap._tcp.housing.ucsb.edu. f > > ailed on the DNS server 128.8.10.90 > > > > 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 > > Name resolution is not functional. > > _ldap._tcp.housing.ucsb.edu. f > > ailed on the DNS server 128.63.2.53 > > > > DNS server: 128.111.1.2 (<name unavailable>) > > 1 test failure on this DNS server > > Name resolution is not functional. > > _ldap._tcp.housing.ucsb.edu. f > > ailed on the DNS server 128.111.1.2 > > > > DNS server: 128.111.1.1 (<name unavailable>) > > 1 test failure on this DNS server > > Name resolution is not functional. > > _ldap._tcp.housing.ucsb.edu. f > > ailed on the DNS server 128.111.1.1 > > > > Summary of DNS test results: > > > > Auth Basc Forw Del Dyn > > RReg Ext > > > > __________________________________________________ ______________ > > Domain: rc.housing.ucsb.edu > > rescomp2 PASS PASS FAIL PASS PASS > > PASS n/a > > ......................... housing.ucsb.edu failed test DNS > > > > I am the same person how posted the issue about GCs. I have a feeling > > they are different problems but we will see I guess. > > > > Thanks, > > Alex > > "Meinolf Weber" wrote: > > > >> Hello Al, > >> > >> Please post the complete dcdiag from one of the servers. I see also a > >> posting in the AD NG about "Global catalog server communication in > >> Paretn/Child" Are these the same machines? So please do not switch > >> around in the NG's, because i think these all belongs together. If > >> you have so many questions, let's do it step by step to find the good > >> way for solutions. > >> > >> Best regards > >> > >> Meinolf Weber > >> Disclaimer: This posting is provided "AS IS" with no warranties, and > >> confers > >> no rights. > >>> I have a couple of DNS servers in a child domain that report the > >>> following when I run DCDIAG /test DNS. > >>> > >>> 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 2002.12.27.33 > >>> > >>> ----------- > >>> This happens for all the root hint entries. The upstream DNS servers > >>> in the > >>> parent domain are fine and have the same root hints listed. Any idea > >>> what the problem could be here? > >>> Thanks, > >>> Alex > > > |
|
|
|
#6 |
|
Messages: n/a
Hébergeur: |
Hello Al,
How your DNS is set up. Internal and the external part. Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. > What setting are you looking for? > > "Meinolf Weber" wrote: > >> Hello Al, >> >> How is your domain DNS configured, from this dcdiag i can not see any >> internal ipconfiguration. Please give some info about the setting in >> the subdomains and also the level above. >> >> Best regards >> >> Meinolf Weber >> Disclaimer: This posting is provided "AS IS" with no warranties, and >> confers >> no rights. >>> Thanks Meinolf, >>> >>> Here it is: >>> >>> C:\Documents and Settings\abrown>dcdiag /test:dns >>> >>> Domain Controller Diagnosis >>> >>> Performing initial setup: >>> Done gathering initial info. >>> Doing initial required tests >>> Testing server: Housing\RESCOMP2 >>> Starting test: Connectivity >>> ......................... RESCOMP2 passed test Connectivity >>> Doing primary tests >>> Testing server: Housing\RESCOMP2 >>> >>> 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 : rc >>> >>> Running partition tests on : Schema >>> >>> Running partition tests on : Configuration >>> >>> Running enterprise tests on : housing.ucsb.edu >>> Starting test: DNS >>> Test results for domain controllers: >>> DC: rescomp2.rc.housing.ucsb.edu >>> Domain: rc.housing.ucsb.edu >>> TEST: Forwarders/Root hints (Forw) >>> Error: Forwarders list has invalid forwarder: >>> 128.111.1.1 >>> (<na >>> me unavailable>) >>> Error: Forwarders list has invalid forwarder: >>> 128.111.1.2 >>> (<na >>> me unavailable>) >>> 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. (198.32.64.12) >>> Error: Root hints list has invalid root hint server: >>> m.root-se >>> rvers.net. (202.12.27.33) >>> Summary of test results for DNS servers used by the above >>> domain >>> contro >>> llers: >>> 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 >>> Name resolution is not functional. >>> _ldap._tcp.housing.ucsb.edu. f >>> ailed on the DNS server 202.12.27.33 >>> 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 >>> Name resolution is not functional. >>> _ldap._tcp.housing.ucsb.edu. f >>> ailed on the DNS server 198.41.0.4 >>> DNS server: 198.32.64.12 (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 198.32.64.12 >>> Name resolution is not functional. >>> _ldap._tcp.housing.ucsb.edu. f >>> ailed on the DNS server 198.32.64.12 >>> 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 >>> Name resolution is not functional. >>> _ldap._tcp.housing.ucsb.edu. f >>> ailed on the DNS server 193.0.14.129 >>> 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 >>> Name resolution is not functional. >>> _ldap._tcp.housing.ucsb.edu. f >>> ailed on the DNS server 192.58.128.30 >>> 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 >>> Name resolution is not functional. >>> _ldap._tcp.housing.ucsb.edu. f >>> ailed on the DNS server 192.5.5.241 >>> 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 >>> Name resolution is not functional. >>> _ldap._tcp.housing.ucsb.edu. f >>> ailed on the DNS server 192.36.148.17 >>> 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 >>> Name resolution is not functional. >>> _ldap._tcp.housing.ucsb.edu. f >>> ailed on the DNS server 192.33.4.12 >>> 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 >>> Name resolution is not functional. >>> _ldap._tcp.housing.ucsb.edu. f >>> ailed on the DNS server 192.228.79.201 >>> 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 >>> Name resolution is not functional. >>> _ldap._tcp.housing.ucsb.edu. f >>> ailed on the DNS server 192.203.230.10 >>> 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 >>> Name resolution is not functional. >>> _ldap._tcp.housing.ucsb.edu. f >>> ailed on the DNS server 192.112.36.4 >>> 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 >>> Name resolution is not functional. >>> _ldap._tcp.housing.ucsb.edu. f >>> ailed on the DNS server 128.8.10.90 >>> 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 >>> Name resolution is not functional. >>> _ldap._tcp.housing.ucsb.edu. f >>> ailed on the DNS server 128.63.2.53 >>> DNS server: 128.111.1.2 (<name unavailable>) >>> 1 test failure on this DNS server >>> Name resolution is not functional. >>> _ldap._tcp.housing.ucsb.edu. f >>> ailed on the DNS server 128.111.1.2 >>> DNS server: 128.111.1.1 (<name unavailable>) >>> 1 test failure on this DNS server >>> Name resolution is not functional. >>> _ldap._tcp.housing.ucsb.edu. f >>> ailed on the DNS server 128.111.1.1 >>> Summary of DNS test results: >>> >>> Auth Basc Forw Del Dyn >>> RReg Ext >>> __________________________________________________ ______________ >>> Domain: rc.housing.ucsb.edu >>> rescomp2 PASS PASS FAIL PASS PASS >>> PASS n/a >>> ......................... housing.ucsb.edu failed test DNS >>> I am the same person how posted the issue about GCs. I have a >>> feeling they are different problems but we will see I guess. >>> >>> Thanks, >>> Alex >>> "Meinolf Weber" wrote: >>>> Hello Al, >>>> >>>> Please post the complete dcdiag from one of the servers. I see also >>>> a posting in the AD NG about "Global catalog server communication >>>> in Paretn/Child" Are these the same machines? So please do not >>>> switch around in the NG's, because i think these all belongs >>>> together. If you have so many questions, let's do it step by step >>>> to find the good way for solutions. >>>> >>>> Best regards >>>> >>>> Meinolf Weber >>>> Disclaimer: This posting is provided "AS IS" with no warranties, >>>> and >>>> confers >>>> no rights. >>>>> I have a couple of DNS servers in a child domain that report the >>>>> following when I run DCDIAG /test DNS. >>>>> >>>>> 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 2002.12.27.33 >>>>> >>>>> ----------- >>>>> This happens for all the root hint entries. The upstream DNS >>>>> servers >>>>> in the >>>>> parent domain are fine and have the same root hints listed. Any >>>>> idea >>>>> what the problem could be here? >>>>> Thanks, >>>>> Alex |
|
|
|
#7 |
|
Messages: n/a
Hébergeur: |
If you are using an ISP I would suggest you remove your root hints from your
internal dns server and forward all unknown requests to your ISP's dns server. If you are also having other problems in your domain I wouldn't even attempt to figure anything else out until you clean up dns. Poor configured dns is the problem for a lot of AD administrators. http://support.microsoft.com/kb/291382 -- Paul Bergson MVP - Directory Services MCT, MCSE, MCSA, Security+, BS CSci 2003, 2000 (Early Achiever), NT http://www.pbbergs.com Please no e-mails, any questions should be posted in the NewsGroup This posting is provided "AS IS" with no warranties, and confers no rights. "al" <al@discussions.microsoft.com> wrote in message news:29394177-A147-4899-BB84-7353A899B077@microsoft.com... >I have a couple of DNS servers in a child domain that report the following > when I run DCDIAG /test DNS. > > 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 2002.12.27.33 > ----------- > This happens for all the root hint entries. The upstream DNS servers in > the > parent domain are fine and have the same root hints listed. Any idea what > the > problem could be here? > > Thanks, > Alex |
|
![]() |
| Outils de la discussion | |
|
|