slaving a zone called "localhost"

[Jeff Stevens]

I have a customer with 2 machines running BIND 8 DNS and he said his zone 
transfers were "failing" for the 'localhost' zone.  I have a log of the 
slave server job with the message:

DNS logging: XFER-IN: INFO: ZONE WAS ALREADY UP TO DATE.

The zone definition from named.conf is:

zone	"localhost" {
	type slave;
	file "LOCALHOST.DB";
	masters {
		192.168.2.10;
	};
	forward first;
	check-names ignore;
	dialup no;
	max-transfer-time-in 60;
	notify yes;
};

I don't see a problem here, but I am curious how the slave can be up-to-date 
and result in this message?

-- 
Jeffrey Stevens