domains not regging

DomainAngel · Dec 20, 2009

Anyone know why I cant register any domains?

Tried a few hours ago at 123 reg and although they have been quite quick lately, back to old ways and still no reg after 4 hours.

So registered them with fasthosts, and nothing regged there either?

Is this usual?

GreyWing · Dec 20, 2009

If you let me know what it is and your reg details I'll reg it for you via my nom tag and can check it out.

redbird · Dec 20, 2009

Nominet seem to have a few problems with automaton
Service Announcements

FC Domains · Dec 20, 2009

redbird said:
Nominet seem to have a few problems with automaton
Service Announcements

I'm guessing that because there could be some 'renews' backed up in automation, nothing is being allowed to drop.

redbird · Dec 20, 2009

FC Domains said:
I'm guessing that because there could be some 'renews' backed up in automation, nothing is being allowed to drop.

Hadn't considered that, but does seem a likely explanation. Seems they have one hell of a backlog though, guess it just gets worse as people see a request doesn't work so do it again and again.....

DomainAngel · Dec 20, 2009

Thanks GreyWing,

your help was fantastic.

Some great people on Acorn.

khalid · Dec 20, 2009

having the same problem with 123-reg and its bloody annoying.

stevebrowne · Dec 20, 2009

a "high volume of requests". is that just standard renews etc queued up, or is something else happening?

khalid · Dec 20, 2009

regged a domain via 123 a good few hours ago and it is still not registered.

Nominet are probably too busy spending the £15 million they have in the bank on xmas pressies to deal with the "backlog".

This is ridiculous and I hope people on the PAB raise this with them. Idiotic.

GreyWing · Dec 20, 2009

khalid said:
regged a domain via 123 a good few hours ago and it is still not registered.

Nominet are probably too busy spending the £15 million they have in the bank on xmas pressies to deal with the "backlog".

This is ridiculous and I hope people on the PAB raise this with them. Idiotic.

I don't thin k it was no mate, I regged them for Domain Angel within a few minutes of his first post, they were registered instantly. So it's probably more 123 than nom.

redbird · Dec 20, 2009

GreyWing said:
I don't thin k it was no mate, I regged them for Domain Angel within a few minutes of his first post, they were registered instantly. So it's probably more 123 than nom.

I think the problems are just with the automaton, as far as I know EPP is working fine. Did you register via EPP by any chance?

GreyWing · Dec 20, 2009

redbird said:
I think the problems are just with the automaton, as far as I know EPP is working fine. Did you register via EPP by any chance?

Just direct through Nominet's web manager, pretty much instant mate.

khalid · Dec 21, 2009

i'll be telephoning 123-reg in 45mins when lines open to find out what's the crack.

Skinner · Dec 21, 2009

123 lost me a load of names way back because of their 'caching' they apparently cache the requests and queue them to flood them in at an interval instead of real time.

What pissed me off with them was they took my money about 10-20 times too many (2-3 times for some names but upto 5 times for others) and it took me months and months to get the money off them.

Nominet and PAB was their usual toothless self against such a large player.

The result was I took mine, all my friends, all my clients, and everyone else I know (prob 3-5k+ names in total) away from them over to DAILY, because 123-reg's answer to my issue with losing the names (1 of which was regged to ANOTHER 123-Reg customer 36 hours after I paid for it 3 times) was "it wasn't our fault", well it was either them or nom, since other people snatched them away, i'm guessing it wasn't nom heh.

You know they say Cleanliness is next to godliness? Staying with 123 is next to using 1 and 1.

Jump Ship!

khalid · Dec 21, 2009

Skinner said:
123 lost me a load of names way back because of their 'caching' they apparently cache the requests and queue them to flood them in at an interval instead of real time.

What pissed me off with them was they took my money about 10-20 times too many (2-3 times for some names but upto 5 times for others) and it took me months and months to get the money off them.

Nominet and PAB was their usual toothless self against such a large player.

The result was I took mine, all my friends, all my clients, and everyone else I know (prob 3-5k+ names in total) away from them over to DAILY, because 123-reg's answer to my issue with losing the names (1 of which was regged to ANOTHER 123-Reg customer 36 hours after I paid for it 3 times) was "it wasn't our fault", well it was either them or nom, since other people snatched them away, i'm guessing it wasn't nom heh.

You know they say Cleanliness is next to godliness? Staying with 123 is next to using 1 and 1.

Jump Ship!

touch wood i've never had any problems with them and my posts on this thread were Nominet's fault.

I tel'd 123-reg, was told to wait 24/48hrs as I regged over weekend (ok bad advice I know).

I tel'd Nominet and they couldn't find it on the system so they said it was 123-reg's fault however they'd had "technical problems" so might be their fault.

Got refund from 123-reg after they confirmed the registration had been reject from Nominet, probably due to the technical faults, and was able to re-register the domains instantly.

Skinner · Dec 21, 2009

If you search the forum, many people have lost names due to 123-reg being slow, they don't admit to caching requests but its the only logical answer, on one of the other threads someone mentioned another reg that also caches them but I can't remember who it was.

Matthew Yates · Dec 23, 2009

Hi,

As discussed on this thread we did have some problems with the Automaton on 19 and 20 December. This was caused by an unusually high volume of requests to the system. As also mentioned here, this particular incident only affected the Automaton with EPP and Web Domain Manager working as normal. Our service announcement RSS feed did cover the incident at the time.

The incident involved a large volume of repeated automaton requests, leading to a 26 hour processing queue. As these requests followed our system instructions, our Acceptable Use Policy (AUP) did not allow us to remove these requests from the Automaton's queue. This adversely affected every other registrar using the Automaton.

This issue has led us to make a change in the AUP for our registrar systems. The new AUP will allow us to take appropriate action and to minimise the impact this type of incident will have in the future. Further details about these changes are on our web site.

We apologise to customers and to registrars who were affected by this and can assure you that we take the integrity of our systems very seriously and will act rapidly to ensure their protection.

Best regards

Nominet UK

retired_member9 · Dec 23, 2009

Matthew Yates said:
The new AUP will allow us to take appropriate action and to minimise the impact this type of incident will have in the future. Further details about these changes are on our web site.

I wasn't able to see any difference in the supposedly new AUP and the old one.

redbird · Dec 23, 2009

vizzy said:
I wasn't able to see any difference in the supposedly new AUP and the old one.

Appreciate the post Matthew, but perhaps you could summarise the differences as it seems I'm not alone in trying to spot them.

Dave

Matthew Yates · Dec 23, 2009

Hi,

Sorry we had a minor glitch and the same versions were up. We are sorting this out and the versions should be fixed in next 10 minutes.

Thanks for pointing this out.

regards

Matthew