jhed9
jhed9
I also noticed that the --fallback option does not seem to work. I have a single upstream server configured and a single fallback configured. But when the upstream goes out,...
I’ll add that I have both my upstream and fallback dns names in my operating system’s hosts file, so I shouldn’t need a bootstrap option.
I upgraded to 970056be2de5eb2b3a20563c4b459b382da58516 from two hours ago, but this issue persists.
@sao321 NXDOMAIN is a valid response. In summary, it means that a DNS server claiming to be in charge of the domain (authoritative) responded, and the response was that the...
@abcbarryn What about it? I'm having the same issue as you. That's why I'm here.
@abcbarryn I noticed today that the failover logic appears to be working better now. After 5 seconds it will fail over to the fallback server, query it, cache cache the...
Hello @Maple38, I set up a nextdns.io profile for myself, but I was not able to reproduce the issue. Lookups worked as expected. The NextDNS console showed the performed lookups,...
No problem @Maple38. You have a great day as well.
I can't reproduce the issue, it's working for me @earache. I'm running the latest version from the master branch as of writing, f00be4dcb6106c8f753a8b45f054bb4ebc774958. My config is as follows, `edns-addr` changed...
Also, I'm curious, what app did you use the get the output in your third example? I'd like to use it. I like the crypto details in the header line.