Question about the dac

[AssetDomains]

Not sure I'll get an answer or not to this but is this a common occurrence as I'm at a loss to why I didn't get the domain and I see this situation in my logs now and again.

1380458206.9304 epoints.co.uk,Y,N,1999-06-29,2013-06-29,NETBANX
1380458207.0385 registration sent for epoints.co.uk
(I sent my first request here pings say I'm less than 2ms from nom)

My script stops for 100ms then queries the dac again domain still not registered apparently so sends the request again.

1380458207.1477 registration sent for epoints.co.uk

So my question is how does my first request not win the race is there delay between registration and the dac updating or is my reading of the timings completely wrong

 

[Skinner]

There is a delay between the dac and registry, this gap from mine and a few other peoples logs is as large as 400ms. This is based on comparing all our logs from when we got the last regged to old tag response and first ,N then the last ,N and first new tag response.

Allowing for polling delays and such I'd say there is at least 200ms delay between the name being regged and the dac showing such.

Going off your log, you have 100ms+ delay between your polls, so if someone else polled between 6.9314 and 7.0384 they would have sent the reg off before you. 100ms is a massive time in terms of catching.

 

[RobM]

The dac will show domains as available when they aren't. This is (according to nominet) due to the epp not informing the dac of a registration instantly. Thus it is possible to see domains available for a couple of pollings but they are already taken.
1380458207.0385 registration sent for epoints.co.uk
The domain had already gone - dac wasn't current yet.

 

[AssetDomains]

Thanks guys was hoping there was some sort of delay and not my script letting me down.