You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Root hints data is stored as a data section in Zonemaster/Engine/Recursor.pm. For some use cases it can be useful to be able to change that to private root hints data:
DNS training using a private DNS tree including root and TLDs.
Zonemaster unit tests making it possible to set up both parent and child in a private tree including TLDs.
To make these use cases possible, put the root hints data was a separate data file. Also make it possible to override that file with a private hints file without updating the perl code.
The text was updated successfully, but these errors were encountered:
Parsing as such should not be a problem, but keep keeping it in json format is not much extra work since it is not updated often. The question is rather how we are triggered to do the update.
If we keep it in its original format we could have a make target download the current version and diff it against our snapshot.
A possible downside to parsing the original format is that it could introduce additional dependencies.
Another possibility could be if IANA has a mailing list or something for announcements regarding the root hints file.
Root hints data is stored as a data section in
Zonemaster/Engine/Recursor.pm
. For some use cases it can be useful to be able to change that to private root hints data:To make these use cases possible, put the root hints data was a separate data file. Also make it possible to override that file with a private hints file without updating the perl code.
The text was updated successfully, but these errors were encountered: