eNom Heads Up- DNS problem

[Grrilla]

I only happened to notice this because I am hosting some photos that disappeared from a listing. I checked the sites index page, and lo and behold, the page was sitting on Sedo parking. Problem is, that's where I had it the day before yesterday and had, since, moved it to my own server space. I uploaded the photos today and saw them resolve on the net w/ my own eyes.

I went to enom to check the dns and got this message.
Nameservers for my domain.net cannot be found.

I tried another domain w/ different name servers, (sedo) and got these two messages:

Failed to get registrar lock
Nameservers for my domain.net cannot be registered.

I went back again a half hour later and successfully reset the name servers but the domain hasn't propagated to my servers, yet, and is still on Sedo's dns.

To make a long story short, the domain was apparently reset to the previous dns which could have, really, created some problems had I not caught it and jumped the images and links over to another domain.

Has anyone else run into this before or have an idea about how this happened??

 

[domainer50]

Ouch. I do not use enom, however im guessing this is a simple issue that can only be worked out with time(possible server malfunction). Did you email enom?

 

[seeker]

this happens infrequently.
I had noticed it only a very few times over the past years.
it has a 'habbit' of happening much more on .co.uk domains.
the only solution I have found is what you did, going back at a later time and retrying to change the nameservers.

 

[Grrilla]

Ouch. I do not use enom, however im guessing this is a simple issue that can only be worked out with time(possible server malfunction). Did you email enom?

Yes. I created a support ticket.

I received this response in an email that arrived today.:
"I accessed your account and confirmed that the DNS are set to the ones
listed in this email."
No explanation, but I did appreciate the fact that someone at the registrar was able to confirm that my domain was, indeed, on the DNS that I had assigned it to and not on someone else's server. :hehe:

this happens infrequently.
I had noticed it only a very few times over the past years.
it has a 'habbit' of happening much more on .co.uk domains.
the only solution I have found is what you did, going back at a later time and retrying to change the nameservers.

I've never seen this before and am relieved to hear that someone else has run across this oddball glitch and that it wasn't a cyber-singularity that was created for my personal edification and enjoyment.

Thanks for the responses.