We should alter the existing Zenodotus monitoring script to also make sure that DNS entries advertised are properly being handled. i.e. if I advertise abcd1234.zenodotus.poly.edu -> 1.2.3.4, and I query a public DNS server, I should get 1.2.3.4 back. This should ideally be done by generating a random subdomain (perhaps in the form of zenodotus-test-[hash of generated public key](SHA).zenodotus.poly.edu), advertising it to point to blackbox, then verifying that a lookup responds with blackbox's IP address.
We should alter the existing Zenodotus monitoring script to also make sure that DNS entries advertised are properly being handled. i.e. if I advertise
abcd1234.zenodotus.poly.edu->1.2.3.4, and I query a public DNS server, I should get1.2.3.4back. This should ideally be done by generating a random subdomain (perhaps in the form ofzenodotus-test-[hash of generated public key](SHA).zenodotus.poly.edu), advertising it to point to blackbox, then verifying that a lookup responds with blackbox's IP address.