ISKTBN: i should know this by now.

  Today on "Things others learned", a client finds out nameservers, when they want to, will 'eff up their deliverability. This story is the counter to " Damn Beautiful Nameservers ." Instead of me oozing praise all over them, I'm going to go all "Negative Nancy" on them. But it's really not their fault. They can't help if it if they are given the wrong information or left unattended. But what the hell, I'm gonna curse them out anyway otherwise my whole schtick for ISKTBN is ruined. So today, nameservers aren't my friend, or, I should say, my client's. And so my story begins... Far, far way, in a work-from-home office that isn't an office, but holds a desk, computer, and internet connection... A prospect (further to be called 'client' because it's easier) reached out to me after they kept experiencing a high volume of bounces to emails they KNEW were active (one was their sister's email.) They also were receiv...

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...