----- Original Message ----- > From: "Robert L Mathews" <li...@tigertech.com> > > However, if "example.com" uses "ns1.he.net" and "ns2.he.net" as its > nameservers, > having the second of those instead be "ns2.he.org" will keep "www.example.com" > reachable if he.net is placed on clientHold. > > That was presumably the emergency concern in this case -- not so much that > www.he.net itself was offline, but that all the other domains using their > nameservers were offline.
Correct. I was not the person who made the original query/report, but that was the concern which made me run the event up the flagpole here and on Outages. > I run a registrar so there's no risk of our domain names getting put on > clientHold, but I still don't trust the *registry* not to put one of our > domain > names on their equivalent "serverHold". And it is there that perhaps I overreacted one step; I had thought from the data I heard that that *was* a registry-side hold (and hence it didn't matter that it was NetSol). Or perhaps that NetSol was still the registry for .net -- that's out of date now, isn't it? Cheers, -- jra -- Jay R. Ashworth Baylink j...@baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://www.bcp38.info 2000 Land Rover DII St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1274
