tags 610036 fixed-upstream
thanks

On Thu, Oct 25, 2012 at 2:14 AM, Simon Paillard <spaill...@debian.org> wrote:
> Control: -1 tag +patch
>
> Hi,
>
> On Sat, Jun 09, 2012 at 07:43:46PM +0200, Witold Baryluk wrote:
>> On 06-09 15:36, Simon Paillard wrote:
>> > On Sat, Jan 15, 2011 at 12:52:17AM +0100, Witold Baryluk wrote:
> [..]
>> > > I today discovered undocumented feature of resolv.conf
>> > > Nameply nameserver can be a IPv6 address!
>> > > Current manpage (implicitly) says only IPv4 is supported.
>> > > ==================
>> > > nameserver 2001:470:20::2
>> > > nameserver 149.156.82.205
>> >
>> > Well, not documented indeed, I wonder if it is really necessary to 
>> > explicit this.
>>
>> Well, many programs often use slightly different notation for IPv4 and
>> IPv6, like putting IPv6 in square brackets (this is for example a case
>> for hosts.allow/hosts.deny syntax).
>
> Code (function inet_pton6) says it conforms to RFC 1884:
>    2.2 Text Representation of Addresses
>    http://tools.ietf.org/html/rfc1884#page-4
>
> In the same time, inet_pton manpages says it's RFC2373 (a small update, not
> changing IPv6 address string format):
>    http://tools.ietf.org/html/rfc2373#section-2.2
>
> Patch sent upstream.
>
>> It also needs documenting, in case in the future glibc would allow
>> changing default port 53 to something else.
>>
>> One could think that it will be something like  'nameserver
>> 10.0.1.1:5353', but it will not work in ipv6 case. So probably a
>> keyword-like syntax 'nameserver 10.0.1.1 port 5353', or squere brackets
>> notations (like in URLs), will be needed.
>
> Let's keep future evolutions for future documentation :)
>
>> Some tools like network-manager, resolvconf, rdnssd, openvpn, etc.
>> sometimes need to write to resolv.conf and until it is documented and
>> stabilized, it cannot be done safely.
>
> PS: btw, I've checked v4/v6 in this manpage, glibc happens to not implement
> sortlist for IPv6 addresses.

Simon, I've applied a slightly modified version of your patch, for
upstream 3.45.

Cheers,

Michael


--- a/man5/resolv.conf.5
+++ b/man5/resolv.conf.5
@@ -42,8 +42,9 @@ and the domain search path is constructed from the
domain name.
 The different configuration options are:
 .TP
 \fBnameserver\fP Name server IP address
-Internet address (in dot notation) of a name server
-that the resolver should query.
+Internet address of a name server that the resolver should query,
+either an IPv4 address (in dot notation),
+or an IPv6 address in colon (and possibly dot) notation as per RFC 2373.
 Up to
 .B MAXNS
 (currently 3, see \fI<resolv.h>\fP) name servers may be listed,


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to