Downloaded and compiled bind-9.9.7 (FreeBSD 8.4-RELEASE) and it built fine
(./configure && make && make install).
If I try to start named (service named start), it starts this version instead
of the version in /usr/local/sbin
I found this in /etc/defaults/rc,conf:
named_enable="NO"
On Mar 29, 2015, at 18.09, Mark Andrews wrote:
>
> The nameserver needs to be able to resolve the hostname of the
> secondary itself, it does not use the servers listed in resolv.conf.
aha, that was the clue i needed, thanks.
-ben
___
Please visit htt
The nameserver needs to be able to resolve the hostname of the
secondary itself, it does not use the servers listed in resolv.conf.
You may want to open up recursion temporatially to chase down why this
is failing.
In message <6a5102d1-44ef-4728-99a2-8eb063958...@bitrate.net>, b...@bitrate.net
hi-
i'm having a problem where notifies are not sent unless also-notify is used to
explicitly specify hosts.
here is the config from the computer serving the master zone:
>named-checkconf -p
options {
bindkeys-file "/etc/bind/keys/dnssec/bind.keys";
blackhole {
"
Hi,
I have
auto-dnssec maintain; inline-signing yes;
and tried a
$INCLUDE tmx4.lrau.net.tlsa
in my manually maintained zone file.
It seems that everything after the $include is missing in the zone.
The $included file contains one or 2 TLSA RRs with absolute origin like
_25._tcp.
5 matches
Mail list logo