Re: named error from /var/named/etc/root.hint
On 2013-01-15, Jamie Paul Griffin ja...@kode5.net wrote: * Stuart Henderson s...@spacehopper.org [2013-01-14 10:54:30 +]: On 2013-01-14, Jamie Paul Griffin ja...@kode5.net wrote: Hi I recently upgraded my system to the Dec 21 snapshot, will be updating again to the Jan 09 snapshot; but, I noticed an error message in /var/log/messages yesterday when I rebooted my machine: Jan 13 21:16:43 kontrol named[23666]: checkhints: d.root-servers.net/A (199.7.91.13) missing from hints Jan 13 21:16:43 kontrol named[23666]: checkhints: d.root-servers.net/A (128.8.10.90) extra record in hints I managed to fix it by downloading a new file from ftp://ftp.internic.net/domain/named.cache and copying it to /var/named/etc/root.hints. I Just thought I would post that in case anyone else has/had the same issue. Cheers, Jamie This would get updated when you run sysmerge against newer sources or a newer etc52.tgz. I did run sysmerge(8) after the upgrade as documented. It must have been something I did wrong then. Sorry for that. Dec 21 would have been too early for that; d.root didn't change address until after then. So you are fixed anyway by downloading from internic, and other people updating and running sysmerge now will also be fixed.
Re: named error from /var/named/etc/root.hint
On Jan 3, D.ROOT changed its ip address. We updated our sources on and after the 3rd. On 2013 Jan 14 (Mon) at 09:32:57 + (+), Jamie Paul Griffin wrote: :Hi : :I recently upgraded my system to the Dec 21 snapshot, will be updating again to the Jan 09 snapshot; but, I noticed an error message in /var/log/messages yesterday when I rebooted my machine: : : :Jan 13 21:16:43 kontrol named[23666]: checkhints: d.root-servers.net/A (199.7.91.13) missing from hints :Jan 13 21:16:43 kontrol named[23666]: checkhints: d.root-servers.net/A (128.8.10.90) extra record in hints : :I managed to fix it by downloading a new file from ftp://ftp.internic.net/domain/named.cache and copying it to /var/named/etc/root.hints. : :I Just thought I would post that in case anyone else has/had the same issue. : :Cheers, Jamie : : :-- :Primary Key: 4096R/1D31DC38 2011-12-03 :Key Fingerprint: A4B9 E875 A18C 6E11 F46D B788 BEE6 1251 1D31 DC38 : -- Sex is the poor man's opera. -- G. B. Shaw
named error from /var/named/etc/root.hint
Hi I recently upgraded my system to the Dec 21 snapshot, will be updating again to the Jan 09 snapshot; but, I noticed an error message in /var/log/messages yesterday when I rebooted my machine: Jan 13 21:16:43 kontrol named[23666]: checkhints: d.root-servers.net/A (199.7.91.13) missing from hints Jan 13 21:16:43 kontrol named[23666]: checkhints: d.root-servers.net/A (128.8.10.90) extra record in hints I managed to fix it by downloading a new file from ftp://ftp.internic.net/domain/named.cache and copying it to /var/named/etc/root.hints. I Just thought I would post that in case anyone else has/had the same issue. Cheers, Jamie -- Primary Key: 4096R/1D31DC38 2011-12-03 Key Fingerprint: A4B9 E875 A18C 6E11 F46D B788 BEE6 1251 1D31 DC38
Re: named error from /var/named/etc/root.hint
On Mon, Jan 14, 2013 at 09:32:57AM +, Jamie Paul Griffin wrote: Hi I recently upgraded my system to the Dec 21 snapshot, will be updating again to the Jan 09 snapshot; but, I noticed an error message in /var/log/messages yesterday when I rebooted my machine: Jan 13 21:16:43 kontrol named[23666]: checkhints: d.root-servers.net/A (199.7.91.13) missing from hints Jan 13 21:16:43 kontrol named[23666]: checkhints: d.root-servers.net/A (128.8.10.90) extra record in hints I managed to fix it by downloading a new file from ftp://ftp.internic.net/domain/named.cache and copying it to /var/named/etc/root.hints. I Just thought I would post that in case anyone else has/had the same issue. Cheers, Jamie The hints file was updated 10 days ago within the -current src tree. That is more so a warning than an error and your name server will work fine even without the most up to date hints file. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Re: named error from /var/named/etc/root.hint
On 2013-01-14, Jamie Paul Griffin ja...@kode5.net wrote: Hi I recently upgraded my system to the Dec 21 snapshot, will be updating again to the Jan 09 snapshot; but, I noticed an error message in /var/log/messages yesterday when I rebooted my machine: Jan 13 21:16:43 kontrol named[23666]: checkhints: d.root-servers.net/A (199.7.91.13) missing from hints Jan 13 21:16:43 kontrol named[23666]: checkhints: d.root-servers.net/A (128.8.10.90) extra record in hints I managed to fix it by downloading a new file from ftp://ftp.internic.net/domain/named.cache and copying it to /var/named/etc/root.hints. I Just thought I would post that in case anyone else has/had the same issue. Cheers, Jamie This would get updated when you run sysmerge against newer sources or a newer etc52.tgz.
Re: named error from /var/named/etc/root.hint
* Stuart Henderson s...@spacehopper.org [2013-01-14 10:54:30 +]: On 2013-01-14, Jamie Paul Griffin ja...@kode5.net wrote: Hi I recently upgraded my system to the Dec 21 snapshot, will be updating again to the Jan 09 snapshot; but, I noticed an error message in /var/log/messages yesterday when I rebooted my machine: Jan 13 21:16:43 kontrol named[23666]: checkhints: d.root-servers.net/A (199.7.91.13) missing from hints Jan 13 21:16:43 kontrol named[23666]: checkhints: d.root-servers.net/A (128.8.10.90) extra record in hints I managed to fix it by downloading a new file from ftp://ftp.internic.net/domain/named.cache and copying it to /var/named/etc/root.hints. I Just thought I would post that in case anyone else has/had the same issue. Cheers, Jamie This would get updated when you run sysmerge against newer sources or a newer etc52.tgz. I did run sysmerge(8) after the upgrade as documented. It must have been something I did wrong then. Sorry for that. Jamie -- Primary Key: 4096R/1D31DC38 2011-12-03 Key Fingerprint: A4B9 E875 A18C 6E11 F46D B788 BEE6 1251 1D31 DC38
Re: named error
file master/example-int.com ; Extra space between com and .
named error
Folks,
I'm in the process of configuring named with a split-view, but I'm
having what I consider a minor issue which I haven't quite figured out.
Here's the significant snippet from named.conf:
snip
view internal { // What the home network will see
match-clients { clients; };
zone example.com {
type master;
notify no;
file master/example-int.com ;
allow-query { any; };
};
view external { // What the Internet will see
match-clients { any; };
recursion no;
zone example.com {
type master;
notify no;
file master/example-ext.com;
allow-query { any; };
};
snip
named spews out these lines on start:
snip
named[31676]:zone example.com/IN/internal: loading master file
master/example-int.com : file not found
named[31676]:zone localhost/IN/internal: loaded serial 1
named[31676]:zone example.com/IN/external: loaded serial 0
named[31676]: running
snip
I have tried placing example-ext.com, and example-int.com in separate
directories and modifying named.conf accordingly, but the same file
not found occurs with regards to example-int.com.
What additional configuration setting do I need to change or add to
resolve the error?
TIA,
--
Qv6
Re: named error
Qv6 wrote:
Folks,
I'm in the process of configuring named with a split-view, but I'm
having what I consider a minor issue which I haven't quite figured out.
Here's the significant snippet from named.conf:
snip
view internal { // What the home network will see
match-clients { clients; };
zone example.com {
type master;
notify no;
file master/example-int.com ;
allow-query { any; };
};
};
view external { // What the Internet will see
match-clients { any; };
recursion no;
zone example.com {
type master;
notify no;
file master/example-ext.com;
allow-query { any; };
};
};
... unless you snipped them out because they were in-significant
to the good folks on [EMAIL PROTECTED]
I'm sure you're frustrated, but without knowing how you are
invoking named, having the complete named.conf available
and being able to examine your directory tree, I don't know
what you think the list can do for you.
Ray
Re: named error
On Thursday 25 August 2005 08:22 pm, you wrote:
... unless you snipped them out because they were in-significant
to the good folks on [EMAIL PROTECTED]
I'm sure you're frustrated, but without knowing how you are
invoking named, having the complete named.conf available
and being able to examine your directory tree, I don't know
what you think the list can do for you.
Ray
The directory structure is the default that OpenBSD uses except for the
split zone files under /var/named/master, that is:
/var/named
/dev
/etc
/named.conf
/master
/example-ext.com
/example-int.com
/192.168.2
/slave
/standard
The problem is named cannot find example-int.com, but it can find
example-ext.com.
Here's the complete named.conf:
// ACL statement
acl clients {
localnets;
# ::1;
};
options {
version ; // remove this to allow version queries
listen-on{ any; };
// listen-on-v6 { any; };
// allow-recursion { clients; };
allow-query { clients; };
forward only
forwarders { a.b.c.d; s.t.u.v; };
};
logging {
category lame-servers { null; };
};
include /etc/rndc.key;
view internal { // What the home network will see
match-clients { clients; };
zone . IN {
type hint;
file standard/root.hint;
};
zone localhost IN {
type master;
file standard/localhost;
allow-update { none; };
allow-transfer { localhost; };
};
zone 127.in-addr.arpa IN {
type master;
file standard/loopback;
allow-update { none; };
allow-transfer { localhost; };
};
// IPv6 Support
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 standard/loopback6.arpa;
allow-update { none; };
allow-transfer { localhost; };
};
zone 2.168.192.in-addr.arpa IN {
type master;
file master/192.168.2;
allow-update { none; };
};
zone example.com {
type master;
notify no;
file master/example-int.com ;
allow-query { any; };
};
};
view external { // What the Internet will see
match-clients { any; };
recursion no;
zone example.com {
type master;
notify no;
file master/example-ext.com;
allow-query { any; };
};
};
