I have a UK database zone file that I would like you to incorporate into a a fresh database for me.
You will the write some code that:-
- Queries the UK domain authority (their DAC) at variable speeds (typically we'll run at 70ms) on port 3043 up to a maximum of 430,000 times per 24 hours.
- Queries the UK domain authority (their DAC) at variable speeds (typically we'll run at 70ms) on port 2043 up to a maximum of 430,000 times per 24 hours.
- The responses will then be stored in the database along with the date that the query was made. The responses from port 2043 contain 2 extra fields than 3043.
- If the DAC responds with a B then the querying should be stopped for whatever period the DAC says the DAC is blocked for (the response would be #B,24 for a block period of 24 seconds for example).
- The querying will prioritise querying on entries that have not before been queried.
- If the querying stops (e.g. if the service stops are the server restarts for example) and then is started again, it must be able to start again from where it last queried.
- Once the final domain in the database is queried, it will start querying from the start again, overwriting whatever data was previously stored for that domain.
- There will be a web interface that must be password protected. I will use this perform my queries on the data from the database. I would like to use it to query all data and run my own SQL queries.
- Your code will run on a CentOS or Ubuntu system (to be decided).
- When you initially incorporate the zone file into the database, I want you to remove all lines that do not end with <domain-name>.[url removed, login to view] or <[url removed, login to view]>. You will also, where <domain-name>.[url removed, login to view] exists but <[url removed, login to view]> does not, will ensure that <domain-name>.uk is added to the database for querying,