DNS Server Problems - Windows Server 2012 - SERVFAIL & Response packet does not match any outstanding query

Hi,

i am having problems with my DNS servers.

i have 2 * Win Server 2012 DC/DNS (192.168.16.0 / fc00:1234:5678:9abc::) onsite and 1 * Win Server 2012 DC/DNS on Azure (10.4.2.0)

i get the following errors in the onsite DNS Serevr longs (i get no errors with the DNS server on Azure):




05/10/2013 22:01:42 0728 PACKET  000000746750FE80 UDP Snd 192.168.16.11   5dbb R Q [8281   DR SERVFAIL] NS     (0)
UDP response info at 000000746750FE80
  Socket = 468
  Remote addr 192.168.16.11, port 57541
  Time Query=124277, Queued=124285, Expire=124288
  Buf length = 0x0200 (512)
  Msg length = 0x0011 (17)
  Message:
    XID       0x5dbb
    Flags     0x8182
      QR        1 (RESPONSE)
      OPCODE    0 (QUERY)
      AA        0
      TC        0
      RD        1
      RA        1
      Z         0
      CD        0
      AD        0
      RCODE     2 (SERVFAIL)
    QCOUNT    1
    ACOUNT    0
    NSCOUNT   0
    ARCOUNT   0
    QUESTION SECTION:
    Offset = 0x000c, RR count = 0
    Name      "(0)"
      QTYPE   NS (2)
      QCLASS  1
    ANSWER SECTION:
      empty
    AUTHORITY SECTION:
      empty
    ADDITIONAL SECTION:
      empty





05/10/2013 21:51:53 098C PACKET  000000746780B8F0 UDP Rcv 192.168.16.11   8315 R Q [8385 A DR NXDOMAIN] NULL  

(32)FHFAEBEECACACACACACACACACACACAAA(0)
UDP response info at 000000746780B8F0
  Socket = 508
  Remote addr 192.168.16.11, port 137
  Time Query=123700, Queued=0, Expire=0
  Buf length = 0x0fa0 (4000)
  Msg length = 0x0038 (56)
  Message:
    XID       0x8315
    Flags     0x8583
      QR        1 (RESPONSE)
      OPCODE    0 (QUERY)
      AA        1
      TC        0
      RD        1
      RA        1
      Z         0
      CD        0
      AD        0
      RCODE     3 (NXDOMAIN)
    QCOUNT    0
    ACOUNT    0
    NSCOUNT   0
    ARCOUNT   0
    QUESTION SECTION:
      empty
    ANSWER SECTION:
      empty
    AUTHORITY SECTION:
      empty
    ADDITIONAL SECTION:
      empty
WARNING: message continues beyond these records
    pch = 000000746780C3E4, pCurrent = 0000000000000000, -1736492004 bytes
    offset = 12, msg length = 56, 44 bytes

05/10/2013 21:52:02 098C PACKET  Response packet 00000074669A9560 does not match any outstanding query













05/10/2013 21:41:45 0990 PACKET  00000074676C11C0 UDP Rcv 192.168.16.11   830f R Q [8385 A DR NXDOMAIN] NULL  

(32)FHFAEBEECACACACACACACACACACACAAA(0)
UDP response info at 00000074676C11C0
  Socket = 41408
  Remote addr 192.168.16.11, port 137
  Time Query=123091, Queued=0, Expire=0
  Buf length = 0x0fa0 (4000)
  Msg length = 0x0038 (56)
  Message:
    XID       0x830f
    Flags     0x8583
      QR        1 (RESPONSE)
      OPCODE    0 (QUERY)
      AA        1
      TC        0
      RD        1
      RA        1
      Z         0
      CD        0
      AD        0
      RCODE     3 (NXDOMAIN)
    QCOUNT    0
    ACOUNT    0
    NSCOUNT   0
    ARCOUNT   0
    QUESTION SECTION:
      empty
    ANSWER SECTION:
      empty
    AUTHORITY SECTION:
      empty
    ADDITIONAL SECTION:
      empty
WARNING: message continues beyond these records
    pch = 00000074676C1CB4, pCurrent = 0000000000000000, -1735138484 bytes
    offset = 12, msg length = 56, 44 bytes

05/10/2013 21:41:53 0990 PACKET  Response packet 0000007465D7A750 does not match any outstanding query
05/10/2013 21:42:53

0990 PACKET  Response packet 0000007466BE02C0 does not match any outstanding query
05/10/2013 21:44:41 990 Note: got GQCS

failure on a dead socket context status=995, socket=460, pcon=0000007465231E60, state=-1, IP=fc00:1234:5678:9abc::11
05/10/2013 21:44:41 990 Note: got GQCS failure on a dead socket context status=995, socket=41408, pcon=0000007465234860,

state=-1, IP=0.0.0.0
05/10/2013 21:44:41 990 Note: got GQCS failure on a dead socket context status=995, socket=41408,

pcon=0000007465234860, state=-1, IP=0.0.0.0
05/10/2013 21:44:41 990 Note: got GQCS failure on a dead socket context

status=995, socket=456, pcon=0000007465234960, state=-1, IP=::
05/10/2013 21:44:41 990 Note: got GQCS failure on a dead

socket context status=995, socket=456, pcon=0000007465234960, state=-1, IP=::
05/10/2013 21:44:41 98C Note: got GQCS

failure on a dead socket context status=995, socket=460, pcon=0000007465231E60, state=-1, IP=fc00:1234:5678:9abc::11
05/10/2013 21:44:42 098C PACKET  0000007465BCB120 UDP Rcv 192.168.16.11   16e6   Q [0001   D   NOERROR] NS    

(13)DomainName(5)local(0)
UDP question info at 0000007465BCB120
  Socket = 468
  Remote addr 192.168.16.11, port 57153
  Time Query=123268, Queued=0, Expire=0
  Buf length = 0x0fa0 (4000)
  Msg length = 0x0025 (37)
  Message:
    XID       0x16e6
    Flags     0x0100
      QR        0 (QUESTION)
      OPCODE    0 (QUERY)
      AA        0
      TC        0
      RD        1
      RA        0
      Z         0
      CD        0
      AD        0
      RCODE     0 (NOERROR)
    QCOUNT    1
    ACOUNT    0
    NSCOUNT   0
    ARCOUNT   0
    QUESTION SECTION:
    Offset = 0x000c, RR count = 0
    Name      "(13)DomainName(5)local(0)"
      QTYPE   NS (2)
      QCLASS  1
    ANSWER SECTION:
      empty
    AUTHORITY SECTION:
      empty
    ADDITIONAL SECTION:
      empty
LVL 1
jackbensonAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

skullnobrainsCommented:
most likely these answer just took too long to reach your server and it had closed the socket assuming the remote server did not answer beforehand. this is pretty usual on loaded dns servers.

do you actually experience some problems ?
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jackbensonAuthor Commented:
turned out to be a problem with my Draytek router.

when I applied new firmware it went away
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
DNS

From novice to tech pro — start learning today.