7 Feb
2014
7 Feb
'14
2:01 p.m.
On Fri, Feb 07, 2014 at 03:33:30PM -0500, Aju Francis <mail@ajufrancis.com> wrote a message of 50 lines which said:
Anyone seeing issues with geo.kaspersky.com DNS ?
Why not sending the output of tests done with dig, next time? You would not report a routing problem without posting traceroute's results. Works for me: % check-soa -i geo.kaspersky.com geons1.kaspersky-labs.com. 4.53.58.200: OK: 1391806811 (103 ms) geons2.kaspersky-labs.com. 195.27.181.5: OK: 1391806811 (11 ms) geons6.kaspersky-labs.com. 202.177.216.203: OK: 1391806811 (357 ms) geons8.kaspersky-labs.com. 4.28.136.49: OK: 1391806811 (98 ms) geons9.kaspersky-labs.com. 195.122.169.46: OK: 1391806811 (11 ms)