[prev in list] [next in list] [prev in thread] [next in thread]
List: bind-users
Subject: Re: Wrong IP Lookup
From: Kevin Darcy <kcd () daimlerchrysler ! com>
Date: 2004-11-29 22:42:41
Message-ID: 41ABA5E1.6070206 () daimlerchrysler ! com
[Download RAW message or body]
Norman Zhang wrote:
>>>I have BIND setup to take DDNS from a multihomed box. DDNS are enabled
>>>on both NICs. For example,
>>>
>>>dc1.mydomain.com 192.168.11.21 192.168.22.21
>>>
>>>However, the wrong IP may sometimes be resolved for the wrong subnet.
>>>Is there a way I can restrict hosts in 192.168.22.0/24 subnet to
>>>resolve to 192.168.22.21 only? And likewise for subnet 192.168.11.0/24?
>>>
>>>
>>Try the "sortlist" config statement.
>>
>>
>
>Thanks Nicolas. I'm currently away from the box. I'll try to do
>something like the following. Will this do?
>
>view "LAN1" {
> match-clients { 192.168.11.0/24; };
>
> sortlist { 192.168.11.0/24; };
>
> zone "hq.arkonnetworks.com" {
> type master;
> file "db.hq.arkonnetworks.com";
> allow-update { 192.168.11.0/24; 192.168.22.0/24; };
>};
>
>view "LAN2" {
> match-clients { 192.168.22.0/24; };
>
> sortlist { 192.168.22.0/24; };
>
> zone "hq.arkonnetworks.com" {
> type master;
> file "db.hq.arkonnetworks.com";
> allow-update { 192.168.11.0/24; 192.168.22.0/24; };
>};
>
If sortlist works for you, why bother with the views?
- Kevin
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic