GoDaddy DNS has gone diddy An unspecified technical infrastructure issue has left GoDaddy customers with serious DNS issues this morning. Despite a status page claims that all is green and healthy at registrar and web hosting business GoDaddy, customers have been complaining on Twitter, as well as to The Register, and to GoDaddy itself, that their …
So, as usual, I see these things and I chuckle a little seeing these budget one stop shops having problems affecting businesses.
20 minutes after reading the story, my boss calls me to say one of our websites are down. I go to check, the DNS address can't be found.
I do a whois on the site, the domain's name server is with GoDaddy.
A/C because I'm feeling a little stupid.
Well I would do but he died late last year.
It's affecting two sites, but there's absolutely nothing I can do about it. I'm moving sites over to DNS Made Easy as they offer failover protection, but the problem is I go on to GoDaddy's control panel and guess what happens?
"sso.godaddy.com’s server DNS address could not be found."
At least this didn't happen on a Friday. I'd have been well pissed off.
Tech: "but it's ok, I changed the TTL from one week to 1 hour when I made the change to the NS record entries"
Engineer: "Sure... but what about all the nameservers that contacted us within the last 6 days. How will they know about the change?"
Tech: "Because I changed the TTL".
Engineer: "<facepalm> Yea, but you need to wait for at least the old TTL value before everyone knows about it. Go read the cricket book... when you're done, come back and I'll draw this out on the whiteboard... in the mean time I have a mess to fix".
Tech: "Because I changed the TTL"."
This.
Spent not one but *four* meetings (hour plus) explaining this issue to management, techies and architects whilst I was outsourced to that "Moving" company. Since default TTL in the originating system was 7 days, it took me forever to get them to understand that if they *wanted* active/active on the open internet, using outside IPs, we had to break the "Standards" enforced by a department that did not quite comprehend what they were doing with DNS.
Oh, there are few that know what to do with DNS. Not I claim to be a mega expert on it either, but I have this weird habit of studying what I use so I know the impact of messing around with it.
The problem with TTLs is that in the era of lesser bandwidth (i.e. at any given time, anything older than 3 months) some idiots started caching DNS data and ignore TTLs - this is part of why you sometimes end up with a 24h wait for full propagation.
But yes, sigh. Explaining it takes sometimes more time than I have.
Spam has started trickling through on one of my affected domains
Spam is the one universal constant of the Internet - sort of like death, taxes an political corruption in the real world.
I registered a domain for someone recently and then went on to configure email on my firewall & mail server. By the time I had logged into the firewall to do the change, I could already see spam being directed at the new domain (and being rejected because the firewall was (quite rightly) claiming it knew nothing about the domain).
It turns out that the spam started being generated about two hours after he registered the new company that the domain was for - which was about 3 days before I did the domain registration. So the spamscum obviously are watching the Companies House website for new companies..
This post has been deleted by its author
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2024
