Oh sry just saw Emanuel’s response. On Wed, Feb 28, 2024 at 7:37 AM Opti Pub <sysad...@optipub.com> wrote:
> I agree on a longer TTL in general if you’re not doing maint but a short > TTL shouldn’t cause failures by itself… unless you’re maxing a limit on > lookups or something? > > Looks like it’s on cloudflare who claims not to cap/cut off lookups but > maybe you have some reporting on that end you could check out/confirm > lookup errors idk. You’d think your DNS monitoring would catch it though. > > > On Wed, Feb 28, 2024 at 2:59 AM Kai Bojens via mailop <mailop@mailop.org> > wrote: > >> Am 27.02.24 um 23:30 schrieb Rob Nagler via mailop: >> >> > $ dig +short txt nagler.me <http://nagler.me> >> > "v=spf1 a mx ip4:139.177.203.52 include:_spf.google.com >> > <http://spf.google.com> -all" >> >> A TTL of just 300 seconds is way too short IMHO. If anything happens to >> your DNS you just have five minutes to fix the problem. Set the TTL to >> at least 3600 seconds. >> >> _______________________________________________ >> mailop mailing list >> mailop@mailop.org >> https://list.mailop.org/listinfo/mailop >> >
_______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
