Chuck Hatcher wrote:
I don't know what problems Tucows had, or whether they affected theirIn our case the problem was reported by a script that queries ns1.mdnsservice.com for information on one of our zones, and if it doesn't get the IP it was expecting, it raises an alarm.
Managed DNS. I do know that I had problems with a large number of domains
not using Tucows DNS at about the same time, and it appeared to me there was
a problem with the root or gTLD servers. I could not get a response for any
query for any domain. May have been coincidence, or it may have been a
problem on my end, I just don't know.
I wasn't monitoring ns[1-3].mdnsservice.com myself and I wasn't online when the issue occured, so I wasn't able to do any actual debugging.
-- SCIENTISTS COMPARE APPLES AND ORANGES FOR VITAMIN CONTENT "It's like comparing apples and oranges," says researcher
