listen-on change in 9.4.0?

[Joseph S D Yao]

On Tue, Apr 10, 2007 at 08:42:17AM +0200, M??ns Nilsson wrote:
> --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:


DNS and BIND 5th ed. shows both external and internal "port"
declarations as being valid for BIND 9 "listen-on":
	listen-on port 53 { any; };
	listen-on { 127.0.0.1 port 1024; };
but noted the syntax of "listen-on-v6" as still being in flux, with the
external "port" valid but not the internal "port".  To listen on
multiple ports in IPv6, one had to use multiple "listen-on-v6"
statements.

As always, the running program is the ultimate authority.  If the
initial poster has checked to make sure there are no invisible
characters messing up the configuration file, then perhaps 9.4.0 has
regressed to only allowing external "port" declarations, and requiring
multiple "listen-on port XXX { ... };" statements to listen on multiple
ports.  This would make the syntax of "listen-on" and "listen-on-v6" the
same [although one might have preferred the more flexible form].


-- 
Joe Yao
Analex Contractor