Re: [Pdns-users] Warning in syslog after upgrade to PowerDNS Authoritative Server 4.7
Quoting Sander Smeenk via Pdns-users (pdns-users@mailman.powerdns.com): > I'll try 4.8.x stable. See if it returns. Heheh. That's not out yet. :-) -Sndr. -- | Always try to be modest, and be proud of it! | 4096R/20CC6CD2 - 6D40 1A20 B9AA 87D4 84C7 FBD6 F3A9 9442 20CC 6CD2 ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com https://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] Warning in syslog after upgrade to PowerDNS Authoritative Server 4.7
Quoting Giorgio Lardone via Pdns-users (pdns-users@mailman.powerdns.com): > "pdns_server[7658]: Unable to retrieve SOA for domainname.tld, this > was the first time. NOTE: For every subsequent failed SOA check the > domain will be suspended from freshness checks for 'num-errors x 60 > seconds', with a maximum of 3600 seconds. Skipping SOA checks until > 1666868614" H. Interesting. I have noticed this specific 'issue' too after i upgraded to 4.8.0~alpha0+master.4.g90d8b86d0-1pdns.focal back in august 2022. Then suddenly a lot of zones i'm secondary for started to log this at random moments. I came from 4.7.0~alpha1+master.826.g9c9e6a1dc-1pdns.focal at that time, and had no issues there. On IRC i wrote "am pretty sure the issue was introduced between 4.7~826 and 4.7~856. I am now back at 4.7~826 and no longer have the timeouts." I stopped 'living on the edge' some time after that and switched back to the stable branch, so i'm running pdns-recursor 4.7.4-1pdns.focal for a while now. The 'Unable to retieve SOA' issue doesn't show in my logs of last week. I'll try 4.8.x stable. See if it returns. -Sndr. -- | Class trip to the Cola factory... I hope there's no pop quiz... | 4096R/20CC6CD2 - 6D40 1A20 B9AA 87D4 84C7 FBD6 F3A9 9442 20CC 6CD2 ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com https://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] Why the rectify-zone? increase-serial?
Quoting Sander Smeenk via Pdns-users (pdns-users@mailman.powerdns.com): > Could this not be handled by some logic that compares the serial > to the last-rectified serial and rectifies it on the fly when needed? > This might not work for super huge zones perhaps, performance wise, > but i dont think i would notice anything in my workload. ;-) Heh. According to da interweps, this was 'discussed' on list earlier. http://powerdns.13854.n7.nabble.com/How-do-you-rectify-zones-tt8633.html#none But that thread just boils down to "Yea, you got to rectify-zone yourself." ;) Rgds, Sndr. -- | Junk is something you've kept for years and throw away three weeks | before you need it. | 4096R/20CC6CD2 - 6D40 1A20 B9AA 87D4 84C7 FBD6 F3A9 9442 20CC 6CD2 ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com https://mailman.powerdns.com/mailman/listinfo/pdns-users
[Pdns-users] Why the rectify-zone? increase-serial?
Hi, Today one of my customers was complaining that his NODATA-proof is failing after adding CAA-records to a signed domain. I quickly rectified the zone, flushed the caches, all is well again. This makes me think about the 'why' behind the rectify-zone command. We've scripted triggers that rectify a zone after a customer changes records, most probably that trigger failed in this case, but why actually do we have to do this manually? Are there any situations where we do NOT want to rectify-zone after a change? ;-) Could this not be handled by some logic that compares the serial to the last-rectified serial and rectifies it on the fly when needed? This might not work for super huge zones perhaps, performance wise, but i dont think i would notice anything in my workload. ;-) | "Volgens Marco Davids, Technisch Adviseur bij SIDN, is het vergeten | van de rectify-zone-opdracht een van de meest voorkomende fouten | van dit moment." Regards, -Sander. -- | Spend some time trying hard not to think about giraffes. | 4096R/20CC6CD2 - 6D40 1A20 B9AA 87D4 84C7 FBD6 F3A9 9442 20CC 6CD2 ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com https://mailman.powerdns.com/mailman/listinfo/pdns-users
