refresh: non-authoritative answer from master
Karl J Rink
karl at webmedianow.com
Wed Oct 27 14:23:30 UTC 2004
Yup. You were on the money. It was a typo in the named.conf of the slave
server.
slave ------
> zone "webmedianow.com.hosts" IN {
> file "webmedianow.com.hosts.bak";
> type slave;
> masters { 216.55.144.16; };
> };
should look like this:
zone "webmedianow.com" IN {
type slave;
masters { 216.55.144.16; };
file "webmedianow.com.hosts";
};
And, just to note; this entry was autogenerated by a GUI front end. I'll
never trust a GUI again.
> changed:
> $TTL 0 --> $TTL 38400
> serial 2002009059 --> 2002009060
>
> ns1 (master) log:
> -------------------------------------------------------------------------
> Oct 25 12:13:32 apollo named: named shutdown succeeded
> Oct 25 12:13:34 apollo named[11357]: starting BIND 9.2.1 -u named
> Oct 25 12:13:34 apollo named[11357]: using 1 CPU
> Oct 25 12:13:34 apollo named[11360]: loading configuration from
> '/etc/named.con f'
> Oct 25 12:13:34 apollo named[11360]: no IPv6 interfaces found
> Oct 25 12:13:34 apollo named[11360]: listening on IPv4 interface lo,
> 127.0.0.1# 53
> Oct 25 12:13:34 apollo named[11360]: listening on IPv4 interface eth0,
> 216.55.1 44.16#53
> Oct 25 12:13:34 apollo named[11360]: command channel listening on
> 127.0.0.1#953
> Oct 25 12:13:34 apollo named[11360]: zone 0.0.127.in-addr.arpa/IN: loaded
> seria l 1997022701
> Oct 25 12:13:34 apollo named[11360]: zone 144.55.216.in-addr.arpa/IN:
> loaded se rial 2004021516
> Oct 25 12:13:34 apollo named[11360]: zone webmedianow.com/IN: loaded
> serial 200 2009060
> Oct 25 12:13:34 apollo named[11360]: zone localhost/IN: loaded serial 42
> Oct 25 12:13:34 apollo named[11360]: running
> Oct 25 12:13:34 apollo named[11360]: zone 144.55.216.in-addr.arpa/IN:
> sending n otifies (serial 2004021516)
> Oct 25 12:13:34 apollo named[11360]: zone webmedianow.com/IN: sending
> notifies (serial 2002009060)
> Oct 25 12:13:34 apollo named: named startup succeeded
>
>
> --------------------------------------------------------------------------
> ns2 (slave) log:
> Oct 25 11:58:36.187 flush_deletions: 17 nodes of 1556 in tree
> Oct 25 11:58:36.187 end cache cleaning, mem inuse 158371
> Oct 25 12:09:29.423 createfetch: 94.167.185.66.in-addr.arpa PTR
> Oct 25 12:14:32.051 received notify for zone 'webmedianow.com': not
> authoritative
>
> --------------------------------------------------------------------------
> let's see if i can cut'n'past this correctly:
> [root at apollo named]# cat /var/named/webmedianow.com.hosts
> $ORIGIN .
> $TTL 38400
> webmedianow.com IN SOA ns1.webmedianow.com. root.webmedianow.com. (
> 2002009060 ; serial
> 10800 ; refresh
> 3600 ; retry
> 432000 ; expire
> 38400 ; default_ttl
> )
> webmedianow.com. IN NS ns1.webmedianow.com.
> IN NS ns2.webmedianow.com.
> IN MX 10 mail.webmedianow.com.
>
> $ORIGIN webmedianow.com.
> @ IN A 216.55.144.16
> ns IN A 216.55.144.16
> ns1 IN A 216.55.144.16
> ns2 IN A 216.55.144.33
> mail IN A 216.55.144.16
> mailhost IN A 216.55.144.16
> pop IN A 216.55.144.16
> smtp IN A 216.55.144.16
> apollo IN A 216.55.144.16
> www IN A 216.55.144.16
> ssh IN A 216.55.144.16
> sftp IN A 216.55.144.16
> ftp IN A 216.55.144.16
> gemman IN A 64.25.130.142
> webrink IN A 68.101.147.136
> home IN A 70.179.25.47
> magnia IN A 68.111.231.9
> radio IN A 68.111.231.9
> ils IN A 213.193.144.104
> irc 0 IN A 64.62.96.42
> 0 IN A 64.235.225.250
> 0 IN A 64.237.38.100
> 0 IN A 194.134.5.82
> 0 IN A 199.184.165.133
> 0 IN A 205.188.149.12
> 0 IN A 209.221.59.11
> 0 IN A 216.152.77.10
> teaser IN A 216.55.144.33
> ircdoor IN A 217.160.246.244
>
>
> [root at apollo named]#
> --------------------------------------------------------------------------
>
> You know... I'm reading this bind book "O'Reilly DNS & BIND Cookbook" and
> it talks about Registering a Domain Name Section 1.5, and Registering Name
> Servers Section 1.6; and that the registrar is responsible for top level
> delegation for zone data.
>
> I did change my ns primary host name and ip via the networksolutions web
> interface... Under the 'host management' section. Perhaps I need to wait
> 48 hours for this to propogate? The site mentioned 24-48 hours.
>
> Yet, when i do a whois webmedianow.com, it returns properly:
>
> NS1.WEBMEDIANOW.COM 216.55.144.16
> NS2.WEBMEDIANOW.COM 216.55.144.33
>
> and it used to be:
>
> NS.WEBMEDIANOW.COM 216.55.144.16
> NS2.WEBMEDIANOW.COM 213.11.111.252
>
>
> Hmmm. other wise, I still do not know how to make 216.55.144.16
> "ns1.webmedianow.com" an authoritative name server.
>
> --Karl
>
> -------------------------------------------------------------------
> other configs, just for kicks:
>
> [root at apollo named]# cat /etc/named.conf
> // master named.conf
>
> options {
> directory "/var/named";
> zone-statistics yes;
> notify yes;
> allow-transfer { 216.55.144.16; 216.55.144.33; };
> also-notify { 216.55.144.16; 216.55.144.33; };
> };
>
> controls {
> inet 127.0.0.1 allow { localhost; } keys { rndckey; };
> };
>
> zone "." IN {
> type hint;
> file "named.ca";
> };
>
> zone "localhost" IN {
> type master;
> file "localhost.zone";
> allow-update { none; };
> };
>
> zone "0.0.127.in-addr.arpa" IN {
> type master;
> file "named.local";
> allow-update { none; };
> };
>
> zone "144.55.216.in-addr.arpa" IN {
> type master;
> file "/var/named/144.55.216.in-addr.arpa";
> allow-update { none; };
> };
>
> include "/etc/rndc.key";
>
> //logging {
> // channel _default_log {
> // file "/var/log/named.log";
> // severity debug;
> // print-time yes;
> // };
> // category default {
> // _default_log;
> // };
> //};
> /////////////////////////////////////////////////////////////
>
> zone "webmedianow.com" {
> type master;
> file "/var/named/webmedianow.com.hosts";
> allow-update { none; };
> allow-query { any; };
> };
>
>
> [teaser:~] root# cat /etc/named.conf
> // slave named.conf
>
> controls {
> inet 127.0.0.1 allow { localhost; } keys { rndckey; };
> };
>
> options {
> directory "/var/named";
> zone-statistics yes;
> notify yes;
> allow-transfer { 216.55.144.16; 216.55.144.33; };
> };
>
> zone "." IN {
> type hint;
> file "named.ca";
> };
>
> zone "localhost" IN {
> type master;
> file "localhost.zone";
> allow-update { none; };
> };
>
> zone "0.0.127.in-addr.arpa" IN {
> type master;
> file "named.local";
> allow-update { none; };
> };
>
> zone "144.55.216.in-addr.arpa" IN {
> type master;
> file "144.55.216.in-addr.arpa";
> allow-update { none; };
> };
>
> zone "webmedianow.com.hosts" IN {
> file "webmedianow.com.hosts.bak";
> type slave;
> masters { 216.55.144.16; };
> };
>
> include "/etc/rndc.key";
> logging {
> channel _default_log {
> file "/Library/Logs/named.log";
> severity debug;
> print-time yes;
> };
> category default {
> _default_log;
> };
>
> };
> [teaser:~] root#
>
>
>
>> Try changing the $TTL 0 at the top of the file to: $TTL 38400
>> Then, reload the file and tell me what you get.
>> -Drew
>> On Oct 25, 2004, at 9:03 AM, Karl J Rink wrote:
>>
>>> So, how do I make this go away:
>>>
>>> "Oct 25 08:57:37.683 lame server resolving 'webmedianow.com' (in
>>> 'webmedianow.com'?): 216.55.144.33#53"
>>>
>>> --------------------------------------------------------------------
>>>> 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
>>>>
>>>
>>>
>>> MailKey: GUINNESS
>>
>
>
> MailKey: GUINNESS
>
MailKey: GUINNESS
More information about the bind-users
mailing list