Am 2011-06-21 19:01:57, hacktest Du folgendes herunter:
This sounds like a failure of the DNS Notify system. Have you checked
the logs? If nothing interesting is logged, have you checked the
logging statement?
On 22.06.11 12:57, Michelle Konzack wrote:
I have nothing found relevant. I will delay the next changement directly
after the logrotate and I will see whats going on here.
And as I sayed, it happen AFTER I have added DNSSEC.
So, if I clean on the SLAVE the Cache, it suck automatical the new zones
from the MASTER, which mean, the SLAVE is OK, right?
This would mean the MASTER does not send the notifiication to the SLAVE
if a zone has changed, but the weird thing is, I see the MTIME changeing
on the SLAVE, which mean, there was a changement... but the zone was
not updated.
After changing the file on master, increasing the SOA and reloading the
zone, did you check the SOA version on master? Did the master reload new
zone? What do logs say?
Changing timestamp on slave indicates that the slave is checking and thinks
it hat the fresh version. What do the logs say?
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Spam = (S)tupid (P)eople's (A)dvertising (M)ethod
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
