listen-on change in 9.4.0?

Måns Nilsson mansaxel at kthnoc.net
Tue Apr 10 06:42:17 UTC 2007


--On måndag, måndag 9 apr 2007 10.53.31 -0500 Jeff Stevens
<jstevens at vnet.ibm.com> wrote:
> Seems the listen-on no longer takes a port inside the braces in 9.4?
> BIND 9.3 book example on page 270:
> 
> options {
> 	listen-on { 192.249.249.1 port 5353; 192.253.252.1 port 1053};
> };
> 
> but in our 9.4.0 test config we have
> 
> listen-on { 9.5.143.134 port 9000; };
> 
> and named-checkconf gives:
> 
> named.conf:77: missing ';' before 'port'

Manual says:

Interfaces

The interfaces and ports that the server will answer queries from may be
specified using the listen-on option. listen-on takes an optional port, and
an address_match_list. The server will listen on all interfaces allowed by
the address match list. If a port is not specified, port 53 will be used.

Multiple listen-on statements are allowed. For example,

listen-on { 5.6.7.8; };
listen-on port 1234 { !1.2.3.4; 1.2/16; };
will enable the name server on port 53 for the IP address 5.6.7.8, and on
port 1234 of an address on the machine in net 1.2 that is not 1.2.3.4.

If no listen-on is specified, the server will listen on port 53 on all
interfaces.

The listen-on-v6 option is used to specify the interfaces and the ports on
which the server will listen for incoming queries sent using IPv6.

When

{ any; }
is specified as the address_match_list for the listen-on-v6 option, the
server does not bind a separate socket to each IPv6 interface address as it
does for IPv4 if the operating system has enough API support for IPv6
(specifically if it conforms to RFC 3493 and RFC 3542). Instead, it listens
on the IPv6 wildcard address. If the system only has incomplete API support
for IPv6, however, the behavior is the same as that for IPv4.

A list of particular IPv6 addresses can also be specified, in which case
the server listens on a separate socket for each specified address,
regardless of whether the desired API is supported by the system.

Multiple listen-on-v6 options can be used. For example,

listen-on-v6 { any; };
listen-on-v6 port 1234 { !2001:db8::/32; any; };
will enable the name server on port 53 for any IPv6 addresses (with a
single wildcard socket), and on port 1234 of IPv6 addresses that is not in
the prefix 2001:db8::/32 (with separate sockets for each matched address.)

To make the server not listen on any IPv6 address, use

listen-on-v6 { none; };
If no listen-on-v6 option is specified, the server will not listen on any
IPv6 address.

	(Administrators Reference Manual, Chapter 6.)
-- 
MÃ¥ns Nilsson                     Systems Specialist
+46 70 681 7204   cell                       KTHNOC
+46 8 790 6518  office                  MN1334-RIPE

I can't think about that.  It doesn't go with HEDGES in the shape of
LITTLE LULU -- or ROBOTS making BRICKS ...



More information about the bind-users mailing list