Yup,
Either way will work.
By default named binds to all interfaces.
If you want multiple instances of named on separate interfaces then they
each must have separate named.conf files. Within each named.conf the
global options 'directory', 'listen-on', and 'pid-file' should each be
uniquely defined:
named.conf1:
options { directory "/var/named1"; listen-on { 1.2.3.4; }; pid-file
"named1.pid"; };
named.conf2:
options { directory "/var/named2"; listen-on { 5.6.7.8; }; pid-file
"named2.pid"; };
This supposedly works even on one interface with aliased ip addresses, but
I've only ever did it with separate interfaces.
J.
On Fri, 17 Dec 1999 [EMAIL PROTECTED] wrote:
> Date: Fri, 17 Dec 1999 03:36:49 -0800 (PST)
> From: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: named on aliased IPs?
>
> Is it possible to run two instances of named, each listening at a
> different IP address? "man named" describes listening on different ports,
> but I'd like to bind each instance to a completely different IP address,
> not just a different port.
>
> Or can I run a single instance of named that will listen to the name
> service port on both of my IP addresses?
>
> I think either solution would probably work, but the first one would be
> preferable.
>
> Thanks.
>
> ---------------------------------------------------------------------------
> Assume just 4 million businesses on the Internet today...
> If 1% of them sent you one piece of junk email per year,
> you'd still have to wade through over 100 messages per day.
>
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
