Announcement

Collapse
No announcement yet.

Wierd DNS problems

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Wierd DNS problems

    Some sites will resolve and others won't... ie, I can almost always go to google.com but yahoo.com sometimes won't work... same with other sites... some work almost always and some almost never... I have deleted and re-installed the DNS role... see attached .txt files of dcdiag / fix info for errors...

    I am a neeeewb so please be easy on me... thanks!
    Attached Files

  • #2
    Re: Wierd DNS problems

    Have you got forwarders or conditional forwarders setup that may be causing the issue?

    Comment


    • #3
      Re: Wierd DNS problems

      I don't think so... Nothing in the conditional forwarders area under DNS and nothing in reverse lookup zone, in my forward lookup zone it has my domain listed...Hope this helps you help me out...sorry I can't be a bit more specific.

      Comment


      • #4
        Re: Wierd DNS problems

        Hi,

        Can you post a ipconfig /all of your DNS server also try clearing the DNS cache on the server (dnscmd /clearcache)
        Caesar's cipher - 3

        ZKHQ BRX HYHQWXDOOB GHFLSKHU WKLV BRX ZLOO UHDOLVH LW ZDV D ZDVWH RI WLPH!

        SFX JNRS FC U6 MNGR

        Comment


        • #5
          Re: Wierd DNS problems

          Here is ipconfig:

          Windows IP Configuration
          Host Name . . . . . . . . . . . . : LPServer
          Primary Dns Suffix . . . . . . . : lonepeak.local
          Node Type . . . . . . . . . . . . : Hybrid
          IP Routing Enabled. . . . . . . . : No
          WINS Proxy Enabled. . . . . . . . : No
          DNS Suffix Search List. . . . . . : lonepeak.local
          Ethernet adapter Local Area Connection:
          Connection-specific DNS Suffix . :
          Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
          Physical Address. . . . . . . . . : 00-23-7D-D6-8B-31
          DHCP Enabled. . . . . . . . . . . : No
          Autoconfiguration Enabled . . . . : Yes
          IPv4 Address. . . . . . . . . . . : 192.168.0.5(Preferred)
          Subnet Mask . . . . . . . . . . . : 255.255.255.0
          Default Gateway . . . . . . . . . : 192.168.0.1
          DNS Servers . . . . . . . . . . . : 127.0.0.1
          NetBIOS over Tcpip. . . . . . . . : Enabled
          Tunnel adapter Local Area Connection* 8:
          Media State . . . . . . . . . . . : Media disconnected
          Connection-specific DNS Suffix . :
          Description . . . . . . . . . . . : isatap.{F8CC7D14-DAB9-402A-94C9-CAAA7794A1A1}
          Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
          DHCP Enabled. . . . . . . . . . . : No
          Autoconfiguration Enabled . . . . : Yes

          Comment


          • #6
            Re: Wierd DNS problems

            Here is dcdiag (after dnscmd /clearcache)


            Directory Server Diagnosis

            Performing initial setup:
            Trying to find home server...
            Home Server = LPServer
            * Identified AD Forest.
            Done gathering initial info.

            Doing initial required tests

            Testing server: Default-First-Site-Name\LPSERVER
            Starting test: Connectivity
            ......................... LPSERVER passed test Connectivity

            Doing primary tests

            Testing server: Default-First-Site-Name\LPSERVER

            Starting test: DNS

            DNS Tests are running and not hung. Please wait a few minutes...
            ERROR: NO DNS servers for IPV6 stack was found
            ......................... LPSERVER 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 : lonepeak

            Running enterprise tests on : lonepeak.local
            Starting test: DNS
            Test results for domain controllers:

            DC: LPServer.lonepeak.local
            Domain: lonepeak.local


            TEST: Basic (Basc)
            Warning: The AAAA record for this DC was not found

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

            TEST: Records registration (RReg)
            Network Adapter
            [00000006] Broadcom NetXtreme Gigabit Ethernet:
            Warning:
            Missing AAAA record at DNS server 192.168.0.5:
            LPServer.lonepeak.local

            Warning:
            Missing AAAA record at DNS server 192.168.0.5:
            gc._msdcs.lonepeak.local

            Warning: Record Registrations not found in some network adapters

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

            DNS server: 192.203.230.10 (e.root-servers.net.)
            1 test failure on this DNS server
            PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.203.230.10
            Summary of DNS test results:

            Auth Basc Forw Del Dyn RReg Ext
            __________________________________________________ _______________
            Domain: lonepeak.local
            LPServer PASS WARN FAIL PASS PASS WARN n/a

            ......................... lonepeak.local failed test DNS

            Comment


            • #7
              Re: Wierd DNS problems

              Originally posted by chakotay2 View Post
              IPv4 Address. . . . . . . . . . . : 192.168.0.5(Preferred)
              Subnet Mask . . . . . . . . . . . : 255.255.255.0
              Default Gateway . . . . . . . . . : 192.168.0.1
              DNS Servers . . . . . . . . . . . : 127.0.0.1
              Change the DNS server in there to point to itself (192.168.0.5) rather than the loopback address 127.0.0.1.
              Caesar's cipher - 3

              ZKHQ BRX HYHQWXDOOB GHFLSKHU WKLV BRX ZLOO UHDOLVH LW ZDV D ZDVWH RI WLPH!

              SFX JNRS FC U6 MNGR

              Comment


              • #8
                Re: Wierd DNS problems

                Ok, I changed that and cleared dns cache.... here is new result:

                Directory Server Diagnosis

                Performing initial setup:
                Trying to find home server...
                Home Server = LPServer
                * Identified AD Forest.
                Done gathering initial info.

                Doing initial required tests

                Testing server: Default-First-Site-Name\LPSERVER
                Starting test: Connectivity
                ......................... LPSERVER passed test Connectivity

                Doing primary tests

                Testing server: Default-First-Site-Name\LPSERVER

                Starting test: DNS

                DNS Tests are running and not hung. Please wait a few minutes...
                ERROR: NO DNS servers for IPV6 stack was found
                ......................... LPSERVER 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 : lonepeak

                Running enterprise tests on : lonepeak.local
                Starting test: DNS
                Test results for domain controllers:

                DC: LPServer.lonepeak.local
                Domain: lonepeak.local


                TEST: Basic (Basc)
                Warning: The AAAA record for this DC was not found

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

                TEST: Records registration (RReg)
                Network Adapter
                [00000006] Broadcom NetXtreme Gigabit Ethernet:
                Warning:
                Missing AAAA record at DNS server 192.168.0.5:
                LPServer.lonepeak.local

                Warning:
                Missing AAAA record at DNS server 192.168.0.5:
                gc._msdcs.lonepeak.local

                Warning: Record Registrations not found in some network adapters

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

                DNS server: 192.203.230.10 (e.root-servers.net.)
                1 test failure on this DNS server
                PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.203.230.10
                Summary of DNS test results:

                Auth Basc Forw Del Dyn RReg Ext
                __________________________________________________ _______________
                Domain: lonepeak.local
                LPServer PASS WARN FAIL PASS PASS WARN n/a

                ......................... lonepeak.local failed test DNS

                Comment


                • #9
                  Re: Wierd DNS problems

                  Any events logged in there? and have you tried using a Forwarder instead of the Root hints?
                  Caesar's cipher - 3

                  ZKHQ BRX HYHQWXDOOB GHFLSKHU WKLV BRX ZLOO UHDOLVH LW ZDV D ZDVWH RI WLPH!

                  SFX JNRS FC U6 MNGR

                  Comment


                  • #10
                    Re: Wierd DNS problems

                    Originally posted by L4ndy View Post
                    Any events logged in there? and have you tried using a Forwarder instead of the Root hints?
                    Sorry, I am not sure what you mean by using forwarder instead of root hints.

                    Comment


                    • #11
                      Re: Wierd DNS problems

                      Originally posted by chakotay2 View Post
                      Sorry, I am not sure what you mean by using forwarder instead of root hints.
                      If no forwarders or conditional forwarders exist, root hints are used. You could look into setting a forwarder to an external DNS server at your ISP or open source one.
                      Last edited by Virtual; 27th April 2009, 19:17. Reason: spelling

                      Comment


                      • #12
                        Re: Wierd DNS problems

                        sorry, you are still a bit over my head... can you explain that in a different way or provide a procedure to do so?

                        Allen

                        Comment


                        • #13
                          Re: Wierd DNS problems

                          This should help.

                          http://www.windowsnetworking.com/art...rver_2003.html

                          Covers forwarders as well in the article. This is also relevant to windows 2008 DNS with regards to forwarders.

                          Comment


                          • #14
                            Re: Wierd DNS problems

                            Looks much better... still getting AAAA error but that is to be expected as ipv6 is disabled. But the roothints error is gone.... Things seem to be resovling now... Thanks for all your help folks!


                            Directory Server Diagnosis


                            Performing initial setup:

                            Trying to find home server...

                            Home Server = LPServer

                            * Identified AD Forest.
                            Done gathering initial info.


                            Doing initial required tests


                            Testing server: Default-First-Site-Name\LPSERVER

                            Starting test: Connectivity

                            ......................... LPSERVER passed test Connectivity



                            Doing primary tests


                            Testing server: Default-First-Site-Name\LPSERVER


                            Starting test: DNS



                            DNS Tests are running and not hung. Please wait a few minutes...

                            ERROR: NO DNS servers for IPV6 stack was found
                            ......................... LPSERVER 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 : lonepeak


                            Running enterprise tests on : lonepeak.local

                            Starting test: DNS

                            Test results for domain controllers:


                            DC: LPServer.lonepeak.local

                            Domain: lonepeak.local




                            TEST: Basic (Basc)
                            Warning: The AAAA record for this DC was not found

                            TEST: Records registration (RReg)
                            Network Adapter

                            [00000006] Broadcom NetXtreme Gigabit Ethernet:

                            Warning:
                            Missing AAAA record at DNS server 192.168.0.5:
                            LPServer.lonepeak.local

                            Warning:
                            Missing AAAA record at DNS server 192.168.0.5:
                            gc._msdcs.lonepeak.local

                            Warning: Record Registrations not found in some network adapters


                            LPServer PASS WARN PASS PASS PASS WARN n/a
                            ......................... lonepeak.local passed test DNS
                            Last edited by chakotay2; 28th April 2009, 09:17.

                            Comment


                            • #15
                              Re: Wierd DNS problems

                              So what did you do to fix the issue? Was it changing the Preferred DNS from 127.0.0.1 to the actual IP that fixed it?
                              |
                              +-- JDMils
                              |
                              +-- Regional Systems Engineer, DotNet programmer & Jack of all trades
                              |

                              Comment

                              Working...
                              X