[ Rédigé dans le sens de lecture professionnel. Written in the professional reading direction. ]
I upgraded the subject to something which is not plain wrong. Le (on) 09/02/2022, Vladimir Mishonov <[email protected]> a écrit (wrote): | I can only do the traceroute from my local machine, since I don't have | access to any remote machines where this problem manifests. It stops | returning meaningful results right after the IP that seems to belong to my | ISP, which is a bit strange - this is most certainly not a local problem, Your conclusion is too fast. This is rather some local side problems. There are some of them through the Internet everyday. You can't conclude the problem is at the otherside of the Internet. This is a politician religion. | > player701@player701server:~ % traceroute -m 10 www.postfix.org | > traceroute to postfix-mirror.horus-it.com (65.108.3.114), 10 hops max, | > 40 byte packets | > 1 192.168.0.1 (192.168.0.1) 0.601 ms 0.436 ms 0.274 ms | > 2 95.46.224.1 (95.46.224.1) 2.869 ms 1.036 ms 0.789 ms | > 3 178.219.45.253 (178.219.45.253) 0.731 ms 60.934 ms 1.402 ms | > 4 * * * [...] | > 10 * * * Your traceroute is the sign of 2 key problems: • your DNS is not working, but it is coming from your ISP: alfatelecom.cz: whois -> route: 95.46.0.0/15 descr: IP-AS.COM / IP-AS.RU Master route origin: AS44546 % host 95.46.224.1 Host 1.224.46.95.in-addr.arpa. not found: 3(NXDOMAIN) The SOA of the domain doesn't have a name: % host 21.21.201.91 Host 21.21.201.91.in-addr.arpa. not found: 3(NXDOMAIN) -> serious DNS slaughter • 6 hops without any reply, without being yet out of your ISP -> serious routing slaughter Better contact your ISP ( with a traceroute without the '-m 10' ), rather than the Postfix users worldwide, even if some of them are real Internet goddess. -- « The only thing necessary for the triumph of evil is for good men to do nothing. » Edmund Burke -------- daniel Azuelos
