-
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
IN_BAILIWICK_ADDR_MISMATCH should give more information #467
Comments
@matsduf I just started to look at that. I noticed (but perhaps is is what we want), that there is no messages specified for IN_BAILIWICK_ADDR_MISMATCH and OUT_OF_BAILIWICK_ADDR_MISMATCH cases. Is it something we decided in a past discussion ? |
In this specific case (aka IN_BAILIWICK_ADDR_MISMATCH), it lists what is found in parent zone AND is missing from child. |
No, there should be messages for IN_BAILIWICK_ADDR_MISMATCH and OUT_OF_BAILIWICK_ADDR_MISMATCH, respectively. What you want in "mismatch" is something like "found in parent, found in zone". |
OK, I can do that. |
Perhaps it needs to be refined, but tell me if the corresponding PR is more or less what you have in mind. |
Fixed by #515. |
Test Case Consistency05 (as currently in the develop branch) returns the message IN_BAILIWICK_ADDR_MISMATCH when there is a mismatch of the IP address for an in-bailiwick name server between delegation and authoritative zone. It then returns the names and IP addresses of the name servers as stated in the delegation but information on what has been found in the authorititative zone is not listed, i.e. it is impossible to see what the problem is.
The text was updated successfully, but these errors were encountered: