-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nameserver14 is not implemented #920
Comments
Maybe we should remove the specification from v2021.1 and reinstate it once we have an implementation? That way it's clearer what is implemented and what's not. |
I'll have a look. If it's easy to implement, I'll add the code this week. |
@vlevigneron, we can wait until next release. |
For v2022.1. |
All links to Nameserver14 specifications are now broken. Is this issue still relevant? |
It is stated in the specification
I am not convinced that it is really meaningful. In theory a name server can behave different in the combination, but I think it is less likely, an I think we should other specification and coding. For me it can be removed. |
To be removed by #1390 and zonemaster/zonemaster#1300. |
Test case Nameserver14 is defined but it is not implemented in Nameserver.pm.
The text was updated successfully, but these errors were encountered: