Re: [CentOS] named log entries - Are any of these a problem?

2014-10-10 Thread Bill Gee
Hello everyone - Update on this: I did some more searching and discovered that OpenNIC is intended to replace the normal top-level DNS servers. It's not just a simple forwarder. I changed my forwarders to AlternateDNS. After two days I no longer get either of the checkhints messages shown

Re: [CentOS] named log entries - Are any of these a problem?

2014-10-08 Thread Bill Gee
On Wednesday, October 08, 2014 14:11:59 Always Learning wrote: > On Wed, 2014-10-08 at 08:05 -0500, Bill Gee wrote: > > I run bind version 9.8.2 on CentOS 6.5. The daily logwatch run sends me > > the following items. Are any of these a real problem? > > > >checkhints: unable to find root NS 'ns1.

Re: [CentOS] named log entries - Are any of these a problem?

2014-10-08 Thread Always Learning
On Wed, 2014-10-08 at 14:11 +0100, Always Learning wrote: > Host ns9.opennic.glue not found: 3(NXDOMAIN) > > Seems your set-up is wrong. Seems I do not know what I am writing about. Haven't yet set-up my own Bind. -- Regards, Paul. England, EU. _

Re: [CentOS] named log entries - Are any of these a problem?

2014-10-08 Thread Always Learning
On Wed, 2014-10-08 at 08:05 -0500, Bill Gee wrote: > I run bind version 9.8.2 on CentOS 6.5. The daily logwatch run sends me the > following items. Are any of these a real problem? >checkhints: unable to find root NS 'ns1.opennic.glue' in hints: 170 Time(s) Host ns1.opennic.glue not found:

[CentOS] named log entries - Are any of these a problem?

2014-10-08 Thread Bill Gee
Hello everyone - I run bind version 9.8.2 on CentOS 6.5. The daily logwatch run sends me the following items. Are any of these a real problem? checkhints: extra NS 'A.ROOT-SERVERS.NET' in hints: 170 Time(s) checkhints: extra NS 'B.ROOT-SERVERS.NET' in hints: 170 Time(s)