Skip to content
madestro edited this page Jul 25, 2018 · 1 revision

TestResolvers project

A server will be developed, which include:

  • Send jobs to the resolvers? or only receive from them?
  1. in first case, a pool of resolvers has to be stored and managed, IP files has to be sent each time.
  2. in second case, keys and IP file renovation has to be managed
  • the pool of resolvers has to be geolocated and registered with its isp information
  • Authentication, for receive data only for valid resolvers
  • Data analysis:
  1. number of resolvers by port 53 (is the service accepting recursion?)
  2. is a valid dnssec name well managed?
  3. is an invalid dnssec well managed? (yes => Rcode with error)
  4. has the resolver some authoritative info? yes? which one? (why?)
  5. is the received information the same for all probes?
  • Which DB we will use?

A client side will be developed:

  • Performing all resolver-tests
  1. is Alive?
  2. has Recursion?
  3. is valid dnssec well managed?
  4. is invalid dnssec well managed?
  5. is QID random?
  6. is IP PORT random?
  • How to test if QID and Port are random?

A pool of tests must be developed

  • Authentication
  • communication
  • border errors
  • performance tests?
Clone this wiki locally