<div dir="ltr">All,<div><br></div><div>I'm in an odd situation. I have an authoritative DNS server that is supposed to forward any unknowns to a specific upstream server. These requests seem to process just fine till the response packet gets back to the system. Here is the resolver.log output specifics omitted.</div>
<div><br></div><div><br></div><div>************************************************************************************************</div><div><div>16-Jun-2014 09:53:54.002 fctx 0x7f92322d5010(QUERIED-HOSTNAME/NAPTR'): cancelquery</div>
<div>16-Jun-2014 09:53:54.002 fctx 0x7f92322d5010(QUERIED-HOSTNAME/NAPTR'): add_bad</div><div>16-Jun-2014 09:53:54.002 fctx 0x7f92322d5010(QUERIED-HOSTNAME/NAPTR'): try</div><div>16-Jun-2014 09:53:54.002 fctx 0x7f92322d5010(QUERIED-HOSTNAME/NAPTR'): cancelqueries</div>
<div>16-Jun-2014 09:53:54.002 fctx 0x7f92322d5010(QUERIED-HOSTNAME/NAPTR'): getaddresses</div><div>16-Jun-2014 09:53:54.002 fctx 0x7f92322d5010(QUERIED-HOSTNAME/NAPTR'): no addresses</div><div>16-Jun-2014 09:53:54.002 fctx 0x7f92322d5010(QUERIED-HOSTNAME/NAPTR'): done</div>
<div>16-Jun-2014 09:53:54.002 fctx 0x7f92322d5010(QUERIED-HOSTNAME/NAPTR'): stopeverything</div><div>16-Jun-2014 09:53:54.002 fctx 0x7f92322d5010(QUERIED-HOSTNAME/NAPTR'): cancelqueries</div><div>16-Jun-2014 09:53:54.002 fctx 0x7f92322d5010(QUERIED-HOSTNAME/NAPTR'): sendevents</div>
<div>16-Jun-2014 09:53:54.003 fetch 0x7f92383471b0 (fctx 0x7f92322d5010(QUERIED-HOSTNAME/NAPTR)): destroyfetch</div><div>16-Jun-2014 09:53:54.003 fctx 0x7f92322d5010(QUERIED-HOSTNAME/NAPTR'): shutdown</div><div>16-Jun-2014 09:53:54.003 fctx 0x7f92322d5010(QUERIED-HOSTNAME/NAPTR'): doshutdown</div>
<div>16-Jun-2014 09:53:54.003 fctx 0x7f92322d5010(QUERIED-HOSTNAME/NAPTR'): stopeverything</div><div>16-Jun-2014 09:53:54.003 fctx 0x7f92322d5010(QUERIED-HOSTNAME/NAPTR'): cancelqueries</div><div>16-Jun-2014 09:53:54.003 fctx 0x7f92322d5010(QUERIED-HOSTNAME/NAPTR'): unlink</div>
<div>16-Jun-2014 09:53:54.003 fctx 0x7f92322d5010(QUERIED-HOSTNAME/NAPTR'): destroy</div><div>16-Jun-2014 09:53:59.611 createfetch: QUERIED-HOSTNAME NAPTR</div><div>16-Jun-2014 09:53:59.611 fctx 0x7f92321d1010(QUERIED-HOSTNAME/NAPTR'): create</div>
<div>16-Jun-2014 09:53:59.611 log_ns_ttl: fctx 0x7f92321d1010: fctx_create: QUERIED-HOSTNAME (in 'HOSTNAME'?): 1 85178</div><div>16-Jun-2014 09:53:59.611 fctx 0x7f92321d1010(QUERIED-HOSTNAME/NAPTR'): join</div>
<div>16-Jun-2014 09:53:59.611 fetch 0x7f92383471b0 (fctx 0x7f92321d1010(QUERIED-HOSTNAME/NAPTR)): created</div><div>16-Jun-2014 09:53:59.611 fctx 0x7f92321d1010(QUERIED-HOSTNAME/NAPTR'): start</div><div>16-Jun-2014 09:53:59.611 fctx 0x7f92321d1010(QUERIED-HOSTNAME/NAPTR'): try</div>
<div>16-Jun-2014 09:53:59.611 fctx 0x7f92321d1010(QUERIED-HOSTNAME/NAPTR'): cancelqueries</div><div>16-Jun-2014 09:53:59.611 fctx 0x7f92321d1010(QUERIED-HOSTNAME/NAPTR'): getaddresses</div><div>16-Jun-2014 09:53:59.611 fctx 0x7f92321d1010(QUERIED-HOSTNAME/NAPTR'): query</div>
<div>16-Jun-2014 09:53:59.611 resquery 0x7f92321d8010 (fctx 0x7f92321d1010(QUERIED-HOSTNAME/NAPTR)): send</div><div>16-Jun-2014 09:53:59.612 resquery 0x7f92321d8010 (fctx 0x7f92321d1010(QUERIED-HOSTNAME/NAPTR)): sent</div>
<div>16-Jun-2014 09:53:59.612 resquery 0x7f92321d8010 (fctx 0x7f92321d1010(QUERIED-HOSTNAME/NAPTR)): udpconnected</div><div>16-Jun-2014 09:53:59.612 resquery 0x7f92321d8010 (fctx 0x7f92321d1010(QUERIED-HOSTNAME/NAPTR)): senddone</div>
<div>16-Jun-2014 09:53:59.683 resquery 0x7f92321d8010 (fctx 0x7f92321d1010(QUERIED-HOSTNAME/NAPTR)): response</div><div>16-Jun-2014 09:53:59.683 received packet:</div><div>;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45393</div>
<div>;; flags: qr rd; QUESTION: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 3</div><div>;; OPT PSEUDOSECTION:</div><div>; EDNS: version: 0, flags: do; udp: 4096</div><div>;; QUESTION SECTION:</div><div>;QUERIED-HOSTNAME. IN NAPTR</div>
<div><br></div><div>;; AUTHORITY SECTION:</div><div>CORRECT-UPSTREAMREAPONSE 86400 IN NS CORRECT-UPSTREAMREAPONSE</div><div>CORRECT-UPSTREAMREAPONSE 86400 IN NS CORRECT-UPSTREAMREAPONSE</div><div><br></div><div>
;; ADDITIONAL SECTION:</div><div>CORRECT-UPSTREAMREAPONSE 86400 IN A CORRECT-Resolved-IP</div><div>CORRECT-UPSTREAMREAPONSE 86400 IN A CORRECT-Resolved-IP</div><div><br></div><div><br></div><div>16-Jun-2014 09:53:59.683 fctx 0x7f92321d1010(QUERIED-HOSTNAME/NAPTR'): noanswer_response</div>
<div>16-Jun-2014 09:53:59.683 log_ns_ttl: fctx 0x7f92321d1010: noanswer_response: QUERIED-HOSTNAME (in 'HOSTNAME'?): 1 85178</div><div>16-Jun-2014 09:53:59.683 fctx 0x7f92321d1010: trimming ttl of HOSTNAME/NS for QUERIED-HOSTNAME/NAPTR: 86400 -> 85178</div>
<div>16-Jun-2014 09:53:59.683 DNS format error from 65.119.117.13#53 resolving QUERIED-HOSTNAME/NAPTR for client 66.171.30.193#15000: non-improving referral</div><div>16-Jun-2014 09:53:59.683 fctx 0x7f92321d1010(QUERIED-HOSTNAME/NAPTR'): cancelquery</div>
<div>16-Jun-2014 09:53:59.683 fctx 0x7f92321d1010(QUERIED-HOSTNAME/NAPTR'): add_bad</div><div>16-Jun-2014 09:53:59.683 fctx 0x7f92321d1010(QUERIED-HOSTNAME/NAPTR'): try</div><div>16-Jun-2014 09:53:59.683 fctx 0x7f92321d1010(QUERIED-HOSTNAME/NAPTR'): query</div>
</div><div><br></div><div>The big thing to NOTE is we're recieving the UPSTREAM packet back with the correct information! But alas our system says there is a formatting error. Does anyone have a quick response to this odd issue?</div>
<div><br></div><div>Thank you,</div><div><br></div><div><br clear="all"><div><div dir="ltr"><b><font color="#660000">Levi Pederson</font></b><div><font color="#660000">Mankato Networks LLC</font></div><div><font color="#660000">cell | 612.481.0769</font></div>
<div><font color="#660000">work | 612.787.7392</font></div><div><a href="mailto:levipederson@mankatonetworks.net" target="_blank">levipederson@mankatonetworks.net</a></div><div><img src="http://www.mankatonetworks.com/files/mnSignatureLogo.png" width="200" height="22"><br>
</div><div><br></div></div></div>
</div></div>