Lars Hecking wrote:
I have started seeing these entries in named.log:
29-Mar-2009 05:02:35.467 general: warning: update with no effect
29-Mar-2009 05:02:35.468 general: warning: update with no effect
29-Mar-2009 05:02:35.469 general: warning: update with no effect
29-Mar-2009 05:02:35.470 general: warning: update with no effect
29-Mar-2009 05:02:35.471 general: warning: update with no effect
29-Mar-2009 05:02:35.472 general: warning: update with no effect
29-Mar-2009 05:02:35.478 general: warning: update with no effect
29-Mar-2009 05:02:35.479 general: warning: update with no effect
29-Mar-2009 05:02:35.480 general: warning: update with no effect
29-Mar-2009 05:02:35.481 general: warning: update with no effect
29-Mar-2009 05:02:35.482 general: warning: update with no effect
29-Mar-2009 05:02:35.483 general: warning: update with no effect
29-Mar-2009 05:02:35.484 general: warning: update with no effect
What is that about? This is bind 9.4.2-P2 on Solaris 8.
If I had to guess, I'd say it's probably a broken IXFR implementation on
the other end:
if (result == DNS_R_UNCHANGED) {
/*
* This will not happen when executing a
* dynamic update, because that code will
* generate strictly minimal diffs.
* It may happen when receiving an IXFR
* from a server that is not as careful.
* Issue a warning and continue.
*/
if (warn)
isc_log_write(DIFF_COMMON_LOGARGS,
ISC_LOG_WARNING,
update with no effect);
It would be nice to have the zone name and/or master server name in the
error message. Maybe that was added in a later version (too lazy to
check right now :-)
- Kevin
___
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
