basic functionality of a slave

[Barry Margolin]

In article <a3eqqm$4hr at pub3.rc.vix.com>,
Patrick Novak <pat.novak at po.state.ct.us> wrote:
>
>i have a master dns running v4.9.4, and a slave running
>v8.2.3.  all appears to be working between the 2, zone
>transfers etc.  i can resolve any host name on the master
>but can only resolve internal hosts on the slave. is this 
>the way it's supposed to work? i expected the slave would
>have the same functionality as the master.

I don't understand what you're saying.  Master and slave apply to specific
zones; a server can be a master for zone A and slave for zone B.  And
resolving external hosts is completely unrelated to whether they're master
or slave for some zones.

>in my named.conf i do not have entries for db.cache, and
>0.0.127.in-addr.arpa. (the db.cache causes errors, and 
>the 0.0.127... i believe shouldnt be entered on the slave -
>maybe i'm wrong??) 

Why don't you have a db.cache?

>beyond that, all other files are
>pulled in the zone transfer.
>other than the "type slave" entries, the db.cache and
>0.0.127.in-addr.arpa entries,  i only have:
>options {
>        forwarders { 1.2.3.4; };
>        directory "/var/named";
>            };
>
>pretty straight-forward - any suggestions?

Even if you're configured with forwarders you should have a root hints
zone configured.

-- 
Barry Margolin, barmar at genuity.net
Genuity, Woburn, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.