We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently the 0 1 port . is used:
0 1 port .
mox/mox-/admin.go
Lines 936 to 943 in 68c130f
Instead of 0 0 0 ., like in the RFC examples of RFC 2782 or RFC 6186.
0 0 0 .
Is there any reason to include the port number and pick a weight of 1? Note this RFC 2782 quote about the weight selection:
1
Domain administrators SHOULD use Weight 0 when there isn't any server selection to do, to make the RR easier to read for humans (less noisy).
BTW cool you already implemented these records, I was researching it for:
The text was updated successfully, but these errors were encountered:
3554880
also use "SRV 0 0 port ." in webadmin pages
c13f181
for issue #240, thanks bwbroersma for reporting and patch
Excellent, thanks! I don't think I had a reason for not using weight 0. I wouldn't be surprised if I never looked at RFC 2782...
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Currently the
0 1 port .
is used:mox/mox-/admin.go
Lines 936 to 943 in 68c130f
Instead of
0 0 0 .
, like in the RFC examples of RFC 2782 or RFC 6186.Is there any reason to include the port number and pick a weight of
1
?Note this RFC 2782 quote about the weight selection:
BTW cool you already implemented these records, I was researching it for:
The text was updated successfully, but these errors were encountered: