I think they fixed it. - - - mx:indra.net
1 k.gtld-servers.net 192.52.178.30 NON-AUTH 20 ms Received 2 Referrals , rcode=NO_ERROR indra.net. 172800 IN NS ns1.indra.com,indra.net. 172800 IN NS ns2.indra.com, 2 ns1.indra.com 216.24.137.192 AUTH 88 ms Received 1 Answers , rcode=NO_ERROR indra.net. 3600 IN MX 10 smtp.indra.com, LookupServer 549ms On Wed, Apr 10, 2024 at 10:48 AM Marco Moock <m...@dorfdsl.de> wrote: > Am Wed, 10 Apr 2024 07:14:41 -0700 > schrieb Russell Clemings via mailop <mailop@mailop.org>: > > > There was an outage starting Sunday on indra.net and although they > > say it's up again now, I'm still getting no response from their > > nameservers and mail for their users (or user, as I see only one) is > > still stacking up in my queue. Seems as if maybe they forgot to > > update the DNS for one of their domains; indra.com is working but > > indra.net is not. > > Works for me. > m@localhost:~$ telnet smtp.indra.com 25 > Trying 216.24.136.105... > Connected to smtp.indra.com. > Escape character is '^]'. > 220-mta1.indra.com ESMTP Postfix > ^] > telnet> quit > Connection closed. > > m@localhost:~$ ping ns2.indra.com. > PING ns2.indra.com (216.24.136.120) 56(84) Bytes an Daten. > 64 Bytes von ns2.indra.com (216.24.136.120): icmp_seq=1 ttl=42 Zeit=204 > ms > > m@localhost:~$ ping ns1.indra.com. > PING ns1.indra.com (216.24.137.192) 56(84) Bytes an Daten. > 64 Bytes von ns1.indra.com (216.24.137.192): icmp_seq=1 ttl=42 Zeit=204 > ms > > Run a traceroute to the UDP/TCP port and post that here, so we can see > if that is maybe an error in your network. > From which ISP (AS number) do you try to connect? > -- =============================================== Russell Clemings <rclemi...@gmail.com> ===============================================
_______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
