Re: Why named bind(2)s 0.0.0.0 and :: adresses?

15 msg	NSEC3 support for BIND
4 msg	interface-interval
5 msg	Subnetted Reverse DNS - Going crazy
17 msg	help with bind
2 msg	Secondary NS on Windows and Linux Bind
2 msg	Re: L.ROOT-SERVERS.NET has changed IP address t...
1 msg	[SOLVED] (Was: Re: [FreeBSD 7.0-BETA1] strange ...
2 msg	[FreeBSD 7.0-BETA1] strange behavior in hostnam...
2 msg	BIND/DLZ/MYSQL
9 msg	BIND 9.4.x empty zones
7 msg	named slow resolving to internet
8 msg	named hangs
3 msg	Timed out while zone transfer
3 msg	named-checkzone 9.4.1-P1 appears to treat 'out ...
4 msg	host from BIND 9.4.1-P1 is confused by multiple...
3 msg	DNS-SD and Dynamic Updates
2 msg	forwarder {};
2 msg	SMP and 9.4.1-P1
2 msg	Bind 9.4.1-P1 allowing ddns running on Linux an...

Why named bind(2)s 0.0.0.0 and :: adresses?
\ Adam Tkac (29 Oct 2007)
. \ Mark Andrews (29 Oct 2007)
. . \ Adam Tkac (29 Oct 2007)

Subject:	Re: Why named bind(2)s 0.0.0.0 and :: adresses?
Group:	Bind-users
From:	Adam Tkac
Date:	29 Oct 2007

On Tue, Oct 30, 2007 at 12:21:50AM +1100, Mark Andrews wrote:
>
> FAQ.
>

Thanks, I missed "address" parameter of query-source* option.

Adam

> > Hi all,
> >
> > has anyone here explanation why named bind(2)s addresses 0.0.0.0 and
> > :: ? I have this in options statement:
> >
> > options {
> > ...
> > listen-on port 53 { 127.0.0.1; };
> > listen-on-v6 port 53 { ::1; };
> > ...
> > };
> >
> > but netstat says named listen also on
> > udp 0 0 0.0.0.0:32779 0.0.0.0:* 6898/named
> > udp 0 0 :::32780 :::* 6898/named
> >
> > I'm interested why named listen on that ports.
> >
> > Adam
> >
> > --
> > Adam Tkac, Red Hat, Inc.
> >
> >
> --
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews

--
Adam Tkac, Red Hat, Inc.