Robert,
Try setting the “Refresh” value in your SOA record to 3600. RFC1912 recommends
refresh values between 1200 and 43200. If notify messages are not working, I’d
set it to 20 or 30 minutes, myself. if the zone is unchanged, all it costs you
is one SOA query by the slave. Just make sure
At least the 'right' way with turning down the SOA TTL for the zone.
This is one of the set it and forget it items (at least for me), and
once I started reading finding enough articles on secondaries it was an
oh yeah moment.
On 09/07/2015 04:09 PM, Robert Moskowitz wrote:
On the Samba list,
On the Samba list, I was told that it is working (bug from2 years ago,
still open, was fixed):
https://bugzilla.samba.org/show_bug.cgi?id=9634
But Notify does not work:
"yes it does work. But the DLZ bind will not notify any slaves, when the
repository changes. This can be painful,
It seems I have this working, but...
I have a regular Centos7 Bind 9.9 server that I want to secondary a
Samba AD (Also Centos7) DLZ zone.
On the DNS server (192.168.192.5) I have:
zone "home.htt" {
type slave;
file "slaves/bak.home.htt";
4 matches
Mail list logo
