Re: Error when start named
In message <3fc4fa8b99c43e359c0e5e13252339ce.squir...@webmail.aminor.no>, "Eiv ind Olsen" writes: > Rodrigo Faria Tavares wrote: > > > [root@centos ~]# grep 4 /etc/sysconfig/named > > #OPTIONS ="-4" > > Looks like you have commented out that line. Remove the # character there, > if you want to really disable IPv6 in BIND. > > Regards > Eivind Olsen The best solution is to ask your ISP for IPv6 and run it along side IPv4. IPv4 passed its "best before" date a long time ago and is now becoming "stinky" as ISP's are are starting to be forced into using CGNs. Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Error when start named
Rodrigo Faria Tavares wrote: > [root@centos ~]# grep 4 /etc/sysconfig/named > #OPTIONS ="-4" Looks like you have commented out that line. Remove the # character there, if you want to really disable IPv6 in BIND. Regards Eivind Olsen ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Error when start named
In message <1309102729.2191.9.camel@rodrigo-Calistoga-ICH7M-Chipset>, Rodrigo F aria Tavares writes: > Hello, > > After copy the zone files for chroot, e change the pemissions > in /var/named, now my dns zones is ready, resolving names. > > But come the logs in messages: > > Jun 26 12:35:39 localhost named[4484]: error (network unreachable) > resolving 'ns.isc.afilias-nst.info//IN': 2001:500:a::79#53 > Jun 26 12:35:39 localhost named[4484]: error (network unreachable) > resolving 'pdns3.ultradns.org/A/IN': 2001:500:48::1#53 > Jun 26 12:35:39 localhost named[4484]: error (network unreachable) > resolving 'pdns3.ultradns.org//IN': 2001:500:c::1#53 > Jun 26 12:35:39 localhost named[4484]: error (network unreachable) > resolving 'pdns4.ultradns.org/A/IN': 2001:500:b::1#53 > Jun 26 12:35:39 localhost named[4484]: error (network unreachable) > resolving 'pdns4.ultradns.org//IN': 2001:500:e::1#53 > Jun 26 12:35:39 localhost named[4484]: error (network unreachable) > resolving 'pdns5.ultradns.info/A/IN': 2001:500:19::1#53 > Jun 26 12:35:39 localhost named[4484]: error (network unreachable) > resolving 'pdns3.ultradns.org/A/IN': 2001:500:e::1#53 > Jun 26 12:35:39 localhost named[4484]: error (network unreachable) > resolving 'pdns4.ultradns.org/A/IN': 2001:500:e::1#53 > Jun 26 12:35:39 localhost named[4484]: error (network unreachable) > resolving 'pdns4.ultradns.org//IN': 2001:500:b::1#53 > Jun 26 12:35:39 localhost named[4484]: error (network unreachable) > resolving 'pdns3.ultradns.org/A/IN': 2001:500:b::1#53 > Jun 26 12:35:39 localhost named[4484]: error (network unreachable) > resolving 'pdns3.ultradns.org/A/IN': 2001:500:c::1#53 > Jun 26 12:35:39 localhost named[4484]: error (network unreachable) > resolving 'pdns4.ultradns.org/A/IN': 2001:500:40::1#53 > Jun 26 12:35:39 localhost named[4484]: error (network unreachable) > resolving 'pdns4.ultradns.org//IN': 2001:500:40::1#53 > Jun 26 12:35:39 localhost named[4484]: error (network unreachable) > resolving 'pdns4.ultradns.org/A/IN': 2001:500:f::1#53 > Jun 26 12:35:39 localhost named[4484]: dynamic/managed-keys.bind.jnl: > create: file not found > Jun 26 12:35:39 localhost named[4484]: zone managed-keys.bind/IN/_meta: > keyfetch_done:dns_journal_open -> unexpected error Not a issue on first boot of a new system as you don't have any managed keys yet on disk yet. If it continues then it is a issue. > Jun 26 12:35:39 localhost named[4484]: error (network unreachable) > resolving 'pdns6.ultradns.co.uk//IN': 2001:630:181:35::83#53 > Jun 26 12:35:40 localhost named[4484]: error (network unreachable) > resolving 'dlv.isc.org/DLV/IN': 2001:4f8:0:2::20#53 > Jun 26 12:36:03 localhost named[4484]: dumping master file: > dynamic/tmp-uROOS8s7nk: open: file not found It looks like you are missing the directory "dynamic". Named tried to create the file dynamic/tmp-uROOS8s7nk to write the master file to and the operating system reported that a file in the path didn't exist. > What mean this lines ? > My DNS is running dnssec ? Yes. You can test by running "dig +dnssec soa ." and looking for the "ad" flag. e.g. ; <<>> DiG 9.6.0-APPLE-P2 <<>> +dnssec soa . ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 14004 ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 2, AUTHORITY: 14, ADDITIONAL: 3 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags: do; udp: 4096 ;; QUESTION SECTION: ;. IN SOA ;; ANSWER SECTION: . 86400 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2011062601 1800 900 604800 86400 . 86400 IN RRSIG SOA 8 0 86400 2011070300 2011062523 34525 . KIvth8kB1r6FD4h/P0eKAJh7wpwB4U59lUDcoewQjxEuSXzFQKpgV0Ng gzSTd8cla2jyngm6+fYYZkCQhxn9ES54Yy2KhTafPwv94C/CIHiMHnB/ fCUiWlH34hfZbZ4QGxzKezVbOeIcs06s+ehl5mjkJZ26Whe1BsmXkpR+ uBg= ;; AUTHORITY SECTION: . 264386 IN NS a.root-servers.net. . 264386 IN NS d.root-servers.net. . 264386 IN NS f.root-servers.net. . 264386 IN NS k.root-servers.net. . 264386 IN NS g.root-servers.net. . 264386 IN NS l.root-servers.net. . 264386 IN NS m.root-servers.net. . 264386 IN NS c.root-servers.net. . 264386 IN NS j.root-servers.net. . 264386 IN NS h.root-servers.net. . 264386 IN NS e.root-servers.net. . 264386 IN NS i.root-servers.net. . 264386 IN NS b.root-servers.net. . 516656 IN RRSIG NS 8 0 518400 2011070300 2011062523 34525 . l8vHvUrLoJosx63p0wGkvYxYlYZMoLOQKYkdZ0mC1+Ij8IuYImsHSm/U JVMV8dCLGLqB9Fx0EJIutnAd6RI
Re: Error when start named
Hello,
I add my network listen-on port 53 { 127.0.0.1; 192.168.1.0/24; }; and
too { localhost; 192.168.1.0/24; };
The zones ipv6 are running when i start DNS, try make steps:
In my /etc/named.conf I comment the lines.
(I not need dnssec now)
//listen-on-v6 port 53 { ::1; };
//dnssec-enable yes;
//dnssec-validation yes;
//dnssec-lookaside auto;
//bindkeys-file "/etc/named.iscdlv.key";
//logging {
// channel default_debug {
//file "data/named.run";
//severity dynamic;
//};
//};
In /etc/named.rfc1912.zones I comment the zone ipv6
//zone
"0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa"
IN {
//type master;
// file "/var/named/named.ip6.local";
// allow-update { none; };
//};
[root@centos ~]# grep 4 /etc/sysconfig/named
#OPTIONS ="-4"
root@centos ~]# cat /etc/resolv.conf
search redefariat.com
nameserver 127.0.0.1
nameserver 192.168.1.200
The zone ipv6 is loadded in logs below, my linux server is CentOS
Ipv6 still enabled, but where ? I had commented all lines about ipv6.
Jun 26 18:16:59 centos named[4489]: received control channel command
'reload'
Jun 26 18:16:59 centos named[4489]: loading configuration from
'/etc/named.conf'
Jun 26 18:16:59 centos named[4489]: using default UDP/IPv4 port range:
[1024, 65535]
Jun 26 18:16:59 centos named[4489]: using default UDP/IPv6 port range:
[1024, 65535]
Jun 26 18:16:59 centos named[4489]: reloading configuration succeeded
Jun 26 18:16:59 centos named[4489]: reloading zones succeede
Jun 26 17:54:23 centos named[4489]: adjusted limit on open files from
1024 to 1048576
Jun 26 17:54:23 centos named[4489]: found 1 CPU, using 1 worker thread
Jun 26 17:54:23 centos named[4489]: using up to 4096 sockets
Jun 26 17:54:23 centos named[4489]: loading configuration from
'/etc/named.conf'
Jun 26 17:54:23 centos named[4489]: using default UDP/IPv4 port range:
[1024, 65535]
Jun 26 17:54:23 centos named[4489]: using default UDP/IPv6 port range:
[1024, 65535]
Jun 26 17:54:23 centos named[4489]: listening on IPv4 interface lo,
127.0.0.1#53
Jun 26 17:54:23 centos named[4489]: listening on IPv4 interface eth0,
192.168.1.200#53
Jun 26 17:54:23 centos named[4489]: generating session key for dynamic
DNS
Jun 26 17:54:23 centos named[4489]: automatic empty zone:
127.IN-ADDR.ARPA
Jun 26 17:54:23 centos named[4489]: automatic empty zone:
254.169.IN-ADDR.ARPA
Jun 26 17:54:23 centos named[4489]: automatic empty zone:
2.0.192.IN-ADDR.ARPA
Jun 26 17:54:23 centos named[4489]: automatic empty zone:
255.255.255.255.IN-ADDR.ARPA
Jun 26 17:54:23 centos named[4489]: automatic empty zone:
0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
Jun 26 17:54:23 centos named[4489]: automatic empty zone:
1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
Jun 26 17:54:23 centos named[4489]: automatic empty zone: D.F.IP6.ARPA
Jun 26 17:54:23 centos named[4489]: automatic empty zone: 8.E.F.IP6.ARPA
Jun 26 17:54:23 centos named[4489]: automatic empty zone: 9.E.F.IP6.ARPA
Jun 26 17:54:23 centos named[4489]: automatic empty zone: A.E.F.IP6.ARPA
Jun 26 17:54:23 centos named[4489]: automatic empty zone: B.E.F.IP6.ARPA
Jun 26 17:54:23 centos named[4489]: command channel listening on
127.0.0.1#953
Jun 26 17:54:23 centos named[4489]: command channel listening on ::1#953
Jun 26 17:54:23 centos named[4489]: zone 0.in-addr.arpa/IN: loaded
serial 42
Jun 26 17:54:23 centos named[4489]: zone 0.0.127.in-addr.arpa/IN: loaded
serial 1997022700
Jun 26 17:54:23 centos named[4489]: zone 255.in-addr.arpa/IN: loaded
serial 42
Jun 26 17:54:23 centos named[4489]: zone redefariat.com/IN:
redefariat.com/MX 'mail.redefariat.com.redefariat.com' has no address
records (A or )
Jun 26 17:54:23 centos named[4489]: zone redefariat.com/IN: loaded
serial 2011062522
Jun 26 17:54:23 centos named[4489]: zone localdomain/IN: loaded serial
42
Jun 26 17:54:23 centos named[4489]: zone localhost/IN: loaded serial 42
Jun 26 17:54:23 centos named[4489]: running
Jun 26 17:54:23 centos named[4489]: zone redefariat.com/IN: sending
notifies (serial 2011062522)
Jun 26 17:54:23 centos named[4489]: client 192.168.1.200#37202: received
notify for zone 'redefariat.com'
un 26 18:55:19 centos named[5036]: error (network unreachable) resolving
'mirror.team-cymru.org/A/IN': 2001:503:ba3e::2:30#53
Jun 26 18:55:19 centos named[5036]: error (network unreachable)
resolving 'mirrors.usc.edu/A/IN': 2001:503:c27::2:30#53
Jun 26 18:55:19 centos named[5036]: error (network unreachable)
resolving 'mirrors.usc.edu/A/IN': 2001:7fd::1#53
Jun 26 19:02:58 centos named[5197]: error (network unreachable)
resolving 'www.uol.com.br/A/IN': 2001:500:1::803f:235#53
Jun 26 19:02:58 centos named[5197]: error (network unreachable)
resolving '45.2.221.200.in-addr.arpa/PTR/IN': 2001:dc3::35#53
Jun 26 19:02:58 centos named[5197]: error (ne
Re: Error when start named
On 06/26/2011 05:38 PM, Rodrigo Faria Tavares wrote:
> After copy the zone files for chroot, e change the pemissions
> in /var/named, now my dns zones is ready, resolving names.
> But come the logs in messages:
>
> Jun 26 12:35:39 localhost named[4484]: error (network unreachable)
> resolving 'ns.isc.afilias-nst.info//IN': 2001:500:a::79#53
To me this smells more like a system misconfiguration than a bind
problem.
I'm guessing: you have enabled IPv6 on the system that's running bind,
but you have no IPv6 connectivity to the outside world and no global
v6 address.
> options {
> listen-on port 53 { 127.0.0.1; };
> listen-on-v6 port 53 { ::1; };
If you only listen on the loopback interface (127.0.0.1 and ::1), the only
machine in your network that will be able to use your DNS server will be
the machine on which it's running. I's a bit of a waste going through all
this installation just to accomplish what a single line in /etc/resolv.conf
would have accomplished too.
Second, you should not define the port unless you're forced to. Under normal
circumstances the correct syntax would be listen-on { 127.0.0.1; }; without
the port.
Third, if you don't have (global or local) v6 connectivity on that box, you
should comment out the listen-on-v6 line (or, if you're on a redhattish system,
add OPTIONS=" -4" at the bottom of /etc/sysconfig/named).
> allow-query { localhost; };
Aha, so you really meant to only serve the local machine :)
Z
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
Re: Error when start named
Hello,
After copy the zone files for chroot, e change the pemissions
in /var/named, now my dns zones is ready, resolving names.
But come the logs in messages:
Jun 26 12:35:39 localhost named[4484]: error (network unreachable)
resolving 'ns.isc.afilias-nst.info//IN': 2001:500:a::79#53
Jun 26 12:35:39 localhost named[4484]: error (network unreachable)
resolving 'pdns3.ultradns.org/A/IN': 2001:500:48::1#53
Jun 26 12:35:39 localhost named[4484]: error (network unreachable)
resolving 'pdns3.ultradns.org//IN': 2001:500:c::1#53
Jun 26 12:35:39 localhost named[4484]: error (network unreachable)
resolving 'pdns4.ultradns.org/A/IN': 2001:500:b::1#53
Jun 26 12:35:39 localhost named[4484]: error (network unreachable)
resolving 'pdns4.ultradns.org//IN': 2001:500:e::1#53
Jun 26 12:35:39 localhost named[4484]: error (network unreachable)
resolving 'pdns5.ultradns.info/A/IN': 2001:500:19::1#53
Jun 26 12:35:39 localhost named[4484]: error (network unreachable)
resolving 'pdns3.ultradns.org/A/IN': 2001:500:e::1#53
Jun 26 12:35:39 localhost named[4484]: error (network unreachable)
resolving 'pdns4.ultradns.org/A/IN': 2001:500:e::1#53
Jun 26 12:35:39 localhost named[4484]: error (network unreachable)
resolving 'pdns4.ultradns.org//IN': 2001:500:b::1#53
Jun 26 12:35:39 localhost named[4484]: error (network unreachable)
resolving 'pdns3.ultradns.org/A/IN': 2001:500:b::1#53
Jun 26 12:35:39 localhost named[4484]: error (network unreachable)
resolving 'pdns3.ultradns.org/A/IN': 2001:500:c::1#53
Jun 26 12:35:39 localhost named[4484]: error (network unreachable)
resolving 'pdns4.ultradns.org/A/IN': 2001:500:40::1#53
Jun 26 12:35:39 localhost named[4484]: error (network unreachable)
resolving 'pdns4.ultradns.org//IN': 2001:500:40::1#53
Jun 26 12:35:39 localhost named[4484]: error (network unreachable)
resolving 'pdns4.ultradns.org/A/IN': 2001:500:f::1#53
Jun 26 12:35:39 localhost named[4484]: dynamic/managed-keys.bind.jnl:
create: file not found
Jun 26 12:35:39 localhost named[4484]: zone managed-keys.bind/IN/_meta:
keyfetch_done:dns_journal_open -> unexpected error
Jun 26 12:35:39 localhost named[4484]: error (network unreachable)
resolving 'pdns6.ultradns.co.uk//IN': 2001:630:181:35::83#53
Jun 26 12:35:40 localhost named[4484]: error (network unreachable)
resolving 'dlv.isc.org/DLV/IN': 2001:4f8:0:2::20#53
Jun 26 12:36:03 localhost named[4484]: dumping master file:
dynamic/tmp-uROOS8s7nk: open: file not found
What mean this lines ?
My DNS is running dnssec ?
my named.conf
options {
listen-on port 53 { 127.0.0.1; };
listen-on-v6 port 53 { ::1; };
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
memstatistics-file "/var/named/data/named_mem_stats.txt";
allow-query { localhost; };
recursion yes;
dnssec-enable yes;
dnssec-validation yes;
dnssec-lookaside auto;
/* Path to ISC DLV key */
bindkeys-file "/etc/named.iscdlv.key";
};
[]'s
Rodrigo Faria Tavares
Em Dom, 2011-06-26 às 16:42 +0200, Zenon Panoussis escreveu:
> On 06/26/2011 03:16 PM, Rodrigo Faria Tavares wrote:
>
> > When I tryed to run named, come many messages about bind files not
> > exist. Then i put the path each file in /var/named, in
> > the /etc/named.rfc1912.zones file. After the changes come this message:
> >
> > zone localhost/IN: loading from master file /var/named/localhost.zone
> > failed: invalid file
>
> This and the other files that you mention should exist and be valid
> zone files for the zones they are supposed to serve. Sample localhost.zone:
>
> $TTL 1D
> @ IN SOA @ rname.invalid. (
> 0 ; serial
> 1D ; refresh
> 1H ; retry
> 1W ; expire
> 3H ); minimum
> NS @
> A 127.0.0.1
> ::1
>
>
> > Then I created links for chroot.
>
> Make a copy of the zone files inside the chroot, rather than just linking.
> Also, pay attention to selinux. If it its not properly configured for your
> chroot it will make your life sour and miserable until you just disable it
> and be done with it.
>
> > For each file in /var/named come these logs:
>
> > Error in named configuration:
> > zone localdomain/IN: loading from master
> > file /var/named/localdomain.zone failed: invalid file
>
> To me it looks as if the file is there and bind can read it, but the contents
> of the file are incorrect.
>
> Then again, that's not fatal:
>
> > zone localdomain/IN: not loaded due to errors.
>
> "Zone not loaded" means that your server won't answer queries for this zone,
> but it will still answer queries for any other zones that were correctly
> configured and loaded.
>
> Depending on your distribution, this mi
Re: Error when start named
On 06/26/2011 03:16 PM, Rodrigo Faria Tavares wrote: > When I tryed to run named, come many messages about bind files not > exist. Then i put the path each file in /var/named, in > the /etc/named.rfc1912.zones file. After the changes come this message: > > zone localhost/IN: loading from master file /var/named/localhost.zone > failed: invalid file This and the other files that you mention should exist and be valid zone files for the zones they are supposed to serve. Sample localhost.zone: $TTL 1D @ IN SOA @ rname.invalid. ( 0 ; serial 1D ; refresh 1H ; retry 1W ; expire 3H ); minimum NS @ A 127.0.0.1 ::1 > Then I created links for chroot. Make a copy of the zone files inside the chroot, rather than just linking. Also, pay attention to selinux. If it its not properly configured for your chroot it will make your life sour and miserable until you just disable it and be done with it. > For each file in /var/named come these logs: > Error in named configuration: > zone localdomain/IN: loading from master > file /var/named/localdomain.zone failed: invalid file To me it looks as if the file is there and bind can read it, but the contents of the file are incorrect. Then again, that's not fatal: > zone localdomain/IN: not loaded due to errors. "Zone not loaded" means that your server won't answer queries for this zone, but it will still answer queries for any other zones that were correctly configured and loaded. Depending on your distribution, this might be helpful: http://webhostingneeds.com/Zone_localdomain_IN_loading_master_file_localdomain_zone_file_not_found Z ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Error when start named
Hello,
I commented the lines in my named.conf
/zone "." IN {
// type hint;
// file "/var/named/named.ca";
//};
So the named not come more this error, but bind is not ok.
When I tryed to run named, come many messages about bind files not
exist. Then i put the path each file in /var/named, in
the /etc/named.rfc1912.zones file. After the changes come this message:
zone localhost/IN: loading from master file /var/named/localhost.zone
failed: invalid file
Then I created links for chroot.
[root@localhost named]# ls -las
total 12
4 drwxr-x--- 3 root named 4096 Jun 26 10:06 .
4 drwxr-x--- 6 root named 4096 Jun 26 09:28 ..
4 drwxrwx--- 2 named named 4096 Jun 25 21:46 data
0 lrwxrwxrwx 1 root root25 Jun 26 10:06 localdomain.zone
-> /var/named/localhost.zone
0 lrwxrwxrwx 1 root root25 Jun 26 09:50 localhost.zone
-> /var/named/localhost.zone
0 lrwxrwxrwx 1 root root26 Jun 26 09:54 named.broadcast
-> /var/named/named.broadcast
0 lrwxrwxrwx 1 root root19 Jun 26 09:29 named.ca
-> /var/named/named.ca
0 lrwxrwxrwx 1 root root26 Jun 26 09:54 named.ip6.local
-> /var/named/named.ip6.local
0 lrwxrwxrwx 1 root root22 Jun 26 09:51 named.local
-> /var/named/named.local
0 lrwxrwxrwx 1 root root21 Jun 26 09:52 named.zero
-> /var/named/named.zero
Now I try to run bind again.
For each file in /var/named come these logs:
Error in named configuration:
zone localdomain/IN: loading from master
file /var/named/localdomain.zone failed: invalid file
zone localdomain/IN: not loaded due to errors.
_default/localdomain/IN: invalid file
zone localhost/IN: loading from master file /var/named/localhost.zone
failed: invalid file
zone localhost/IN: not loaded due to errors.
What I can to do ?
[]'s
Rodrigo Faria
Em Dom, 2011-06-26 às 03:52 +0200, Eivind Olsen escreveu:
> Rodrigo Faria Tavares wrote:
>
> > Error in named configuration:
> > /etc/named.rfc1912.zones:10: zone '.': already exists previous
> > definition: /etc/named.conf:35
> > How I can resolve it ?
>
> By fixing your configuration. The error message seems clear enough, so
> check what you have in /etc/named.rfc1912.zones around line 10, and in
> /etc/named.conf around line 35. The error message suggests you have
> defined the root zone "." twice.
>
> Regards
> Eivind Olsen
>
>
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
Crashes
Hello all My recently installed SL6 bind-sdb-9.7.3-2.el6_1.P1.1.x86_64 keeps crashing at irregular intervals likes this: grep -A1 'name.c:2111: REQUIRE' /var/named/chroot/var/log/named.log 25-Jun-2011 22:50:15.762 general: name.c:2111: REQUIRE(suffixlabels > 0) failed 25-Jun-2011 22:50:15.762 general: exiting (due to assertion failure) -- 25-Jun-2011 23:57:14.697 general: name.c:2111: REQUIRE(suffixlabels > 0) failed 25-Jun-2011 23:57:14.697 general: exiting (due to assertion failure) -- 26-Jun-2011 00:31:40.246 general: name.c:2111: REQUIRE(suffixlabels > 0) failed 26-Jun-2011 00:31:40.247 general: exiting (due to assertion failure) -- 26-Jun-2011 01:23:51.683 general: name.c:2111: REQUIRE(suffixlabels > 0) failed 26-Jun-2011 01:23:51.683 general: exiting (due to assertion failure) -- 26-Jun-2011 02:23:45.415 general: name.c:2111: REQUIRE(suffixlabels > 0) failed 26-Jun-2011 02:23:45.415 general: exiting (due to assertion failure) The log line immediately preceeding each name.c:2111 failure always has a time stamp long before the error and is completely unrelated, so this is all I have to go by. The error has been seen by google before, but an explanation or a solution has not. Does anyone have any idea where to start looking and for what? Z ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
