Hello Guys,
i have some strange situation here on solaris 10 with version 9.9.3-P2 after
upgrade from 9.9.2.
Sometimes i just become a servfail for the same request. (after restart
- because of cache)
is just do a `dig @127.0.0.1 test.com`
here is a snoop output what i capture on that inter
named error report
named.service - Berkeley Internet Name Domain (DNS) Loaded: loaded
(/usr/lib/systemd/system/named.service; enabled) Active: failed (Result:
exit-code) since Wed, 11 Sep 2013 20:17:05 +0100; 13min ago Process: 1660
ExecStart=/usr/sbin/named -u named $OPTIONS (code=exited, sta
There is a lot of information missing here. I'm sure someone could help you but
I'm not sure this is the correct list for that as I assume BIND, is not the
cause of your errors.
--
Jason Hellenthal
Inbox: jhellent...@dataix.net
Voice: +1 (616) 953-0176
JJH48-ARIN
On Sep 17, 2013, at 11:00
To add to Len's comments, bind will keep going to the partially broken Fedora
dns as long as it has the fastest response time.
As a short term fix, you can use the 'blackhole' option to prevent your dns
from sending queries to that IP.
John Manson
U.S. House of Representatives | HIR Data Communi
When I upgraded bind I had trouble writing /var/log too.
I moved the bind output logs down one level, /var/log/named-logs/
updating my config and allowing write access to the bind user for
the new directory.
I think I had trouble with the pid file, but I think I resolved
that by removing the one
5 matches
Mail list logo