That cat was a typo, or cut-n-paste blunder, that chopped off the last
part. The zone file does load on the master.

The host file loads on startup.

log on ns1 (master):
--------------------------------------------------------------------

Oct 25 08:46:45 apollo named[6016]: starting BIND 9.2.1 -u named
Oct 25 08:46:45 apollo named[6016]: using 1 CPU
Oct 25 08:46:45 apollo named[6019]: loading configuration from
'/etc/named.conf'
Oct 25 08:46:45 apollo named[6019]: no IPv6 interfaces found
Oct 25 08:46:45 apollo named[6019]: listening on IPv4 interface lo,
127.0.0.1#53
Oct 25 08:46:45 apollo named[6019]: listening on IPv4 interface eth0,
216.55.144.16#53
Oct 25 08:46:45 apollo named[6019]: command channel listening on
127.0.0.1#953
Oct 25 08:46:45 apollo named[6019]: zone 0.0.127.in-addr.arpa/IN: loaded
serial 1997022701
Oct 25 08:46:45 apollo named[6019]: zone 144.55.216.in-addr.arpa/IN:
loaded serial 2004021516
Oct 25 08:46:45 apollo named[6019]: zone webmedianow.com/IN: loaded serial
2002009059
Oct 25 08:46:45 apollo named[6019]: zone localhost/IN: loaded serial 42
Oct 25 08:46:45 apollo named[6019]: running
Oct 25 08:46:45 apollo named[6019]: zone 144.55.216.in-addr.arpa/IN:
sending notifies (serial 2004021516)
Oct 25 08:46:45 apollo named[6019]: zone webmedianow.com/IN: sending
notifies (serial 2002009059)
Oct 25 08:46:45 apollo named: named startup succeeded

log on ns2 (slave)
--------------

And, this is what I get on the slave side:


Oct 25 08:41:53.248 received notify for zone 'webmedianow.com': not
authoritative
Oct 25 08:43:02.078 createfetch: apollo.webmedianow.com A
Oct 25 08:43:02.093 lame server resolving 'apollo.webmedianow.com' (in
'webmedianow.com'?): 216.55.144.33#53
Oct 25 08:43:02.095 no_references: delete from rbt: 0x2ce400
apollo.webmedianow.com
Oct 25 08:46:14.336 received notify for zone 'webmedianow.com': not
authoritative
Oct 25 08:47:28.235 received notify for zone 'webmedianow.com': not
authoritative
Oct 25 08:47:41.996 received notify for zone 'webmedianow.com': not
authoritative



-------------------------------------------------------------------------


> It's a non-authoritative answer because the nameserver is having
> trouble locating the file.
> If you notice, your named.conf is referencing the file
> "/var/named/webmedianow.com.hosts", but your cat (and thus the actual
> filename) is /var/named/webmedianow.com.
> Fix the filename issue, and named shouldn't have any problem returning
> authoritative answers. You could also have seen errors indicating this
> in the logfiles on the master server.
> For future reference - pretty much anytime you get a non-authoritative
> answer from a master - it means that there was some problem loading the
> zone ON THE MASTER server. From there, logfiles and double and
> triple-checking recent changes are a good thing.
> -Drew Schatt
> On Oct 24, 2004, at 11:03 PM, Karl J Rink wrote:
>
>> zone "webmedianow.com" {
>> type master;
>> file "/var/named/webmedianow.com.hosts";
>> allow-update { none; };
>> allow-query { any; };
>> };
>>
>> cat /var/named/webmedianow.com

>
>



MailKey: GUINNESS