resolver change between 9.20.16 and 9.20.17

[Andreas S. Kerber]

Hi,

just upgraded some resolver instances from 9.20.16 to 9.20.17 and I'm noticing issues resolving some domain names.

Using: 9.20.16
# dig -t ns teckbote.de | grep status:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9717

Using: 9.20.17
# dig -t ns teckbote.de | grep status:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 62960


This issue seems to be (once again) the result of a bad setup at a particular domain (they don't seem to have any glue records at all. DUH...).

I just wonder if there is a expected behaviour change between 9.20.16 and 9.20.17 and whether anybody else can resolve the name above using 9.20.17?

Important Note: resolving works fine when using "dig +trace" (I guess with +trace the glue for the NS is fetched as part of the trace operation and therefore does not expose this resolving problem)