Although I did enhance reliability of my other domains with a total of 3 secondaries, I forgot to do so with the most visited bogdan.org.ua. Thus, when yesterday bogdan.org.ua stopped resolving from ns0 and ns1 of XName, the site actually became unaccessible. Other XName-hosted domains, but with more secondaries, are resolving finely even 24 hours after the primary ns failure…

Little research based on the list of free DNS services helped me find this comparison, and made me think this way:

• zoneedit has 18 servers, but had very unfavourable user feedback from it’s users
• everydns has 4 servers and very good user feedback
• editdns has 3 servers, could be a backup
• xname has only 2

There is also freedns.afraid.org, but there was nothing substantial about this service I could find (except for the note that if you’re using one of their subdomains, it might not be visible to Google).

To remedy the problem, yesterday I modified the domain record to contain two more NS. This seems to have helped now. I suspect that I’ll remove XName’s secondary NS from the record, and will replace it with some other secondary NS, and then add one more secondary to get a total of 5 independent NS for the domain.

Update: according to my blog uptime monitor, total domain downtime exceeds 33 hours. Problems started yesterday with two short downtimes (33 and 38 minutes), then domain name went down for 32 hours. Now domain is up, but that could be only because of adding more non-XName secondaries.

Update 2:

XName infrastructure was under heavy attack since friday 8PM (GMT+2).
Until sunday 1PM, despite efforts of our different transit providers, www , ns0, and our internal mail server were unreachable. ns1 was reachable, but not very responsive (about 30% of DNS requests were answered). ns2 was unaffected.
From Sunday 1PM to monday 3AM, ns0 was reachable with a responsiveness of about 50%. ns1 was fully responsive, as ns2. www and internal mail were still heavily affected.