On 28/11/2023 08:59, Noel Butler wrote:
~$ host 24.116.100.90
;; connection timed out; no servers could be reached
Seems like AT&T *ARE* doing the correct thing and it is *YOU* with the
problem. before you start calling others f'wits do better
investigation, a dig trace indicates root servers dont know you.
Seems your IP provider is the onle with problems, now I get an answer of
sorts
~$ dig +trace -x 24.116.100.90
< snip >
116.24.in-addr.arpa. 86400 IN NS ns2.cableone.net.
116.24.in-addr.arpa. 86400 IN NS ns1.cableone.net.
116.24.in-addr.arpa. 10800 IN NSEC 117.24.in-addr.arpa. NS RRSIG NSEC
116.24.in-addr.arpa. 10800 IN RRSIG NSEC 8 4 10800 20231211213247
20231127203247 6558 24.in-addr.arpa.
ChfIccQU9mphSoPwTZf6Og2pumL3BRTQBGm7ZyFb5R8ycVL/jyXD94O8
XOLL48wgXFQPuW4bfoSlmB/nNJ4tfb1Vyeb3x5MmVQTL74tdotoGfFYS
2+gjyFWYkWAtkzOAmC7Eeva7hotpQ9Qa3LbkFtfznKBFdPAHHQ1vXs0K Shg=
;; Received 366 bytes from 199.180.180.63#53(r.arin.net) in 194 ms
;; connection timed out; no servers could be reached
On 28/11/2023 07:31, Philip Prindeville wrote:
We're being blacklisted by att.net with the following message:
(reason: 550 5.7.1 Connections not accepted from servers without a
valid sender domain.flph840 Fix reverse DNS for 24.116.100.90)
I don't know what the hell is up with these pinheads:
--
Regards,
Noel Butler
