Odd problem with zones not being loaded

Jim Reid jim at rfc1035.com
Tue Apr 3 17:05:41 UTC 2001


>>>>> "Forrest" == Forrest Aldrich <forrie at navipath.com> writes:

    Forrest> I've noticed a slight problem with some zones not loading
    Forrest> with the latest Bind.8.2.3.

    Forrest> In this case, we have 1.2.3.rev, which loads, but for
    Forrest> some reason the forwards are only loading on the local
    Forrest> machine and not being propogated to all our secondaries.
    Forrest> If I go to a secondary and manually remove ALL the
    Forrest> secondary/*.rev files and then reload, it works.

Could the slaves have zones with SOA serial numbers larger than their
equivalents on the master?

    Forrest> This makes absolutely no sense.  I'm wondering if there
    Forrest> is a new bug present that can cause this problem.  Since
    Forrest> we have many secondaries around the US, this is a major
    Forrest> problem for us to resolve.

    Forrest> I've tried re-updating the SOA, etc.  Nothing erratic is
    Forrest> reported in the named.log.

Well unless you provide the actual zone names and IP addresses of the
servers involved, how do you expect anyone to help? The master
server's logs would be useful too. So would the named.confs and zone
files.


More information about the bind-users mailing list