ISKTBN: i should know this by now.

  Today on "Things that are awesome!", I get to share BIG NEWS! Deliverability Week 2024 is coming! That's right you deliverability nerds. You finally get your day in the sun. Your week to geek out with your technique out!  Oof, did I just say that? YES, yes I did! And I don't care because I'm super jazzed to be able to collaborate with the deliverability greats out there that have taught me so damn much. Those that keep teaching me. Those helping me learn. Those correcting me when I'm mislead. Those guiding me when things get tough. And those cheering me on and believing in me. This deliverability thing can be hard. But having a community makes a world of difference! So although I'm celebrating the upcoming week that will be filled with wonderful content, undoubtedly loaded with secrets of the trade and, if we are lucky, full on rants dripping with sarcasm and brilliance, I'm really celebrating the people who have paved the way and made this an indust...

May 10, 2024 Update  and SPOILER ALERT  ( jump ahead if you want to read through the post first) I incorrectly attributed my success to DNS cache. But it wasn't DNS cache that saved my butt. It was nameservers (and I got lucky with timing.)  The information I was searching for was available not because of cache, but because GoDaddy's nameservers hadn't yet received the updated instructions to remove the DNS records. Looking at some of GoDaddy's documents for removing domain entries, they do list out recovery times if something was done in error, but that is likely some other process. I also asked someone at GoDaddy how the UI and DNS were connected, and they stated that although UI changes are typically updated on the nameservers quickly (within an hour), it can take longer.  THIS is why I was able to look up values well beyond the often generic TTL of 1 hour and the  records I needed were therefore  published long enough for me to go back and look them up...