1 # Configuration for getaddrinfo(3).
3 # So far only configuration for the destination address sorting is needed.
4 # RFC 3484 governs the sorting. But the RFC also says that system
5 # administrators should be able to overwrite the defaults. This can be
8 # All lines have an initial identifier specifying the option followed by
9 # up to two values. Information specified in this file replaces the
10 # default information. Complete absence of data of one kind causes the
11 # appropriate default information to be used. The supported commands include:
14 # If set to yes, each getaddrinfo(3) call will check whether this file
15 # changed and if necessary reload. This option should not really be
16 # used. There are possible runtime problems. The default is no.
18 # label <mask> <value>
19 # Add another rule to the RFC 3484 label table. See section 2.1 in
20 # RFC 3484. The default is:
26 #label ::ffff:0:0/96 4
30 # This default differs from the tables given in RFC 3484 by handling
31 # (now obsolete) site-local IPv6 addresses and Unique Local Addresses.
32 # The reason for this difference is that these addresses are never
33 # NATed while IPv4 site-local addresses most probably are. Given
34 # the precedence of IPv6 over IPv4 (see below) on machines having only
35 # site-local IPv4 and IPv6 addresses a lookup for a global address would
36 # see the IPv6 be preferred. The result is a long delay because the
37 # site-local IPv6 addresses cannot be used while the IPv4 address is
38 # (at least for the foreseeable future) NATed.
40 # precedence <mask> <value>
41 # Add another rule the to RFC 3484 precedence table. See section 2.1
42 # and 10.3 in RFC 3484. The default is:
44 #precedence ::1/128 50
46 #precedence 2002::/16 30
48 #precedence ::ffff:0:0/96 10
50 # For sites which prefer IPv4 connections change the last line to
52 #precedence ::ffff:0:0/96 100