Need HELP - Not all db.files migrating to secondary DNS!

[Barry Margolin]

In article <8jdabb$c44$1 at thoth.cts.com>,
Don Smith <dsm at sandag.cog.ca.us> wrote:
>Hi, we have one primary DNS running BIND 4.9.3-P1 and two secondary DNS
>servers running BIND 8.2.2-P5.  All O/S'es are Solaris 2.6.
>I just noticed that when our primary DNS is down, some of our domains are
>unreachable.
>The primary DNS db files are:
>db.domain1
>db.domain2
>db.domain3
>db.domain4
>etc...
>On the secondary DNS, the only db files that migrate are:
>db.domain1
>db.domain2
>db.domain3
>And that's it!  I've checked the named.boot and named.conf, all appears OK.
>I've changed the serial #, refresh, etc.  I've removed the db files on the
>secondary, restart named, and only dom1, 2, and 3 appear.
>When our primary DNS is down, domain4, domain5, etc are unreachable.
>What am I missing?  What do I need to do?

Have you checked the log on the secondaries, to see whether they complain
about problems when trying to transfer domain4?

When you query your primary server for domain4, does it answer
authoritatively?

-- 
Barry Margolin, barmar at genuity.net
Genuity, 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.