Solved

What kind of DNS Problem is this and how bad is it?

Posted on 2008-06-23
2
275 Views
Last Modified: 2013-12-05
I was testing some group policies, and tried to run the group policy results wizard in GPMC against a pc and got

the following:

RPC Server is unavailable.

I read and used some steps in this article:
http://technet.microsoft.com/en-us/magazine/cc138001.aspx.  Good article but didn't help me.

On our primary DC, which runs Windows 2k sp4, I ran repadmin /showreps and all the replication came back ok.

I also ran the following with the results below:

dcdiag
Skipping all tests, because server SERVER1 is
not responding to directory service requests

dcdiag /test:connectivity
   Starting test: Connectivity
      SERVER1's server GUID DNS name could not be resolved to an
      IP address.  Check the DNS server, DHCP, server name, etc
      Although the Guid DNS name (3bdc1b6f-776e-4652-9fe8-518e4515860d._msdcs.domain.name)
      couldn't be resolved, the server name (SERVER1) resolved to the IP address
      (192.168.*.*) and was pingable.  Check that the IP address is registered correctly with
      the DNS server.
      ......................... <SERVER1> failed test Connectivity


Our Second DC is running Win2003 R2 SP2.  Ran DCDIAG on this domain controller, SERVER2

dcdiag /test:dns
   Running enterprise tests on : DOMAIN.NAME
      Starting test: DNS
         Test results for domain controllers:

            DC: SERVER2.DOMAIN.NAME
            Domain: DOMAIN.NAME

          TEST: Basic (Basc)
               Warning: adapter [00000003] Intel(R) PRO/1000 MT Network Connection has invalid DNS server:
(192.168.SERVER1.ipaddr ) (<name unavailable>)

        TEST: Forwarders/Root hints (Forw)
           Error: Root hints list has invalid root hint server: l.root-servers.net. (198.32.64.12)

      TEST: Delegations (Del)
         Error: DNS server: SERVER3.DOMAIN.NAME. IP:192.168.SERVER3.IPADDR [Broken delegated domain SERVER3.ic.internal.]

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

            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.127.in-addr.arpa. failed on the
                 DNS server 198.32.64.12

            DNS server: 192.168.IP.ADDR (<name unavailable>)
               1 test failure on this DNS server
               This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the
               DNS server 192.168.IP.ADDR
               Name resolution is not functional. _ldap._tcp.DOMAIN.NAME. failed on the DNS server
                 192.168.ip.addr<---address here is not in our domain

            DNS server: 192.168.SERVER3.IPADDR (SERVER3.DOMAIN.NAME.)
               1 test failure on this DNS server
               This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the
                 DNS server 192.168.SERVER3.IPADDR
               Delegation is broken for the domain SERVER3.DOMAIN.NAME. on the DNS server          
                 192.168.SERVER3.IPADDR

         Summary of DNS test results:
                                            Auth Basc Forw Del  Dyn  RReg Ext
               ________________________________________________________________
            Domain: ic.internal
               SERVER2                    PASS WARN PASS FAIL PASS PASS n/a

         ......................... ic.internal failed test DNS

________________________

Can anyone tell me what is going on and what I should do next?

Thanks for any help at all on this.
0
Comment
Question by:maureen99
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 24

Accepted Solution

by:
purplepomegranite earned 400 total points
ID: 21851526
          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.127.in-addr.arpa. failed on the
                 DNS server 198.32.64.12


Your server is set to use an internet root server as it's DNS server?  This is not correct.

How many servers do you have?  Which ones run DNS?

All you internal machines should point to internal DNS servers - there should be no external DNS servers at all.  Only the domain DNS servers should forward DNS requests to external DNS servers (either using root hints or forwarders).  Everything else (including other servers if they don't run DNS themselves) points to an internal DNS server.  If you only have one DNS server, make sure you don't have any secondary DNS servers set in any internal IP configurations.
0
 

Author Closing Comment

by:maureen99
ID: 31469981
Thanks for your help.  I am accepting this because it is a step in our overall problem.  Moreover, I did not present the full scope of our problem due to my lack of understanding and will do so in the future if need be.   The A rating is due to a helpful answer to an unclear, confused question.

thanks again,

Maureen
0

Featured Post

On Demand Webinar: Networking for the Cloud Era

Did you know SD-WANs can improve network connectivity? Check out this webinar to learn how an SD-WAN simplified, one-click tool can help you migrate and manage data in the cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Have you considered what group policies are backwards and forwards compatible? Windows Active Directory servers and clients use group policy templates to deploy sets of policies within your domain. But, there is a catch to deploying policies. The…
One of the most often confused topics in the area DNS is the idea of GLUE records. Specifically, what they are, when they are needed, when they are provided, and how they are created. First, WHAT IS GLUE? To understand GLUE, you must first under…
There's a multitude of different network monitoring solutions out there, and you're probably wondering what makes NetCrunch so special. It's completely agentless, but does let you create an agent, if you desire. It offers powerful scalability …
Monitoring a network: how to monitor network services and why? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the philosophy behind service monitoring and why a handshake validation is critical in network monitoring. Software utilized …

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question