On 2022-02-09 19:31, daniel Azuelos wrote:
• 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)
I'm sorry, but I have no idea what you're talking about. So it seems
that there is no PTR record for 95.46.224.1, how does that relate to the
issue in question? I don't think it's mandatory for every host to have a
PTR record (especially if said host is not a mail server).
More on the topic: I've tried running some more checks from the
ping-admin website, and it seems that different tests yield different
results. For example, it claims that the website is not available from a
certain node, yet it can be pinged from that node and the traceroute
from there also works. For nodes where traceroute doesn't work, it
appears that it can't leave the local ISP's AS.
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.
It's definitely not a local issue because it is happening in several
different places at once and in more than one country (a couple nodes in
Belarus also fail the traceroute check). Might be something on a
regional level, but I have no idea why the impact is so selective. I'm
not a network expert.
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.
I've already tried with the default settings (40 hops I think) - it's
just more of "* * *" and nothing else.
But I think you are right, by this point we've established that this is
highly unlikely to do anything with the operators of the Postfix
website, especially if they don't block IPs by country or region. So
there's probably no point in continuing this discussion here.
---
Kind regards,
Vladimir
