Announcement

Collapse
No announcement yet.

Possible DNS issue

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

  • Possible DNS issue

    Hi, here is the scenario. I currently run 3 servers. ServerA is running 2003 32bit and holds the the FSMO roles, DNS. ServerB is running 2003 32bit as a BDC running the CA & DNS. Server C is running server 2008 running DHCP and DNS. Server C was supposed to replace server B, However when server B crashed the entire network came to a complete holt. Any suggestions would be helpful.

    Thanks,

  • #2
    Re: Possible DNS issue

    Certificate Authority can be pretty important.

    when you say the network came to a halt, what happened? what errors did you see, what do the event logs say.
    Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

    Comment


    • #3
      Re: Possible DNS issue

      Network browsing was very slow. Printing stopped working even though server C hosted the printers. AD worked but very slowly.. internet access stopped. Server A crawled. The event logs showed NTFS errors: unable to replicate between servers, DNS errors: unable to locate AD connections. FSMO roles all show SERVER A as the HOST for all.
      Last edited by springboks07; 4th November 2010, 14:26.

      Comment


      • #4
        Re: Possible DNS issue

        Hi,

        can you post netdiag and dcdiag results.
        Thanks & Regards
        v-2nas

        MCTS 2008, MCTIP, MCSE 2003, MCSA+Messaging E2K3, MCP, E2K7
        Sr. Wintel Eng. (Investment Bank)
        Independent IT Consultant and Architect
        Blog: http://www.exchadtech.blogspot.com

        Show your appreciation for my help by giving reputation points

        Comment


        • #5
          Re: Possible DNS issue

          is each server pointing to itself for dns ?
          Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

          Comment


          • #6
            Re: Possible DNS issue

            are your clients pointing to b for dns???

            Comment


            • #7
              Re: Possible DNS issue

              i think wullieb could be on the nose here..

              check your DHCP scope configuration, and see what DNS server is configured for the clients
              Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

              Comment


              • #8
                Re: Possible DNS issue

                Directory Server Diagnosis

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

                Doing initial required tests

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

                Doing primary tests

                Testing server: Default-First-Site-Name\STU-SRV1

                Starting test: DNS

                DNS Tests are running and not hung. Please wait a few minutes...
                ......................... STU-SRV1 passed test DNS

                Running partition tests on : DomainDnsZones

                Running partition tests on : ForestDnsZones

                Running partition tests on : Schema

                Running partition tests on : Configuration

                Running partition tests on : ******

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

                DC: STU-SRV1.******.local
                Domain: ******.local


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

                TEST: Records registration (RReg)
                Network Adapter [00000010] BASP Virtual Adapter:
                Warning:
                Missing AAAA record at DNS server 192.168.2.254:
                STU-SRV1.******.local

                Warning:
                Missing AAAA record at DNS server 192.168.2.254:
                gc._msdcs.******.local

                Warning:
                Missing AAAA record at DNS server 192.168.1.251:
                STU-SRV1.******.local

                Warning:
                Missing AAAA record at DNS server 192.168.1.251:
                gc._msdcs.******.local

                Warning: Record Registrations not found in some network adapters

                STU-SRV1 PASS WARN PASS PASS PASS WARN n/a
                ......................... ******.local passed test DNS

                Comment


                • #9
                  Re: Possible DNS issue

                  All client wrkstns are pointing to server C. I have also listed the server A and Server C as the DNS entries in the DHCP service hand out. Each server points to it's self as DNS in the NIC config.

                  Comment


                  • #10
                    Re: Possible DNS issue

                    Is it running WINS on that server???

                    Exactly what roles does the server have??? Are your other 2 DC's GC's???

                    Comment


                    • #11
                      Re: Possible DNS issue

                      Errors are for IPv6 records -- try disabling that protocol and see if it corrects itself
                      Tom Jones
                      MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
                      PhD, MSc, FIAP, MIITT
                      IT Trainer / Consultant
                      Ossian Ltd
                      Scotland

                      ** Remember to give credit where credit is due and leave reputation points where appropriate **

                      Comment


                      • #12
                        Re: Possible DNS issue

                        I have disabled WINS, it causes too much traffic.
                        Server A is the DC, server B and C are both GCs. IPv6 is disabled.
                        I ran dcdiag /test:dns on Server A (DC).
                        Domain Controller Diagnosis

                        Performing initial setup:
                        Done gathering initial info.

                        Doing initial required tests

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

                        Doing primary tests

                        Testing server: Default-First-Site-Name\SQLSVR-PSL

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

                        Running partition tests on : ForestDnsZones

                        Running partition tests on : DomainDnsZones

                        Running partition tests on : Schema

                        Running partition tests on : Configuration

                        Running partition tests on : ****

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

                        DC: SQLSVR-PSL.****.local
                        Domain: ****.local


                        TEST: Forwarders/Root hints (Forw)
                        Error: Root hints list has invalid root hint server: a.root-servers.net. (198.41.0
                        .4)
                        Error: Root hints list has invalid root hint server: b.root-servers.net. (128.9.0.
                        107)
                        Error: Root hints list has invalid root hint server: b.root-servers.net. (192.228.
                        79.201)
                        Error: Root hints list has invalid root hint server: c.root-servers.net. (192.33.4
                        .12)
                        Error: Root hints list has invalid root hint server: d.root-servers.net. (128.8.10
                        .90)
                        Error: Root hints list has invalid root hint server: e.root-servers.net. (192.203.
                        230.10)
                        Error: Root hints list has invalid root hint server: f.root-servers.net. (192.5.5.
                        241)
                        Error: Root hints list has invalid root hint server: g.root-servers.net. (192.112.
                        36.4)
                        Error: Root hints list has invalid root hint server: h.root-servers.net. (128.63.2
                        .53)
                        Error: Root hints list has invalid root hint server: i.root-servers.net. (192.36.1
                        48.17)
                        Error: Root hints list has invalid root hint server: j.root-servers.net. (192.58.1
                        28.30)
                        Error: Root hints list has invalid root hint server: k.root-servers.net. (193.0.14
                        .129)
                        Error: Root hints list has invalid root hint server: l.root-servers.net. (198.32.6
                        4.12)
                        Error: Root hints list has invalid root hint server: m.root-servers.net. (202.12.2
                        7.33)

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

                        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.127.in-addr.arpa. fail
                        ed 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.127.in-addr.arpa. fail
                        ed on the DNS server 128.8.10.90

                        DNS server: 128.9.0.107 (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.127.in-addr.arpa. fail
                        ed on the DNS server 128.9.0.107

                        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.127.in-addr.arpa. fail
                        ed 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.127.in-addr.arpa. fail
                        ed 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.127.in-addr.arpa. fail
                        ed 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.127.in-addr.arpa. fail
                        ed 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.127.in-addr.arpa. fail
                        ed 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.127.in-addr.arpa. fail
                        ed 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.127.in-addr.arpa. fail
                        ed 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.127.in-addr.arpa. fail
                        ed on the DNS server 193.0.14.129

                        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. fail
                        ed on the DNS server 198.32.64.12

                        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.127.in-addr.arpa. fail
                        ed on the DNS server 198.41.0.4

                        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.127.in-addr.arpa. fail
                        ed on the DNS server 202.12.27.33

                        Summary of DNS test results:

                        Auth Basc Forw Del Dyn RReg Ext
                        __________________________________________________ ______________
                        Domain: ****.local
                        SQLSVR-PSL PASS PASS FAIL PASS PASS PASS n/a

                        ......................... ****.local failed test DNS

                        I failed to mention that these servers are spread across 2 sites using a metro ethernet. Sorry about the lack of info
                        Thanks,
                        Last edited by springboks07; 9th November 2010, 14:59. Reason: additional info

                        Comment


                        • #13
                          Re: Possible DNS issue

                          You look lke your not using forwarders but Root Hints. IMHO i'd get your ISP's DNS servers and add them to the forwaders list.

                          Please post an IPCONFIG /ALL from both your servers and a client that was having issues.

                          Comment


                          • #14
                            Re: Possible DNS issue

                            I have tried the dns forwarders. It seems to work for a day or 2 but it seems to cause internet browsing issues on the workstations. I might be forced to virtualize serverB to retain stability...The other possible problem is that our routers are configured and managed by the ISP/phone company. I never had this issue prior to them pulling out my Ciscos...

                            Comment


                            • #15
                              Re: Possible DNS issue

                              Can you post and ipconfig /all from both a client and server b please.

                              Comment

                              Working...
                              X