3 ms·
a.ns13.net. and b.ns13.net. were the last 2 to be fixed, seems to be all ok now. If you can, flush your resolver cache.
by supine 13y ago
a.ns13.net. and b.ns13.net. were the last 2 to be fixed, seems to be all ok now. If you can, flush your resolver cache.