On 2022-08-07 08:50, Linkcheck wrote:
On 07/08/2022 1:12 pm, Rob McGee wrote:
dig 2.0.0.127.zen.spamhaus.org. any
ANY has to be after DIG, not at the end, but...
Thank you for the correction. But as you have probably discovered
by now, my syntax was correct. In fact refer to the SIMPLE USAGE
section of "man dig"; my syntax was exactly as documented.
================
; <<>> DiG 9.10.3-P4-Ubuntu <<>> any 2.0.0.127.zen.spamhaus.org.
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18750
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;2.0.0.127.zen.spamhaus.org. IN ANY
;; ANSWER SECTION:
2.0.0.127.zen.spamhaus.org. 3579 IN A 127.255.255.254
This means you queried through a blocked resolver, as others have
mentioned.
;; Query time: 1 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sun Aug 07 14:34:59 BST 2022
;; MSG SIZE rcvd: 71
================
And I use a local copy of Unbound for all DNS work.
This means that your local resolver is(was) using forwarders. The
forwarder is blocked, not you. Simply remove the forwarders from
your configuration and all should be well.
With your nameserver configuration fixed (as it seems to be from
another post in this thread), you might want to reconsider your
decision about not using Zen.
I recommend (in *addition* to the POSTSCREEN_README) this short
guide:
http://rob0.nodns4.us/postscreen.html
--
http://rob0.nodns4.us/
