On Thu, 2 Aug 2012, Marco Davids (SIDN) wrote:
> Dig 9.9.1 is setting the AD-bit in queries by default.
>
> Does anyone know why?
3205. [func] Upgrade dig's defaults to better reflect modern
nameserver behaviour. Enable "dig +adflag" and
Hi,
Dig 9.9.1 is setting the AD-bit in queries by default.
Does anyone know why?
Took me a while to figure out, among other things because Wireshark has
a little bug that prevents the AD-bit being shown in queries.
(reported as bug 2472 and 7555 on https://bugs.wireshark.org/bugzilla/)
Thanks.
> To check whether BIND is your problem simply run "dig -t MX " on
> the host that is trying to send the email to your mail host. If it returns
> the right IP address for your mail host then BIND isn't the problem.
I can't do this because I tried to send it from gmail.
> As Jeff Lightner said, t
Context: BIND 9.8.3-P2
If dnssec-signzone is invoked with -S (smart signing), it examines keys
in the key repository directory (-K) and selects only current keys for
inclusion in the zone. That works well. It also generates DS records for
the parent zone and lands them in a dsset file in (-d).
Th
Jiann-Ming Su wrote:
> What would cause a delay in zone transfers? The notify go out
> immediately when the serial number changes on the master, but some of the
> secondaries can take up to 10 minutes before initiating the zone
> transfer. Also, even after the zone has been transferred, the secon
On 8/2/2012 2:38 PM, Jiann-Ming Su wrote:
> What would cause a delay in zone transfers? The notify go out immediately
> when the serial number changes on the master, but some of the secondaries can
> take up to 10 minutes before initiating the zone transfer. Also, even after
> the zone has bee
What would cause a delay in zone transfers? The notify go out immediately when
the serial number changes on the master, but some of the secondaries can take
up to 10 minutes before initiating the zone transfer. Also, even after the
zone has been transferred, the secondary will not immediately
I built statically linked binaries, and it fixed the problem.
- Original Message -
> From: Jiann-Ming Su
> To: "bind-users@lists.isc.org"
> Cc:
> Sent: Thursday, August 2, 2012 3:50 AM
> Subject: undefined symbol: isc_commandline_index??
>
> Initially sent this message to the dhcp-us
-Original Message-
From: Peter Olsson
Date: Thursday, August 2, 2012 10:25 AM
To: Cathy Almond
Cc: "bind-users@lists.isc.org"
Subject: Re: What does "deleted from unreachable cache" mean?
>Excellent information, thanks!
Agreed. I really appreciate the effort ISC has put into the KB.
On Thu, Aug 02, 2012 at 03:26:08PM +0100, Cathy Almond wrote:
> On 19/07/12 00:49, Peter Olsson wrote:
> > Hello!
> >
> > After my latest bind upgrade our slave server started
> > occasionally writing these messages to the log:
> >
> > master 2a02:::::2#53 (source ::#0) deleted from u
On 19/07/12 00:49, Peter Olsson wrote:
> Hello!
>
> After my latest bind upgrade our slave server started
> occasionally writing these messages to the log:
>
> master 2a02:::::2#53 (source ::#0) deleted from unreachable cache
>
> master 62.xxx.xxx.2#53 (source 0.0.0.0#0) deleted from
Initially sent this message to the dhcp-users list by mistake...
Successfully building 9.8.3-P2 on a CentOS 5.x system with rpmbuild. I
can install the RPMs, but when I try to start the named process, I get
the following:
/usr/sbin/named-checkconf: symbol lookup error: /usr/sbin/named-checkcon
12 matches
Mail list logo
