two nameserver, two ip, one host problem.
Kevin Darcy
kcd at daimlerchrysler.com
Thu Nov 10 00:00:17 UTC 2005
/dev/rob0 wrote:
>On Wednesday 2005-November-09 16:41, Kevin Darcy wrote:
>
>
>>named.conf #1: listen-on { localhost; x.x.x.x; };
>>
>>named.conf #2: listen-on { y.y.y.y; };
>>
>>
>
>Correct me if I'm wrong, but in this context "localhost" is the built-
>in ACL which refers to all interfaces on the machine, so neither could
>use it without a negation:
>
>named.conf #1: listen-on { ! y.y.y.y; localhost; };
>
>named.conf #2: listen-on { y.y.y.y; };
>
>
Ouch, you are correct. Fell into the same old trap :-)
"localhost" doesn't work; it should either be explicitly 127.0.0.1 or,
as you suggested, rearranged as a negation...
- Kevin
More information about the bind-users
mailing list