[Pdns-users] TCP Queries always go to the recursor?

[Augie Schwer]

Is there a reason why TCP queries are always getting sent to the
recursor (if available) for answers instead of checking for an
authoritative answer first and then recursing if no authoritative
answer was found?

I am able to reproduce this by setting up a bogus zone in our
authoritative data (MySQL) and watching as I get the correct answer
for UDP recurse and norecurse queries as well as TCP norecurse
queries, however I see root referrals for TCP recurse queries. An even
easier way to see this is to ask for the version.bind :

[augie at augnix ~]$ dig +short ch txt version.bind @pdns-lab +notcp +norecurse
"Served by POWERDNS 2.9.21-svn.20061029.908 $Id: packethandler.cc 884
2006-08-19 12:32:32Z ahu $"

[augie at augnix ~]$ dig +short ch txt version.bind @pdns-lab +notcp +recurse
"Served by POWERDNS 2.9.21-svn.20061029.908 $Id: packethandler.cc 884
2006-08-19 12:32:32Z ahu $"

[augie at augnix ~]$ dig +short ch txt version.bind @pdns-lab +tcp +norecurse
"Served by POWERDNS 2.9.21-svn.20061029.908 $Id: packethandler.cc 884
2006-08-19 12:32:32Z ahu $"

[augie at augnix ~]$ dig +short ch txt version.bind @pdns-lab +tcp +recurse
"PowerDNS Recursor 3.1.4-pre2 $Id: pdns_recursor.cc 903 2006-10-21
16:26:49Z ahu $"

I am going to go check the RFC, but does anyone know why this would be
the case? This is with both PowerDNS recursor and BIND as a recursor.


-- 
Augie Schwer    -    Augie at Schwer.us    -    http://schwer.us
Key fingerprint = 9815 AE19 AFD1 1FE7 5DEE 2AC3 CB99 2784 27B0 C072