lame server showing up in logs constantly and name server eventually hangs
Pete Ehlke
pde at ehlke.net
Wed Feb 19 21:42:55 UTC 2003
On Wed, Feb 19, 2003 at 09:22:27AM -0800, Ali Eghtessadi wrote:
>
> I appreciate any help I can get with this issue. Here is a copy of my
> /etc/named.conf
No, this is not a copy of your named.conf. You've obscured the only data
that could allow anyone to help you. Post the entire contents of your
file, including the contents of files you're including. If you've
mistakenly set up one of your servers as authoritative for more of
in-addr.arpa than you think you have, that might produce the symptoms
you describe, but we can't figure that bit out from the munged data that
you posted.
-P.
> # more /etc/named.conf
> options {
> directory "/var/named";
> query-source address * port 53;
> allow-transfer { none; };
> };
>
> logging {
> channel chatty { syslog daemon; severity debug; };
> category config { chatty; };
> category default { chatty; };
> category general { chatty; };
> };
>
> # controls for rndc
> controls {
> inet 127.0.0.1 allow { 127.0.0.1; } keys { "rndckey"; };
> };
>
> acl sprint-servers { 144.228.254.10; 206.228.179.10; 144.228.255.10; };
>
> acl babcockbrown-servers { a.b.c.d; a.b.c.e; };
> #
> # Secure key defenitions file
> #
> include "/etc/rndc.key";
>
> #
> # Zone Files
> #
> include "/var/named/named.conf.active-zones";
> #
> include "/var/named/named.conf.reserved-zones";
> #
> # PTR records for a.b.c
> #
> zone "a.b.c.in-addr.arpa" in {
> type master;
> file "master-active/a.b.c";
> allow-query { any; };
> };
>
>
> # Local Loopback
> zone "0.0.127.in-addr.arpa" in {
> type master;
> file "master-active/127.0.0";
> allow-query { any; };
> };
>
> zone "." in {
> type hint;
> file "named.ca";
> };
> #
>
>
>
>
>
More information about the bind-users
mailing list