Re: rep.mailspike.net
Bill Cole <[email protected]>
| Newsgroups | gmane.mail.spam.spamassassin.general |
|---|---|
| Message-ID | <[email protected]> |
On 2025-05-20 at 11:32:26 UTC-0400 (Tue, 20 May 2025 15:32:26 +0000) Rupert Gallagher <[email protected]> is rumored to have said: > Hello, > > Is rep.mailspike.net working for you? > > If I query 78.153.140.99 at https://mailspike.io/ip_verify I get > 127.0.0.11, however if I query using dig I get no answer at all, and > the name server itself does not exist. > >> dig +short -t A 99.140.153.78.rep.mailspike.net > [no answer] $ dig 99.140.153.78.rep.mailspike.net ; <<>> DiG 9.10.6 <<>> 99.140.153.78.rep.mailspike.net ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 40483 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 >> dig @1.1.1.1 +short -t A rep.mailspike.net > [no answer] > >> dig @8.8.8.8 +short -t A rep.mailspike.net > [no answer] Using open resolvers to query DNSBLs is pointless. >> dig @127.0.0.1 +short -t A rep.mailspike.net > [no answer] rep.mailspike.net is not even supposed to be a nameserver. I don't see why you think it should have an A record. -- Bill Cole [email protected] or [email protected] (AKA @[email protected] and many *@billmail.scconsult.com addresses) Not Currently Available For Hire