Document that an IPv6 nserver address needs square brackets

nserver and authnserver parse their argument with parsehost(), which reads
the first colon as the address/port separator, so a bare IPv6 address picks
up a bogus port number. Document the bracket form in 3proxy.cfg(5) and in
both HOWTOs.

Refs #1275, #460

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Vladimir DubrovinandClaude Opus 5 committed 2026-09-16 15:04:08 +03:00
1 parent 97ac10b3c5
commit f20848fda7
4 files changed
+18 -3

No files matched your search

+5 -1
View File
@@ -482,7 +482,11 @@ experimental.</p>
Nameserver to use for name resolutions. If none specified
system routines for name resolution is used. Optional port
number may be specified. If optional /tcp is added to IP
address, name resolution is performed over TCP.</p>
address, name resolution is performed over TCP. An IPv6 address
has to be enclosed in square brackets: <br>
<b>nserver 1.1.1.1</b> <br>
<b>nserver [2001:4860:4860::8844]</b> <br>
<b>nserver [2001:4860:4860::8844]:5353/tcp</b></p>
<p style="margin-left:9%; margin-top: 1em"><b>authnserver</b>