- Joined
- Oct 15, 2012
- Posts
- 1,325
- Reaction score
- 191
No becasue according to Nominets website they are release randomly![]()
I know, I'm just trying to grasp the conspiracy theories
No becasue according to Nominets website they are release randomly![]()
No becasue according to Nominets website they are release randomly![]()
To catch so consistently with so much competition at any point in the 24 hours and the drop time be completely random is impossible. The maths don't allow it.
It's either knowing the drop time or utilising a lot more tags/quota. This is not a single script / DAC quota running that fast for 24 hours. Not a chance.
It's either knowing the drop time or utilising a lot more tags/quota. This is not a single script / DAC quota running that fast for 24 hours. Not a chance.
Well it's always the same TAG catching and I don't think it's multiple but perhaps his found a way around the limits?
To catch so consistently with so much competition at any point in the 24 hours and the drop time be completely random is impossible. The maths don't allow it.
So if you had a multiple tag/quota system in place, you could just hammer the DAC across the tags, and then register to your primary tag for the catch? You'd only need 4 tags to trump the theoretical 16.67/sec limit of one tag across 60 secs, with 20/sec possible across the 4 sticking to the 24hour 5/sec limit. You wouldn't need to know exact drop times then. Sounds like a bloody good plan... despite Nominet not allowing multiple tags, you'd only need some mates up for it. Sorry if this is all common knowledge, I'm still catching up!
There's a difference between knowing the drop time and knowing the drop order. Many years ago a number of people worked out the drop time (the interval) between domain names dropping. What they didn't know is which domain names would drop at the particular time intervals. Obviously it would help to know which time intervals to target ones resources at and would help even more if one had figured out a drop pattern or order.
(from iPhone)
In respect of the live DAC, yes. Purely for clarification here is it assumed to be a breach of the anti avoidance rules to buy in access to more DAC whether that be the live DAC or the delayed DAC?
(from iPhone)
There have been multiple ways discovered over the years to do exactly this, so dismissing it as impossible is a mistake.
It's much easier to cry bug/foul play than it is to put the time in to find out what's happening for yourselves, but it's not going to get you anywhere 'cos there is no bug or foul play going on as far as I can see.
Grant
If you have contacts / colleagues who are happy to become Nominet members with DAC access, I don't know how Nominet could police this at all. You'd just host scripts on different servers with different IPs and geo. To Nominet, it would ust look like multiple catchers going after the same premium names.
If you have contacts / colleagues who are happy to become Nominet members with DAC access, I don't know how Nominet could police this at all. You'd just host scripts on different servers with different IPs and geo. To Nominet, it would ust look like multiple catchers going after the same premium names.
But in this case the drops still end up on the same tag. It wouldn't be hard for Nominet to see which tag sent the registration request and see which tag the domain ended up on.
You can't "collaborate" or pool multiple dacs, you can however use multiple dacs which belong to multiple other real people.
The people who run untagged.co.uk blatantly on their site request people "lease" them their dac.
I presume as long as each dac runs independently and trace back to a real person, then lease 10, little difference between you booking me for a day to catch a name, than booking my dac for a month ?
Does that mean you could (theoretically) legitimately lease 24 "real" DACs from 24 different genuinely arms-length third parties, and run each for exactly 1 hour a day, with zero overlap?
Under that scenario, there would then be no need for any of the individual DACs to "collude" in any programmatic way with any of the others since each would be running genuinely as if the others didn't exist post-setup - just for 1/24th of a day apiece.
We use essential cookies to make this site work, and optional cookies to enhance your experience.