Re: Having multiple name servers - is it really necessary
On February 2, 2010 2:25:50 PM -0800 Rob Tanner rtan...@linfield.edu 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 applications that depend on name services. For example, if your link goes down and instead of a DNS lookup which results in an answer of an MX server that doesn't respond, someone trying to send you mail would (after cache timeout) get back a non-result DNS answer and might bounce a mail instead of queueing it for later delivery. That's perhaps not a good example because actually MTAs should handle this case as a transient error and queue any mail, but you get my point. Consider also that folks just browsing your website will get a different kind of error which might lead them to believe that your site doesn't even exist. That would definitely be worse than connection timed out. Other applications may result in similar types of disconcerting errors instead of just connection timeouts. You really do need multiple nameservers, and you absolutely need to make your DNS zone transfers reliable. I do sympathize with you. Old data is often worse than no data. -frank ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: NOTIFY logging problem
On February 1, 2010 1:12:56 PM +1100 Mark Andrews ma...@isc.org wrote: In message ed6e4c848e8fef4b16e71...@181.sub-97-18-81.myvzw.com, Frank Cusack writes: On February 1, 2010 11:35:15 AM +1100 Mark Andrews ma...@isc.org 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 that the default anyway? Seems to me that you aren't likely to have too many servers and the info level is already pretty verbose so you would expect (or at least *I* would expect) to have that amount of information. When you have 10+ zones with 10's of servers it gets noisy. quite. I hadn't considered there would be a log entry per zone. -frank ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
NOTIFY logging problem
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 (serial 2010012700)
I'd like to see a verification of every host a NOTIFY message was sent to.
-frank
___
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
how do I get a slave to send NOTIFY messages?
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-notify only applies to type master servers however I can't find confirmation of that anywhere else. Note that I do not want to send NOTIFY messages to the NS servers for the zone, I want to send them to different servers. thanks ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
