- Joined
- Jun 15, 2019
- Posts
- 210
- Reaction score
- 55
Many questions on this, so heres a quick overview, for those that have the software, theres a DAC timing chart in your build.
Nominet allows 4 DAC processes to run concurrently, however, the hits are ADDED up, and the total must never exceed the max daily allowance of 432000 DAC hits per 24hr period or 1000 DAC hits per minute, or you will enter blocking mode.
Back calculating to remain safe means that you can run full speed for 8 hrs a day only without fear of blocking, the space between hits will be 200ms.
If you run for for the whole day, ie, 24 hours, there will be 600ms between lookups, therefore the probability of a catch decreases by 3 fold.
The time taken to drop to EPP registration against this is only determined by the path time to the Nominet EPP servers, as the actual software process on receipt of the status change is nano seconds, for a good server within the same AS, this should be between 1.5ms to 2ms to the first hop, theres nothing anyone can do with the internal Nominet Lan routing and infrastructure.
Our Dropcatch servers are typically 0.8 to 1.7 ms, available here dont forget your 25% discount
So a high profile catch boils down to the timing between hits, in max mode with a single IPS tag, this is 200ms + EPP reg time, theres a key here on how to improve this, plus recommendations below.
200ms is a long time, and if there are many hundreds chasing the same domain, you can easily see theres a large window, as an example, if your DAC hit happened 5ms after a status change, youll have 195ms before the next check, and in that time, many hundreds of EPP regs can occur, and you wont even know about it.
On really popular domains, they can be re registered between hits... but, our software will detect this due to a renewal date change and warn.
To improve the chances, we incorporate many dynamic algorithms (without adding hundreds of IPS tags...), as well as multiple EPP sockets pre, or as we call them, coil scripts (like a cobra), these are restricted to 6 x under Nominets policies. (note: the SDS verion has 1 x, the SUITE, 6 x)
You can also dynamicaly stager hits using 4 x DAC processes, but remember that running 4 x means each will need its own 200ms slot, the software will calculate this for you, so no blocking occurs.
Hope this helps all, click here to see all the options, ie, web based, shell based, leased and servers
Cheers
Bill
Nominet allows 4 DAC processes to run concurrently, however, the hits are ADDED up, and the total must never exceed the max daily allowance of 432000 DAC hits per 24hr period or 1000 DAC hits per minute, or you will enter blocking mode.
Back calculating to remain safe means that you can run full speed for 8 hrs a day only without fear of blocking, the space between hits will be 200ms.
If you run for for the whole day, ie, 24 hours, there will be 600ms between lookups, therefore the probability of a catch decreases by 3 fold.
The time taken to drop to EPP registration against this is only determined by the path time to the Nominet EPP servers, as the actual software process on receipt of the status change is nano seconds, for a good server within the same AS, this should be between 1.5ms to 2ms to the first hop, theres nothing anyone can do with the internal Nominet Lan routing and infrastructure.
Our Dropcatch servers are typically 0.8 to 1.7 ms, available here dont forget your 25% discount
So a high profile catch boils down to the timing between hits, in max mode with a single IPS tag, this is 200ms + EPP reg time, theres a key here on how to improve this, plus recommendations below.
200ms is a long time, and if there are many hundreds chasing the same domain, you can easily see theres a large window, as an example, if your DAC hit happened 5ms after a status change, youll have 195ms before the next check, and in that time, many hundreds of EPP regs can occur, and you wont even know about it.
On really popular domains, they can be re registered between hits... but, our software will detect this due to a renewal date change and warn.
To improve the chances, we incorporate many dynamic algorithms (without adding hundreds of IPS tags...), as well as multiple EPP sockets pre, or as we call them, coil scripts (like a cobra), these are restricted to 6 x under Nominets policies. (note: the SDS verion has 1 x, the SUITE, 6 x)
You can also dynamicaly stager hits using 4 x DAC processes, but remember that running 4 x means each will need its own 200ms slot, the software will calculate this for you, so no blocking occurs.
Hope this helps all, click here to see all the options, ie, web based, shell based, leased and servers
Cheers
Bill
