Newbie Mayday

Barry Margolin barmar at bbnplanet.com
Mon Feb 28 15:40:44 UTC 2000


In article <38b9f798 at mars.winshop.com.au>,
Adam Pentland <adam at atnet.net.au> wrote:
>Hi all,
>
>I have just inherited a bind DNS setup that I know little about. Hopefully a
>kind soul out there will lend me a (gentle) hand figuring
>my problem out. All replies are TIA!
>
>I have a primary and a secondary DNS server. If I nslookup the primary I can
>resolve the domain. The secondary cannot resolve it - it displays a list of
>..com.au root servers instead.
....
>named.conf on secondary
>
>zone "coastlinealarms.com.au" {
>type slave;
>file "/etc/bind/coastlinealarms.com.au";
>masters { "210.8.78.175"; };
>};
>
>
>Now with everything I have read, this is all I shold have to do. It is all I
>have done. Have I missed anything? Are there any issues anyone out there can
>see?

That should be all you need to do.  I'm able to transfer the zone from your
primary to my machine, so it looks like it's OK.  You need to check the
log on the secondary to see why it's failing.

Did you reload named on the secondary after updating its named.conf?

-- 
Barry Margolin, barmar at bbnplanet.com
GTE Internetworking, Powered by BBN, Burlington, 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.



More information about the bind-users mailing list