"
I'm getting `status: REFUSED` DNS responses at times from Unbound according to dig lookups, with dig complaining about recursion not being available. Restarting Unbound "fixed" it at the moment but don't have confidence this will stay that way.
To be clear, not using DoT or an external resolver, I'm letting Unbound perform recursion itself. Also don't see anything obvious in the logs.
Code Select
% dig example.com
; <<>> DiG 9.10.6 <<>> example.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 55088
;; flags: qr rd ad; QUERY: 0, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available
;; Query time: 67 msec
;; SERVER: 2601:18d:xxxx:xxxx:xxx:xxxx:xxxx:xxxx#53(2601:18d:xxxx:xxxx:xxx:xxxx:xxxx:xxxx)
;; WHEN: Thu Jun 24 20:10:03 EDT 2021
;; MSG SIZE rcvd: 12To be clear, not using DoT or an external resolver, I'm letting Unbound perform recursion itself. Also don't see anything obvious in the logs.
