Brit registrar 123-Reg begins 2021 in much the same way it ended 2020 – with DNS issues
- Reference: 1610019911
- News link: https://www.theregister.co.uk/2021/01/07/123_reg_dns/
- Source link:
While [1]Microsoft and [2]Slack suffered their own high-profile wobbles as the first working week of the year got started, 123-Reg's issues appear to have been rumbling since December, biting Register reader, Alan, over the weekend.
[3]
While attempting to add a new DNS entry, Alan found that his configuration had been wiped. "All that remained was a solitary CNAME for 'www' to '@'," he told us.
"Fortunately, their nameservers are still serving the correct answers."
Alan duly raised a ticket (to which he's yet to receive a reply), checked back this week and found the configuration had changed once more, "but not what I'd ever set up, including a broken MX record pointing to 'mail.' ," he told us.
That trailing "." could cause all manner of problems in its own right.
The Christmas elves did their thing once more, and on his next check things had reverted back to just the "www" CNAME.
Alan isn't alone – a glance at the company's social media shows a number of users experiencing issues.
[4]@123reg Hey 123Reg,
my mx records have disappeared and you have no support available , really?
this is a bit rubbish for a company , no 24/7? hardly google are we , unhappy customers need support 24/7 :( cancelling asap — Damian Jones (@DamianJ95923939) [5]January 2, 2021
For its part, the company [6]admitted that some customers might be experiencing "issues related to DNS management". It suffered a prolonged DNS wobble [7]back in November following what a spokesperson described as a "recent platform update" left some unable to view or edit their DNS records.
The spokesperson went on to say the error had been corrected "for the majority of customers" and urged those still having problems to contact the company.
"I attempted a few minutes ago to phone support," said Alan. "An answering machine told me the wait would be 20+ minutes."
The Register has contacted 123-Reg for its take on the situation, and why its status page is still showing a month-old problem. We will update should an explanation be forthcoming.
[8]
In the meantime, perhaps it is time to update the age-old adage: "It's not DNS, it can't be DNS... it was 123-Reg." ®
Get our [9]Tech Resources
[1] https://www.theregister.com/2021/01/05/microsoft_365_down_in_uk/
[2] https://www.theregister.com/2021/01/04/slack_down/
[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_datacentre/networks&sz=300x250%7C300x252%7C300x600&tile=3&c=33X-c@KA6IJMeSv3qsPm9fuwAAAMs&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dtop%26test%3D0
[4] https://twitter.com/123reg?ref_src=twsrc%5Etfw
[5] https://twitter.com/DamianJ95923939/status/1345280062661283840?ref_src=twsrc%5Etfw
[6] https://www.123-status.co.uk/
[7] https://www.theregister.com/2020/11/11/123_reg/
[8] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_datacentre/networks&sz=300x100%7C300x250%7C300x251&tile=4&c=44X-c@KA6IJMeSv3qsPm9fuwAAAMs&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[9] https://whitepapers.theregister.com/
Nice pun, I dig it!
Consistency. That's what ISO9000 prizes.
This is not K8s on Istio with Space Thrusters and AI.. It's DNS hosting, stable technology for decades. How do you fuck this up so regularly.
Recommendation for Mythic Beasts for better features and a quiet life at more or less the same price...
BIND/DNS itself is stable technology. It's their pretty UI/Frontend that appears to be causing the problems. It probably stores the user's configuration in a database then that DB is exported into a BIND file. I guess the problem is in the DB/Web app. DNS is still working as they probably stopped the DB->BIND exports.
Yet another DNS fail at 123reg.co.uk
It's technical but Email from private domains at 123reg have been marked as spam senders by SPF fails at Google's Gmail for months now.
The DNS txt lines at 123reg.co.uk are so long and chaotic that they cannot be sent in a single UDP packet. Google declines to get the full TXT/SPF records and thus marks 123reg.co.uk customer domains as spam senders.
$ dig 123reg.co.uk TXT
.....
123reg.co.uk. 3600 IN TXT "v=spf1 include:a.123-reg.co.uk ip4:109.68.39.0/24 ip4:80.237.138.26 ip4:92.51.170.64/27 ip4:68.178.213.0/24 include:trustpilotservice.com include:spf.mandrillapp.com include:spf.protection.outlook.com include:sendgrid.net include:mailcontrol.com include:s" "pf.em.secureserver.net ~all"
notice the broken bit in quotes near the end >>> include:s" "pf.em.secureserver.net ~all" <<< that's the failure point. Customers with own email sending domains have to guess (from a wide selection) which of the outbound 123reg.co.uk email server will be in use. As you know a domain that sends emails out via another has to inherit that domains SPF record.
Yes they have been told/shown/proven this problem and admitted the issue but have failed to correct the problem. Other proper hosting providers do this technical point correctly. Despite promoting hosted domains as suitable for email and web friendly they disappointingly fail to deliver ( or send correctly ).
Re: Yet another DNS fail at 123reg.co.uk
I don't think that quoting is broken, see this [1]ISC document "You may have more than 255 characters of data in a TXT or SPF record, but not more than 255 characters in a single string".
[1] https://kb.isc.org/docs/aa-00356
DNS, such a bind...