Yes. Immediately right after. I just re-read your log lines:
>>> 10-Jan-2018 18:11:24.387 notify: client 10.198.180.41#12149: received notify for zone 'example.com' >>> 10-Jan-2018 18:11:24.387 general: zone lhr4.dqs.booking.com/IN: notify from 10.198.180.41#12149: no serial >>> 10-Jan-2018 18:11:29.453 notify: client 10.198.180.41#12149: received notify for zone 'example.com' >>> 10-Jan-2018 18:11:29.453 general: zone lhr4.dqs.booking.com/IN: notify from 10.198.180.41#12149: no serial >>> 10-Jan-2018 18:11:38.350 notify: client 10.198.180.41#12149: received notify for zone 'example.com' >>> 10-Jan-2018 18:11:38.350 general: zone lhr4.dqs.booking.com/IN: notify from 10.198.180.41#12149: no serial There is example.com and lhr4.dqs.booking.com, hence I guess this is incomplete obfuscation. The NOTIFY is received every 7-10 seconds. Do you update the zone that often or are these retransmission? If these are retransmissions then there may be a firewall problem between Bind and PowerDNS. regards Klaus Am 17.01.2018 um 15:43 schrieb Steve Zeng: > Klaus, > > Good to know. when would BIND do a SOA query to the configured master to > check the serial? Is it immediately right after it get NOTIFY from master? > > Thanks, > Steve >> On Jan 17, 2018, at 3:32 PM, Klaus Darilion <[email protected]> >> wrote: >> >> >> >> Am 17.01.2018 um 15:13 schrieb Steve Zeng: >>> Pieter, >>> >>> I checked BIND slaves logs around the time frame and found: >>> >>> 10-Jan-2018 18:11:17.211 notify: client 10.198.180.41#12149: received >>> notify for zone 'example.com' >>> 10-Jan-2018 18:11:17.211 general: zone lhr4.dqs.booking.com/IN: notify from >>> 10.198.180.41#12149: no serial >>> 10-Jan-2018 18:11:24.387 notify: client 10.198.180.41#12149: received >>> notify for zone 'example.com' >>> 10-Jan-2018 18:11:24.387 general: zone lhr4.dqs.booking.com/IN: notify from >>> 10.198.180.41#12149: no serial >>> 10-Jan-2018 18:11:29.453 notify: client 10.198.180.41#12149: received >>> notify for zone 'example.com' >>> 10-Jan-2018 18:11:29.453 general: zone lhr4.dqs.booking.com/IN: notify from >>> 10.198.180.41#12149: no serial >>> 10-Jan-2018 18:11:38.350 notify: client 10.198.180.41#12149: received >>> notify for zone 'example.com' >>> 10-Jan-2018 18:11:38.350 general: zone lhr4.dqs.booking.com/IN: notify from >>> 10.198.180.41#12149: no serial >>> >>> wondering why there is ’no serial’ in the logs. Since the column does have >>> the value: >>> >>>> select * from domains where name='example.com'\G; >>> *************************** 1. row *************************** >>> id: 484 >>> name: example.com >>> master: 10.187.125.2:53,10.187.125.2:53 >>> last_check: 1516197871 >>> type: SLAVE >>> notified_serial: 2016918645 >>> >>> is “no serial” the cause of notification failure? >> >> I do not think this is the problem. NOTIFYs may have serials, but >> without serial is also allowed. And PowerDNS does not send serials. >> >> Usually, when there is no serial, Bind will do SOA-Queries to the >> configured masters to check the serial on the master. >> >> regards >> Klaus >> _______________________________________________ >> Pdns-users mailing list >> [email protected] <mailto:[email protected]> >> https://mailman.powerdns.com/mailman/listinfo/pdns-users >> <https://mailman.powerdns.com/mailman/listinfo/pdns-users> > _______________________________________________ Pdns-users mailing list [email protected] https://mailman.powerdns.com/mailman/listinfo/pdns-users
