extra benefit of not breaking on servers that don't properly handle
unknown EDNS options.
Regards,
-- Ralph
On 02-01-18 21:14, Dan McCombs via Unbound-users wrote:
Hello,
I've come across an authoritative that responds with BADVERS when edns
client subnet is sent in a query to it, for examp
Hello,
I've come across an authoritative that responds with BADVERS when edns
client subnet is sent in a query to it, for example it can only be
queried with dig if edns is turned off and no subnet is set:
fails:
dig www.tsp.gov @ns2.tsp.gov
; <<>> DiG 9.11.2 <<>> www.tsp.gov @ns2.tsp.gov
;; gl
Excellent! I had no idea that had been merged. Thanks!
-Dan
[image: Dyn logo, Dyn.com] <http://dyn.com/>
*Dan McCombs * | Principal Software Engineer
p: 603.296.1568 | @danmccombs
On Fri, May 5, 2017 at 1:29 PM, Eduardo Schoedler
wrote:
> 2017-05-05 11:29 GMT-03:00 Dan McCombs vi
Hello,
Any chance of the edns-subnet branch having recent changes in trunk merged
into it?
I'd like to start testing that branch soon handling production traffic, but
would like the change in trunk that disables older TLS versions for
remote-control if built with a newer openssl, and just syncing
