I've received a report from someone that said that all IP lookups against the SpamCop blocklist resulted in blocks during this time. Did anyone else have the same observation? I'm trying to figure out if this person has a bad blocklist lookup implementation (saying an IP is in the list, as opposed to returning an error, when the blocklist DNS is unavailable), or if it was something larger.
./don > On Jan 31, 2021, at 09:01, Don Owens <d...@regexguy.com> wrote: > > We have the domain back now, but we have to wait for propagation delays. If > you query the name servers they Arne mentioned, that should give you the > right IPs. > > Sorry for the trouble, folks. Now I have to go see who needs flogging. > > ./don > > > >> On Jan 31, 2021, at 08:36, Arne Jensen via mailop <mailop@mailop.org> wrote: >> >> >>> Den 31-01-2021 kl. 16:56 skrev Andreas Schamanek via mailop: >>> >>> Could someone provide the old but apparently still valid IP addresses >>> so that we can configure DNS forwarding locally instead of disabling >>> the DNSBL? >>> >> Domain was updated ~21 minutes ago on 2021-01-31T16:04:06Z, now saying: >> >> Name Server: NS1-109.AKAM.NET >> Name Server: NS1-11.AKAM.NET >> Name Server: NS1-73.AKAM.NET >> Name Server: NS1-90.AKAM.NET >> Name Server: NS1-93.AKAM.NET >> Name Server: USE1.AKAM.NET >> >> -- >> Med venlig hilsen / Kind regards, >> Arne Jensen >> >> _______________________________________________ >> mailop mailing list >> mailop@mailop.org >> https://list.mailop.org/listinfo/mailop _______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
