Forwarding a domain does not support fallback to TCP #704

Closed
Habbie opened this Issue Apr 26, 2013 · 7 comments

Projects

None yet

1 participant

@Habbie
Member
Habbie commented Apr 26, 2013

If we forward a domain and the remote nameserver returns a truncated answer, powerdns recursor 3.5rc2 does not retry over TCP/IP. Reported by Jan Piet Mens.

@Habbie Habbie was assigned Apr 26, 2013
@Habbie Habbie closed this Apr 26, 2013
@Habbie
Member
Habbie commented Apr 26, 2013

Author: peter
(this is with forward-zones-recurse=.=1.2.3.4)

@Habbie
Member
Habbie commented Apr 26, 2013

Author: peter
With --forward-zones-recurse=.=149.20.64.21, I have no trouble resolving 'txt ring.nlnog.net', and tcpdump shows TCP fallback:

10:57:16.950087 IP (tos 0x0, ttl 64, id 61989, offset 0, flags [DF], proto TCP (6), length 74)
    172.16.68.10.44322 > 149.20.64.21.53: Flags [P.], cksum 0xc580 (incorrect -> 0xf317), seq 1:35, ack 1, win 14600, length 3436800+ TXT? ring.nlnog.net. (32)
@Habbie
Member
Habbie commented Apr 26, 2013

Author: anon
Would you please try jpmens.net any ?

@Habbie
Member
Habbie commented Apr 26, 2013

Author: peter
Confirmed TWO bugs.

  1. without forwarding, jpmens.net ANY will sometimes send a response packet that dig chokeson
  2. with forwarding, ANY queries (to other, 'smaller' names too), tend to yield an empty NOERROR
@Habbie
Member
Habbie commented Apr 26, 2013

Author: peter
item 1 fixed in r3109. Item 2 remains.

@Habbie
Member
Habbie commented Apr 26, 2013

Author: peter
item 2 presumably fixed in r3116, please confirm!

@Habbie
Member
Habbie commented Apr 26, 2013

Author: peter
confirmed by jpmens, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment