RES: problem with bind9, view and nsupdate

Michael Dosser mic at strg.at
Wed Aug 3 08:50:45 UTC 2005


Hi,

Paula Saito Telloli Martins wrote:

> Bind considers each view as a separated nameserver (for different publics).
> So, if you have three views, it considers you have three files (even though
> they are all about the same zone). This way, you must have three different
> files to answer the publics you have and, each one of them will make a
> "zontransfer" according to your named.conf parameters. 

That's what the setup looks like. All different files are included in 
each view. They look all the same for each view. Those zones who are 
intended for the internal view are setup with allow-query { internal; }; 
in named.internal. All other included files in the views have no 
allow-query statement, which AFAIK should fall back to allow-query { 
any; }; right?

> It means that you need to define an IP address (specifically for 
 > allow-transfer) to each view in order to get the correct zonetransfer
 > and correct serial updates between ns1 and ns2.

Both nameservers are in sync (obviously due to the fact, that ns2 is 
also in "view internal"). But not if I dig from a host defined in the 
external view. So what would I have to do to fix this? Put in each view 
a zone-transfer statement (although it is already defined in options? 
Define three IP addresses for ns1' named to listen on?

Thanks for your help,
Michael Dosser

-- 
At end of article, press SPACE for next unread article.



More information about the bind-users mailing list