> I collect related NS records and try to ping them from another IP > (different ISP), to be sure that they are not blocked by me nor by my > ISP, and results corresponds with my experiences: > > ns0.sorbs.net. 113.52.8.11 ping fail > ns2.sorbs.net. 87.106.246.125 ping fail > ns4.sorbs.net. 78.153.202.24 ping OK > ns5.sorbs.net. 72.12.198.241 ping fail > ns1175.dns.dyn.com. 108.59.166.201 ping fail > ns2174.dns.dyn.com. 108.59.168.201 ping fail > ns3179.dns.dyn.com. 108.59.170.201 ping fail > ns4151.dns.dyn.com. 108.59.172.201 ping fail > ns9.sorbs.net. 169.48.121.207 ping OK > rbldns10.sorbs.net. 185.87.186.55 ping OK > rbldns7.sorbs.net. 88.208.216.85 ping fail > rbldns0.sorbs.net. 113.52.8.50 ping fail > rbldns17.sorbs.net. 210.50.3.173 ping fail > rbldns3.sorbs.net. 74.208.146.124 ping fail > rbldns16.sorbs.net. 74.53.186.252 ping fail > rbldns8.sorbs.net. 89.150.195.2 ping fail > rbldns4.sorbs.net. 78.153.202.22 ping OK > rbldns15.sorbs.net. 87.106.246.154 ping fail > rbldns2.sorbs.net. 72.12.198.247 ping OK > rbldns18.sorbs.net. 72.12.198.248 ping OK > rbldns14.sorbs.net. 194.134.35.168 ping fail > rbldns12.sorbs.net. 74.208.146.124 ping fail > rbldns13.sorbs.net. 113.52.8.157 ping fail > rbldns6.sorbs.net. 194.134.35.204 ping fail > rbldns1.sorbs.net. 78.153.202.21 ping OK > rbldns11.sorbs.net. 216.12.212.155 ping fail > rbldns9.sorbs.net. 169.48.121.206 ping OK > > As any can see, some responds, and some not... > > I do not know, if they are not accessible or have ICMP blocked, but i > will expect, that if they block ICMP, they will block all not only some > hosts.
Why are you instead not doing a dig against these ips? It's clear you understand that ICMP may be blocked, so why not use a check method that actually uses the protocol you'd use to query them? -Dan _______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
