Maintained by: NLnet Labs

[Unbound-users] again: capsforid let unbound fail to resolv a domain

A. Schulze
Fri Feb 27 14:11:48 CET 2015


after unbound 1.5.2 was announced I was happy to read:
- Fix 0x20 capsforid fallback to omit gratuitous NS and additional  
section changes.

Unfortunately that fix still make my unbound not resolve some  
problematic domains.

Current case:

dig ptr +noall +answer +nocomments

; <<>> DiG 9.9.4-P2 <<>>  
ptr +noall +answer +nocomments
; (1 server found)
;; global options: +cmd 3600 IN     PTR

-> notice the lowercase "" in the answer section

other domains I have workarounds for:

The last one is not related to capsforid. The Nameserver[]
serve the label with a ttl 0 seconds and don't  
answer at all.
At the end unbound to fail to resolve