slaving a zone called "localhost" won't IXFR

[BOG]

Greetings,
 You should never have to "swap" (transfer) localhost zones. These are special
zones and are used only for the host/ server it is located on. As a matter of
fact, here is a typical entry in named.conf for the zone "localhost":

zone "localhost." in {
    type master;
    file "localhost.zone";
    allow-query { any; };
    allow-transfer { none; };
    notify no;
};

Take note of the "allow-transfer" line. There should be no need to transfer this
zone to any other machine/ host/ server. Each has it's own for *it's own* use.
This is why BIND is telling you "it is already up to date". The log message
is, as it should be. Change the allow-transfer line to none; as above.

Hope this clears things up a bit.

Best wishes,
 Chris


Jeff Stevens <jstevens at vnet.ibm.com> wrote in message news:<cdk37e$2u5f$1 at sf1.isc.org>...
> I have a customer with 2 machines running BIND 8 DNS and he said his zone
> transfers were "failing" for the 'localhost' zone, because he says he does
> an update to the master zone and his SOA on his slave is lower than his SOA
> on his master. I have a log of the slave server job with the message:
> 
> DNS logging: XFER-IN: INFO: ZONE WAS ALREADY UP TO DATE.
> 
> I don't exactly see a problem here, but I am curious how the slave can be
> up-to-date and result in this message?