multiples views in function of ip server

Kevin Darcy kcd at daimlerchrysler.com
Wed Sep 18 22:05:13 UTC 2002


Saad Kadhi wrote:

> On Wed, Sep 18, 2002 at 12:49:39PM +0200, Hostmaster wrote:
> > I have a box with two interfaces connected to two different ISP with two
> > different ip. There is one bind 8.3.3 server running, listening on all
> > interfaces. I have a problem with SOA registry, because I need that when some
> > client ask dns-on-isp1 SOA must be dns-on-isp1, and when some client ask
> > dns-on-isp2, SOA must be dns-on-isp2. All files are dns-on-isp1. I see that
> > multiples views selecting by client ip, and I use it in one slave with bind9,
> > but nothing about server ip. how could configure it for do this?
> errm. the SOA record must be unique within a given zone. if dns-on-isp1 and
> dns-on-isp2 are authoritative for the same zone, then the mname field of the SOA
> record is the same. and save for specific requirements for dynamic updates, I
> cannot think of any practical use of having different mname fields depending on
> on which interface of the same nameserver receives the request.
>
> and by the way, how would a client end up asking one or the other dns-on-ispx
> unless the delegation information contains NS records for both? in this case,
> why don't you setup the thing as it should be ? that is, put a primary master as
> dns-on-ispx and a slave on dns-on-ispy. if you are short on hardware, either use
> two differents instances of BIND 8, one as a master, the other as a slave or
> better, use BIND 9 with views and listen-on substatements.

You don't need listen-on substatements; just use "match-destinations".


- Kevin





More information about the bind-users mailing list