On 1/31/10 10:08 PM -0500 Joseph S D Yao wrote:
I suspect that the notify option is set to 'no' either in your global
options or in your view or in your zone.
Indeed, I had a global "notify no" option. I misunderstood the way
that zone-specific also-notify and the global notify option interact
On February 2, 2010 2:25:50 PM -0800 Rob Tanner
wrote:
cached (i.e. Is no data treated the same as bad data by upstream bind
servers?
I didn't entirely follow your ramble (paragraphs would have helped),
but it's not BIND or other nameservers that would be the real problem,
it's the application
On February 1, 2010 1:12:56 PM +1100 Mark Andrews wrote:
In message , Frank
Cusack writes:
On February 1, 2010 11:35:15 AM +1100 Mark Andrews wrote:
> You need to be looking a debug 3.
>
> notify_log(notify->zone, ISC_LOG_DEBUG(3), "sending notify to
>
On February 1, 2010 11:35:15 AM +1100 Mark Andrews wrote:
You need to be looking a debug 3.
notify_log(notify->zone, ISC_LOG_DEBUG(3), "sending notify to %s",
addrbuf);
ouch, debug 3 is probably way TMI. I guess I'll just patch the above
to log at info. Why isn't
I have also-notify configured for a slave zone. The real master is a
so-called stealth master and all other slaves must consult this slave
nameserver that has also-notify configured.
The slave doesn't appear to be sending NOTIFY messages to the also-notify
hosts. zytrax does say that also-notif
How can I get logs of all NOTIFY messages sent?
logging {
// use local0 instead of daemon
channel local0_syslog {
syslog local0;
severity info;
};
category notify{ local0_syslog; default_debug; };
};
The above only generates a summary log:
zone XXX/IN/internet: sending notifies (s
6 matches
Mail list logo