* [gentoo-user] SERVFAIL with bind; problems in named.conf?
@ 2011-10-05 9:06 Andrey Moshbear
2011-10-05 13:27 ` Alan McKinnon
0 siblings, 1 reply; 7+ messages in thread
From: Andrey Moshbear @ 2011-10-05 9:06 UTC (permalink / raw
To: gentoo-user
For bind, I have the following as named.conf:
acl "xfer" { none; };
acl "trusted" { 127.0.0.0/8; ::1/128; };
options {
directory "/var/bind";
pid-file "/var/run/named/named.pid";
listen-on-v6 { none; };
listen-on port 53 { 127.0.0.1; 192.168.1.0/10; EXTERNAL_IP; };
};
include "/etc/bind/rndc.key";
controls { inet 127.0.0.1 port 953 allow { 127.0.0.1/32; ::1/128; }
keys { "rndc-key"; }; };
zone "." in { type hint; file "/var/bind/root.cache"; };
zone "localhost" IN { type master; file "pri/localhost.zone"; notify no; };
zone "127.in-addr.arpa" IN { type master; file "pri/127.zone"; notify no; };
zone "moshbear.net" IN { type master; file
"/var/bind/pri/moshbear.net.zone"; allow-query { any; };
allow-transfer { xfer; }; };
// end of dump
The zone file does not have any errors.
Any reasons as to why "dig @127.0.0.1 moshbear.net" returns SERVFAIL?
--
001100 Andrey "m05hbear" Vul
010010
100001 andrey dot vul at gmail
110011
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: [gentoo-user] SERVFAIL with bind; problems in named.conf?
2011-10-05 9:06 [gentoo-user] SERVFAIL with bind; problems in named.conf? Andrey Moshbear
@ 2011-10-05 13:27 ` Alan McKinnon
2011-10-05 13:38 ` [gentoo-user] " Andrey Moshbear
0 siblings, 1 reply; 7+ messages in thread
From: Alan McKinnon @ 2011-10-05 13:27 UTC (permalink / raw
To: gentoo-user
On Wed, 5 Oct 2011 05:06:27 -0400
Andrey Moshbear <andrey.vul@gmail.com> wrote:
> For bind, I have the following as named.conf:
>
> acl "xfer" { none; };
>
> acl "trusted" { 127.0.0.0/8; ::1/128; };
>
> options {
> directory "/var/bind";
> pid-file "/var/run/named/named.pid";
>
> listen-on-v6 { none; };
> listen-on port 53 { 127.0.0.1; 192.168.1.0/10; EXTERNAL_IP; };
> };
>
> include "/etc/bind/rndc.key";
> controls { inet 127.0.0.1 port 953 allow { 127.0.0.1/32; ::1/128; }
> keys { "rndc-key"; }; };
>
> zone "." in { type hint; file "/var/bind/root.cache"; };
>
> zone "localhost" IN { type master; file "pri/localhost.zone"; notify
> no; };
>
> zone "127.in-addr.arpa" IN { type master; file "pri/127.zone"; notify
> no; };
>
> zone "moshbear.net" IN { type master; file
> "/var/bind/pri/moshbear.net.zone"; allow-query { any; };
> allow-transfer { xfer; }; };
> // end of dump
>
> The zone file does not have any errors.
>
> Any reasons as to why "dig @127.0.0.1 moshbear.net" returns SERVFAIL?
What result does bind write to log files when it loads that zone?
SERVFAIL usually indicates something wrong with the zone and bind
refuses to load it.
>
> --
> 001100 Andrey "m05hbear" Vul
> 010010
> 100001 andrey dot vul at gmail
> 110011
>
--
Alan McKinnnon
alan.mckinnon@gmail.com
^ permalink raw reply [flat|nested] 7+ messages in thread* [gentoo-user] Re: SERVFAIL with bind; problems in named.conf?
2011-10-05 13:27 ` Alan McKinnon
@ 2011-10-05 13:38 ` Andrey Moshbear
2011-10-05 13:45 ` Alan McKinnon
0 siblings, 1 reply; 7+ messages in thread
From: Andrey Moshbear @ 2011-10-05 13:38 UTC (permalink / raw
To: gentoo-user
No clue, as logging isn't yet enabled. However, chechzone says that all is fine.
On 2011-10-05, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
> On Wed, 5 Oct 2011 05:06:27 -0400
> Andrey Moshbear <andrey.vul@gmail.com> wrote:
>
>> For bind, I have the following as named.conf:
>>
>> acl "xfer" { none; };
>>
>> acl "trusted" { 127.0.0.0/8; ::1/128; };
>>
>> options {
>> directory "/var/bind";
>> pid-file "/var/run/named/named.pid";
>>
>> listen-on-v6 { none; };
>> listen-on port 53 { 127.0.0.1; 192.168.1.0/10; EXTERNAL_IP; };
>> };
>>
>> include "/etc/bind/rndc.key";
>> controls { inet 127.0.0.1 port 953 allow { 127.0.0.1/32; ::1/128; }
>> keys { "rndc-key"; }; };
>>
>> zone "." in { type hint; file "/var/bind/root.cache"; };
>>
>> zone "localhost" IN { type master; file "pri/localhost.zone"; notify
>> no; };
>>
>> zone "127.in-addr.arpa" IN { type master; file "pri/127.zone"; notify
>> no; };
>>
>> zone "moshbear.net" IN { type master; file
>> "/var/bind/pri/moshbear.net.zone"; allow-query { any; };
>> allow-transfer { xfer; }; };
>> // end of dump
>>
>> The zone file does not have any errors.
>>
>> Any reasons as to why "dig @127.0.0.1 moshbear.net" returns SERVFAIL?
>
> What result does bind write to log files when it loads that zone?
>
> SERVFAIL usually indicates something wrong with the zone and bind
> refuses to load it.
>
>
>
>
>>
>> --
>> 001100 Andrey "m05hbear" Vul
>> 010010
>> 100001 andrey dot vul at gmail
>> 110011
>>
>
>
>
> --
> Alan McKinnnon
> alan.mckinnon@gmail.com
>
>
--
Sent from my mobile device
001100 Andrey "m05hbear" Vul
010010
011110 andrey at moshbear dot net
100001 andrey dot vul at gmail
101101 4163039923
110011
Today's quote:
[ ] Obsolete code offends me.
[ ] Be aware of [ ] Murphy's, [ ] Muphry's Law.
[ ] Use [ ] Occam's, [ ] Hanlon's razor.
[ ] Greenspun's Tenth Rule.
[ ] Sturgeon's Law, [ ] Pareto principle.
[ ] RTFM, [ ] RTF[__]
[ ] [___]
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: [gentoo-user] Re: SERVFAIL with bind; problems in named.conf?
2011-10-05 13:38 ` [gentoo-user] " Andrey Moshbear
@ 2011-10-05 13:45 ` Alan McKinnon
2011-10-05 17:29 ` Andrey Moshbear
0 siblings, 1 reply; 7+ messages in thread
From: Alan McKinnon @ 2011-10-05 13:45 UTC (permalink / raw
To: gentoo-user
On Wed, 5 Oct 2011 09:38:01 -0400
Andrey Moshbear <andrey.vul@gmail.com> wrote:
> No clue, as logging isn't yet enabled. However, chechzone says that
> all is fine.
Well that's your primary error right there. How can you run a daemon
that isn't logging and consider that even halfway proper? Get some real
logs from when bind loads the zone and I'll bet it'll tell you right
away what the problem is
checkzone != a full bind
>
> On 2011-10-05, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
> > On Wed, 5 Oct 2011 05:06:27 -0400
> > Andrey Moshbear <andrey.vul@gmail.com> wrote:
> >
> >> For bind, I have the following as named.conf:
> >>
> >> acl "xfer" { none; };
> >>
> >> acl "trusted" { 127.0.0.0/8; ::1/128; };
> >>
> >> options {
> >> directory "/var/bind";
> >> pid-file "/var/run/named/named.pid";
> >>
> >> listen-on-v6 { none; };
> >> listen-on port 53 { 127.0.0.1; 192.168.1.0/10;
> >> EXTERNAL_IP; }; };
> >>
> >> include "/etc/bind/rndc.key";
> >> controls { inet 127.0.0.1 port 953 allow { 127.0.0.1/32; ::1/128; }
> >> keys { "rndc-key"; }; };
> >>
> >> zone "." in { type hint; file "/var/bind/root.cache"; };
> >>
> >> zone "localhost" IN { type master; file "pri/localhost.zone";
> >> notify no; };
> >>
> >> zone "127.in-addr.arpa" IN { type master; file "pri/127.zone";
> >> notify no; };
> >>
> >> zone "moshbear.net" IN { type master; file
> >> "/var/bind/pri/moshbear.net.zone"; allow-query { any; };
> >> allow-transfer { xfer; }; };
> >> // end of dump
> >>
> >> The zone file does not have any errors.
> >>
> >> Any reasons as to why "dig @127.0.0.1 moshbear.net" returns
> >> SERVFAIL?
> >
> > What result does bind write to log files when it loads that zone?
> >
> > SERVFAIL usually indicates something wrong with the zone and bind
> > refuses to load it.
> >
> >
> >
> >
> >>
> >> --
> >> 001100 Andrey "m05hbear" Vul
> >> 010010
> >> 100001 andrey dot vul at gmail
> >> 110011
> >>
> >
> >
> >
> > --
> > Alan McKinnnon
> > alan.mckinnon@gmail.com
> >
> >
>
--
Alan McKinnnon
alan.mckinnon@gmail.com
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2011-10-05 22:27 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-10-05 9:06 [gentoo-user] SERVFAIL with bind; problems in named.conf? Andrey Moshbear
2011-10-05 13:27 ` Alan McKinnon
2011-10-05 13:38 ` [gentoo-user] " Andrey Moshbear
2011-10-05 13:45 ` Alan McKinnon
2011-10-05 17:29 ` Andrey Moshbear
2011-10-05 19:27 ` Alan McKinnon
2011-10-05 22:25 ` Andrey Moshbear
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox