Views...

[Kevin Darcy]

Forrest Aldrich wrote:

>So, I presume that zone "." and any other data you want that is technically 
>local must go into a view, like the internal "view"?   The DNS book I have 
>doesn't seem to have a really good example going.
>
>
>
>At 12:19 AM 9/27/2003, Forrest Aldrich wrote:
>  
>
>>I do serve a couple of small zones, but my own zone is hosted elsewhere.
>>
>>
>>
>>At 10:28 PM 9/26/2003, Kevin Darcy wrote:
>>    
>>
>>>Forrest Aldrich wrote:
>>>
>>>      
>>>
>>>>I'm creating a named.conf with views support.   It seems you must have all
>>>>zones in a view.
>>>>
>>>>My internal LAN is an RFC network, so when I go to mydomain.com, I 
>>>>        
>>>>
>>want the
>>    
>>
>>>>view to indicate that RFC address, not the routable address on the 
>>>>        
>>>>
>>external
>>    
>>
>>>>interface; however, my real DNS is served externally (ie: by another
>>>>source) so I don't need inbound queries on those zones.
>>>>
>>>>I suppose it's harmless to simply place a stub db.* file in the "external"
>>>>view to get this working, but I wonder if I'm doing this correctly.
>>>>
>>>>        
>>>>
>>>If you're not serving anything to the Internet, why bother with views at
>>>all? Who is going to see your "external" view?
>>>
>>>- Kevin
>>>      
>>>
Right. Think of each view as kind of a "virtual" nameserver instance, 
with its own set of zone definitions, etc. Just as a regular nameserver 
instance needs some sort of root-zone definition (which could possibly 
be the compiled-in definition if nothing is defined explicitly), so does 
a "view".

I thought the "view" example on pages 326 and 327 of _DNS_and_BIND_, 
Fourth Edition, were pretty handy...

- Kevin