Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Monday, November 24, 2014 10:00 AM
Dears,
hope that somebody of you may help me in this issue; unfortunately I don't find further information.
After setting up an external DNS service with different Microsoft Windows Server 2012R2 the DNS log is full of this strange messages. DNS service is (still) working, but this message is driving me crazy as I don't see any configuration error nor do I find any other information about this. Every help is greatly appriciated!DNS Server log file creation at 20.11.2014 18:20:59
Message logging key (for packets - other items use a subset of these fields):
Field # Information Values
1 Date
2 Time
3 Thread ID
4 Context
5 Internal packet identifier
6 UDP/TCP indicator
7 Send/Receive indicator
8 Remote IP
9 Xid (hex)
10 Query/Response R = Response
blank = Query
11 Opcode Q = Standard Query
N = Notify
U = Update
? = Unknown
12 [ Flags (hex)
13 Flags (char codes) A = Authoritative Answer
T = Truncated Response
D = Recursion Desired
R = Recursion Available
14 ResponseCode ]
15 Question Type
16 Question Name
20.11.2014 18:22:06 AB0 Note: got GQCS failure on a dead socket context status=995, socket=516, pcon=000000D07FAB7090, state=-1, IP=0.0.0.0
20.11.2014 18:22:06 170 Note: got GQCS failure on a dead socket context status=995, socket=516, pcon=000000D07FAB7090, state=-1, IP=0.0.0.0
20.11.2014 18:22:06 AB0 Note: got GQCS failure on a dead socket context status=995, socket=524, pcon=000000D07FAB7190, state=-1, IP=::
20.11.2014 18:22:06 170 Note: got GQCS failure on a dead socket context status=995, socket=524, pcon=000000D07FAB7190, state=-1, IP=::
20.11.2014 18:22:06 170 Note: got GQCS failure on a dead socket context status=995, socket=524, pcon=000000D00078B130, state=-1, IP=0.0.0.0
20.11.2014 18:22:06 170 Note: got GQCS failure on a dead socket context status=995, socket=21420, pcon=000000D000788930, state=-1, IP=::
20.11.2014 18:22:06 170 Note: got GQCS failure on a dead socket context status=995, socket=21420, pcon=000000D000788930, state=-1, IP=::
20.11.2014 18:22:06 AB0 Note: got GQCS failure on a dead socket context status=995, socket=524, pcon=000000D00078B130, state=-1, IP=0.0.0.0
20.11.2014 18:22:06 170 Note: got GQCS failure on a dead socket context status=995, socket=524, pcon=000000D00078B230, state=-1, IP=0.0.0.0
20.11.2014 18:22:06 170 Note: got GQCS failure on a dead socket context status=995, socket=21448, pcon=000000D00078B530, state=-1, IP=::
20.11.2014 18:22:06 170 Note: got GQCS failure on a dead socket context status=995, socket=21448, pcon=000000D00078B530, state=-1, IP=::
20.11.2014 18:22:06 AB0 Note: got GQCS failure on a dead socket context status=995, socket=524, pcon=000000D00078B230, state=-1, IP=0.0.0.0
20.11.2014 18:22:06 AB0 Note: got GQCS failure on a dead socket context status=995, socket=21448, pcon=000000D00078BF30, state=-1, IP=0.0.0.0
20.11.2014 18:22:06 AB0 Note: got GQCS failure on a dead socket context status=995, socket=21464, pcon=000000D00078B930, state=-1, IP=::
20.11.2014 18:22:06 AB0 Note: got GQCS failure on a dead socket context status=995, socket=21464, pcon=000000D00078B930, state=-1, IP=::
20.11.2014 18:22:06 170 Note: got GQCS failure on a dead socket context status=995, socket=21448, pcon=000000D00078BF30, state=-1, IP=0.0.0.0
20.11.2014 18:22:06 AB0 Note: got GQCS failure on a dead socket context status=995, socket=21464, pcon=000000D00078BA30, state=-1, IP=0.0.0.0
20.11.2014 18:22:06 AB0 Note: got GQCS failure on a dead socket context status=995, socket=268, pcon=000000D00078BB30, state=-1, IP=::
20.11.2014 18:22:06 AB0 Note: got GQCS failure on a dead socket context status=995, socket=268, pcon=000000D00078BB30, state=-1, IP=::
20.11.2014 18:22:06 170 Note: got GQCS failure on a dead socket context status=995, socket=21464, pcon=000000D00078BA30, state=-1, IP=0.0.0.0
All replies (3)
Tuesday, November 25, 2014 7:49 AM
Hi,
According to your description, my understanding is that the DNS server debug log displays “got GQCS failure…” after add an external DNS service.
If convenient, I suggest you to restart the DNS server according the steps below:
1. Open DNS manager, right-click DNS server name and select Properties.
2. Select Debug logging tab, uncheck Log packets for debug logging.
3. Click Apply and OK to save the change.
4. Right-click DNS server name and select All Task.
5. Click Stop.
6. After the DNS server is stopped, then click Start to restart DNS server.
7. Check Log packets for debug logging on Debug logging tab of Properties.
In this case, the debug log will be overridden. Open CMD and use NSlookup, check to see if the DNS debug log displays the record correctly.
Besides, you may try to restart the device and check to see if it works.
If the problem still exits, it would be helpful if you can provide the “ipconfig /all” results of your DNS server. You have mentioned that “DNS service is (still) working”, does this mean that name resolution works correctly? Does the “setting up an external DNS service” mean add another DNS server, and configured it in the Forwarder tab of your DNS server’s Properties?
Best Regards,
Eve Wang
Tuesday, November 25, 2014 2:46 PM
Hi Eve,
thanks for your reply. Restarting the service (and restarting the different servers) didn't helped to resolve this issue: After few seconds the same messages came back. To clarify: Whith "external DNS" I refer to DNS that provides name resolution for external parties (from the internet).
We built up the following structure:
Server B
|
Server A
|
Server C
All servers are authoritative for the zones. Server A is the zone master for all configured zones, DNS is only accessible for internal devices. Server A responds for recursive queries. Server B and server C provide DNS for queries from the internet, they only answer for iterative queries. B and C got their zones from A. A hidden master concept is implemented, we're not using forwarders.
DNS for all servers is working, i.e. the service answers on queries as expected. My fear is that due to this unknown und unidentifiable error message we can't provide high availability and a trusted service. In my next post I provide the ipconfig /all.
Once again, every help that may identify the error soure is greatly appreciated!
Kind rergards
Joerg
Thursday, November 27, 2014 9:12 AM
Hi,
Check state and process about TCP and UDP port 53.
Open CMD, type “netstat –nao >>c:\port.txt” and hit Enter. “c:\port.txt” is a text file which used to export the result of “netstat –nao”. Open Task Manager, check to see which process is using port 53 according to the PID.
Best Regards,
Eve Wang