Re: DNS query question
On Wed, Jun 12, 2024 at 06:42:04AM +0200, Marco Moock wrote: > Am 12.06.2024 um 10:51:45 Uhr schrieb Jeff Peng: > > Hello list, > > > > I have made a successful query in one of my VPS as the following. > > > > ~$ dig 235.84.36.104.zen.spamhaus.org > > ;; QUESTION SECTION: > > ;235.84.36.104.zen.spamhaus.org.IN A > > > > ;; ANSWER SECTION: > > 235.84.36.104.zen.spamhaus.org. 852 IN A 127.0.0.10 > > > > ;; Query time: 0 msec > > ;; SERVER: 127.0.0.53#53(127.0.0.53) > > > > > > But, the same query wouldn't success in another VPS as follows. > > > > $ dig 235.84.36.104.zen.spamhaus.org > > ;; QUESTION SECTION: > > ;235.84.36.104.zen.spamhaus.org.IN A > > > > ;; Query time: 1 msec > > ;; SERVER: 127.0.0.53#53(127.0.0.53) > > > > > > The returned result is "NXDOMAIN". > > > > Both nodes use systemd-resolve as DNS subresolver. > > > > Do you know what's the reason behind this? > > Spamhaus restricts queries from public resolvers. > https://www.spamhaus.org/resource-hub/email-security/if-you-query-the-legacy-dnsbls-via-digitalocean-move-to-spamhaus-technologys-free-data-query-service/#the-headlines-for-those-in-a-hurry > > > > Thanks. Thanks for keeping context Thanks for noting that response text is below previous text. Yes, keep the discussion order. Regards Geert Stappers Aware of people in different time zones Creating awareness for that not all messages are read Asking for standalone messages -- Silence is hard to parse
Re: DNS query question
Am 12.06.2024 um 10:51:45 Uhr schrieb Jeff Peng: > Do you know what's the reason behind this? Spamhaus restricts queries from public resolvers. https://www.spamhaus.org/resource-hub/email-security/if-you-query-the-legacy-dnsbls-via-digitalocean-move-to-spamhaus-technologys-free-data-query-service/#the-headlines-for-those-in-a-hurry -- Gruß Marco Send unsolicited bulk mail to 1718182305mu...@cartoonies.org
DNS query question
Hello list, I have made a successful query in one of my VPS as the following. ~$ dig 235.84.36.104.zen.spamhaus.org ; <<>> DiG 9.16.48-Ubuntu <<>> 235.84.36.104.zen.spamhaus.org ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2160 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;235.84.36.104.zen.spamhaus.org.IN A ;; ANSWER SECTION: 235.84.36.104.zen.spamhaus.org. 852 IN A 127.0.0.10 ;; Query time: 0 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Wed Jun 12 02:45:16 UTC 2024 ;; MSG SIZE rcvd: 75 But, the same query wouldn't success in another VPS as follows. $ dig 235.84.36.104.zen.spamhaus.org ; <<>> DiG 9.16.1-Ubuntu <<>> 235.84.36.104.zen.spamhaus.org ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 15831 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;235.84.36.104.zen.spamhaus.org.IN A ;; Query time: 1 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Wed Jun 12 10:45:41 HKT 2024 ;; MSG SIZE rcvd: 59 The returned result is "NXDOMAIN". Both nodes use systemd-resolve as DNS subresolver. Do you know what's the reason behind this? Thanks.