Replies should have the aa (Authoritative) flag set to true #11
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
``` chashell 300 IN A [SERVERIP] c 300 IN NS chashell.[DOMAIN]. ``` The chanserv unning at [SERVERIP] is an authoritative nameserver for chashell.[DOMAIN]. The message header reply should have the 'aa' (Authoritative) flag set. Without this flag set, a strict recursive nameserver may block replies from reaching the client. This was observed with DigitalOcean for example.
lts-rad
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The chanserv running at [SERVERIP] is an authoritative nameserver for chashell.[DOMAIN].
The message header reply should therefore have the 'aa' (Authoritative) flag set.
Without this flag, a strict recursive nameserver may block replies from reaching the client