is my router a slave?

[Gerry Reno]

Mark Andrews wrote:
>> I am seeing this in the log:
>>
>> Apr  8 19:54:38 grp-01-30-50 named[8947]: client 192.168.1.1#53: view 
>> internal: received notify for zone '189.91.72.in-addr.arpa': not 
>> authoritative
>> Apr  8 19:54:38 grp-01-30-50 named[8947]: client 192.168.1.1#53: view 
>> internal: received notify for zone 'example.com'
>>
>> 192.168.1.1 is the IP of my internet router.  It's also the DHCP server 
>> for the network.  Would it also response to notifies?
>>     
>
> 	If you want help post the real log messages, addresses etc.
>
> 	Mark
> 	
>   
>> Gerry
>>     
I just saw this.  Mark, I only changed the domain.  I wasn't sure it was 
safe to post real information.
I've got things running internally very well for the most part.  But I 
still have a few questions about
these types of things that I notice in the logs.  Next week I'll tell my 
ISP I'm running my own nameservers
and see if they will delegate DNS to me.

192.168.1.1 is my router.
===============================================

Apr  8 19:54:38 grp-01-30-50 named[8947]: client 192.168.1.1#53: view 
internal: received notify for zone '189.91.72.in-addr.arpa': not 
authoritative
Apr  8 19:54:38 grp-01-30-50 named[8947]: client 192.168.1.1#53: view 
internal: received notify for zone 'gerryrenoproperties.com'

===============================================



Also, what about this? 
68.238.96.12 and 68.238.112.12 are my ISP nameservers.
===============================================
Apr 11 04:46:54 grp-01-30-50 named[20116]: client 192.168.2.102#57279: 
view internal: query: 37.235.28.193.in-addr.arpa IN PTR +
Apr 11 04:47:00 grp-01-30-50 named[20116]: unexpected RCODE (SERVFAIL) 
resolving '37.235.28.193.in-addr.arpa/PTR/IN': 68.238.96.12#53
Apr 11 04:47:00 grp-01-30-50 named[20116]: unexpected RCODE (SERVFAIL) 
resolving '37.235.28.193.in-addr.arpa/PTR/IN': 68.238.112.12#53
Apr 11 04:47:07 grp-01-30-50 named[20116]: client 192.168.2.102#57281: 
view internal: query: 37.235.28.193.in-addr.arpa IN PTR +
Apr 11 04:47:09 grp-01-30-50 named[20116]: unexpected RCODE (SERVFAIL) 
resolving 'cygnus.starnode.net/AAAA/IN': 62.4.16.80#53
Apr 11 04:47:09 grp-01-30-50 named[20116]: unexpected RCODE (SERVFAIL) 
resolving 'cygnus.starnode.net/AAAA/IN': 68.238.112.12#53
Apr 11 04:47:11 grp-01-30-50 named[20116]: unexpected RCODE (SERVFAIL) 
resolving 'cygnus.starnode.net/AAAA/IN': 68.238.96.12#53
Apr 11 04:47:19 grp-01-30-50 named[20116]: unexpected RCODE (SERVFAIL) 
resolving 'cygnus.starnode.net/AAAA/IN': 68.238.96.12#53
Apr 11 04:47:30 grp-01-30-50 named[20116]: unexpected RCODE (SERVFAIL) 
resolving 'cygnus.starnode.net/AAAA/IN': 68.238.112.12#53
Apr 11 04:47:30 grp-01-30-50 named[20116]: unexpected RCODE (SERVFAIL) 
resolving 'cygnus.starnode.net/AAAA/IN': 62.4.16.80#53
===============================================



And one last one:

I've haven't been about to get reverse dns working for 127.0.0.1.
===============================================
[root at grp-01-30-50 named]# nslookup localhost
Server:         127.0.0.1
Address:        127.0.0.1#53

Non-authoritative answer:
Name:   localhost
Address: 127.0.0.1

[root at grp-01-30-50 named]# nslookup 127.0.0.1
Server:         127.0.0.1
Address:        127.0.0.1#53

** server can't find 1.0.0.127.in-addr.arpa.: NXDOMAIN
===============================================



What I have is a 0.0.127.in-addr.arpa. zone with '1' defined:
===============================================
$TTL    86400
@       IN      SOA     localhost. root.localhost.  (
                                      42         ; Serial
                                      28800      ; Refresh
                                      14400      ; Retry
                                      3600000    ; Expire
                                      86400 )    ; Minimum
        IN      NS      localhost.
1       IN      PTR     localhost.
===============================================


in named.conf:
===============================================
zone "0.0.127.in-addr.arpa." IN {
        type master;
        file "named.local";
        allow-update { none; };
};
===============================================


but the rdns doesn't seem to use it.


Thanks,
Gerry