SIGCHASE is a external contribution that is provide "as is" to dig.
The reason that you have to explicitly define it is that ISC hasn't
fully gone through the code to find bugs like this in it and it
basically needs a full re-write. That said it does mostly work and
is better than nothing.
This
I guess I'm still not understanding your requirements. In my thinking,
the local DNS server would *be* a stealth slave. Why are you considering
these as 2 separate instances?
- Kevin
On 2/24/2014 9:56 AM, houguanghua wrote:
Dan,
Yes
I have verified that this also happens intermittently with dig in BIND 9.9.5
built/configured with:
STD_CDEFINES="-DDIG_SIGCHASE=1"
export STD_CDEFINES
./configure --enable-threads --enable-largefile
—
Raymond Walker
Software Systems Engineer StSp.
ITS - Northern Arizona University
From: Ray Wal
Dan,
Yes, also-notify can hide the slave name server. But local dns server can't
know where is 'stealth' slave too.
Thanks,
Guanghua
Date: Fri, 21 Feb 2014 07:50:05 -0600
From: Daniel McDonald
To: Untitled
Subject: Re: bind-users Digest, Vol 1769, Issu
4 matches
Mail list logo
