MENU
  • Enom.com
  • Resellers

Enom Blog

DNS
Category

  • Update your DNS for our hosting service

    March 13, 2017

    Advice, Announcement, DNS, Resellers

     3

    Views: 4425

    On April 13th, 2017, we will be performing changes to our infrastructure that will affect your hosting account. We have recently sent an email, outlining your account details as well as new IP addresses for your use. If you have not received the email, please contact customercare@enom.com to retrieve the details.

     

    What you need to know

    A series of IP addresses for the server which your hosting account is associated with, will be changing that will require you to update your DNS. If you are using a third-party DNS to point to your website, you will need to configure the zone records for the domains hosted on that server. If your domains are with us and are using our DNS, there’s no action required on your part. We will take care of the changes for you. There will be no downtime during this period, and we strongly encourage you to make the changes before the April 13th, 2017 to avoid any service interruptions.

    Please note: If you require support on configuring your DNS, please refer to your third-party DNS provider.

    Read More

  • Preparing your business for the next internet outage

    October 28, 2016

    Advice, DNS, SSL

     6

    Views: 4675

    Is your business prepared for the next internet outage?

    October 21st, 2016 was a frustrating day for many internet users as a coordinated attack on the Domain Name System (DNS) provider Dyn caused major platforms like Twitter, Netflix, and Reddit to go down for much of the day. The complaints raised that morning (and the conspicuous lack of complaints on the affected social networks) were what made the headlines, but in the aftermath, cybersecurity experts started piecing together what happened. The suspected source of the attack was actually millions of sources: household appliances and other internet-connected devices that had been infected by the Mirai strain of malware.

    Businesses that relied on these platforms to interact with their customers were either slowed, or stopped entirely during the outage. Imagine how many pre-existing customer issues being handled over Twitter were exacerbated when the cyberattack occurred. This is perhaps the first lesson to be learned: Diversify your web presence across several social networks, and better yet, have a dedicated domain and website that you can update easily. No one social network is ultimately immune from massive cyberattacks, but spreading your communication across several channels helps to ensure that you aren’t entirely cut-off in a crisis.

    While there’s little you can do alone to prevent massive cyberattacks, over the long term, you can and should be protecting yourself and your customers. The appliances and devices used in the October 21st attacks are considered “easy targets” by hackers, but there’s no reason that your own customers should be exposed to the same risks. One of the first things you ought to be doing is adding an SSL certificate to your domain to make sure traffic to your website is kept private and safe. GeoTrust’s True BusinessID with EV is a popular option with businesses because it not only keeps visitors safe from malware and data breaches, but makes sure they know they are safe when conducting business on your website.

    The October 21st outages shouldn’t be thought of as outliers. With countless household appliances and devices now connected to the internet, cybercriminals have more resources than ever to launch attacks on websites and online service providers. Taking the precautions outlined above will give you more options to keep in touch with your customers when the next emergency hits.

    Read More

  • Our New DNS: Under the Hood

    December 9, 2015

    DNS, News

     1

    Views: 4931

    At Enom, we know that every DNS performance issue we can solve proactively saves you from countless support headaches down the line. Striving to ensure that it “just works” is a given, but we’re also constantly searching for ways to go above and beyond, pushing the bounds of what’s possible on a global scale. Every facet of our operation is dedicated to that cause, and we’ve been working hard on some major changes to our DNS to deliver on it. This is why we wanted to peel back the curtain a bit, talk with some of the experts close to these changes, and give you an idea of what it all means for you.

    Three billion DNS queries. That’s what Enom’s platform handles every day to service our customers. In some ways, it’s a daunting number that reinforces how many portfolio owners, resellers, and end users rely on our DNS, but it also presents an opportunity. That’s because each improvement made to the system sends ripples through every level of the experience. Thanks to the Rightside and Enom engineering team, we are now happy to introduce our new DNS platform, one that is faster, more reliable, and scalable to your growing needs.

    We’ve undertaken this massive overhaul because those three billion DNS queries will only continue to grow. In addition to total volume, the standards and requirements for DNS have changed dramatically since our last upgrade. Yet, if we’ve done our job, most won’t realize a change even occurred. “The new DNS infrastructure will go largely unnoticed,” says Rightside CTO Wayne MacLaurin. “Infrastructure is like plumbing; nobody really notices it unless it breaks.”

    New platform

    The new DNS platform, which has been live since November, is based on BIND, one of the most widely used, open-source implementations. The decision to change from a PowerDNS infrastructure to BIND 9.10 came about due to a confluence of factors: aging hardware, rapidly expanding data volume, a need for more standardized, secure solutions, and the constant pursuit of general performance improvements. Newer servers optimized for BIND were the antidote to a highly customized, and increasingly unwieldy architecture.

    “The previous infrastructure relied heavily on MS SQL and replication to distribute data to our various DNS PoPs,” MacLaurin says. “It also had a large amount of programmatic logic built into the DNS software itself to handle various customized features. As time passed and DNS query volumes increased, the infrastructure started showing its age. It was hard to update, hard to debug, and it could only handle a fifth of the volume of our new modern DNS server.”

    Additionally, Enom’s servers now employ Kafka to provide high-throughput messaging between our central system and distributed DNS nodes. A series of complex transformations handle the translation of older data into standard DNS types, managing the emulation of non-standard features such as CNAME at apex. To improve monitoring, an ELK (Elasticsearch, Logstash, Kibana) stack now manages statistics gathering and logging.

    What’s different?

    Again, many of the changes may go unnoticed, but the actual differences are remarkable for those with a keen eye for DNS performance. In addition to the new architecture, Enom made significant investments into SSD-based storage, which were then deployed throughout our production environments. Together, software and hardware greatly reduced response times, with updates (such as host changes) now being delivered to the world in under 3 seconds. The everyday end user may not be aware of these faster response times, but cumulatively, this equates to vastly improved interactions.

    “CNAME at apex is possibly the most significant change,” says Ron West, a Senior Software Architect at Enom. Currently, Enom’s DNS answers with what’s known as a CNAME record at the apex of a zone. “This isn’t allowed in DNS, and has undefined behavior to end users. It often works, but sometimes fails badly.” Standard DNS software doesn’t support these records creating uncertainty as to how they would behave in the wild. A workaround was deployed to eliminate that uncertainty.

    “We now take the target of the CNAME record, look up the records it points to, and add them to our own DNS instead of the CNAME record. These look-ups are refreshed continuously, and allow all affected domains to keep working.” These previously undefined behaviors—affecting more than 65,000 domains in Enom’s system—represented many headaches for support at the reseller level, an effort that is no longer necessary thanks to these new enhancements.

    The new DNS also supports deletion holds to benefit customers moving their domains to another registrar or DNS host. “Instead of suddenly refusing to answer queries, or answering with parking,” West says, “we can now facilitate transitions by continuing to answer with the last known DNS records for 4 days. After deletion, we either decline to answer queries (if no longer aimed at our nameservers) or answer with parking.”

    The only exception is multiply hosted domains (multiple DomainNameIDs with the same domain name) where deletion is immediate, leading to the next-highest-priority domain’s records being activated immediately.

    Philosophy shift

    Ultimately, all these changes have come about due to a philosophy of looking creatively at different technologies to solve challenges more quickly than traditional approaches. “Doing so is crucial because the requirements and limitations of one registry aren’t necessarily the same as another,” MacLaurin says. “It’s something that we embrace wholeheartedly, especially if we can reduce complexity, improve reliability, and move faster.”

    The change to Enom’s DNS infrastructure is just one step in a continuous improvement process. “We try not to make technology choices the limiting factor in designing great product architectures. For instance, Kafka was used heavily in the DNS project, but we are also looking at RabbitMQ because each messaging platform has different strengths and weaknesses, depending on the engineering requirements. Elasticsearch is only one of the technologies we are looking at to redefine how we manage our data.”

    Looking ahead

    The DNS improvement project isn’t just a way to squeeze more speed out of the system; it’s an outcome of our goals in using technology to advance the domain name industry and make it easier and less complex to manage for you and your customers. The standards-based nature of BIND, for instance, means we will be able to protect our users better by pushing ahead with support for DNSSEC and other new extensions such as DANE.

    System-wide stability and security are also always in mind. DDOS mitigation is now a major component of any modern DNS infrastructure both in terms of the scale of DDOS we see, but also in how we handle and mitigate DDOS in general. We want to reduce or eliminate every instance of downtime that we can for you and your users, and won’t stop until we have.

    “Nobody really notices DNS unless it breaks.” It highlights the reactive nature of most DNS support efforts. But it’s also why our engineering team has bucked the trend by taking a creative, proactive approach to fixing major DNS issues, some of which are only just now on the others’ radars. We’re always busy applying modern technology solutions to an aging global network. It’s the only way to ensure that our industry keeps prospering, and we are thrilled to keep you updated about all the exciting innovations we’re developing (and surprising things we’re learning) as the Internet continues to grow and adapt.

    If you’d like to learn more about DNS, check out this article from ICANN.

    Read More

FEATURED POSTS

  • How to Win by Treating Your Customers as Members

    August 13, 2020

  • A Great Domain for Freelancers and Entrepreneurs? Try .ME

    June 22, 2020

  • Bandzoogle: website builder for musicians

    June 1, 2020

  • security lock and credit cards on keyboard

    Avoiding COVID-19 Cyberattacks with Security Best-Practices

    April 28, 2020

CATEGORIES

  • Advice
  • Announcement
  • Developers
  • DNS
  • Featured
  • Fun
  • GDPR
  • Industry Insight
  • New TLDs
  • News
  • Premium Domains
  • Promotion
  • Resellers
  • Roadmap
  • SSL
  • Uncategorized
  • WTB

ARCHIVES

  • February 2021
  • January 2021
  • December 2020
  • November 2020
  • September 2020
  • August 2020
  • July 2020
  • June 2020
  • April 2020
  • March 2020
  • January 2020
  • December 2019
  • November 2019
  • October 2019
  • July 2019
  • June 2019
  • May 2019
  • April 2019
  • March 2019
  • February 2019
  • January 2019
  • December 2018
  • November 2018
  • September 2018
  • August 2018
  • June 2018
  • May 2018
  • April 2018
  • March 2018
  • February 2018
  • January 2018
  • December 2017
  • November 2017
  • October 2017
  • September 2017
  • August 2017
  • July 2017
  • June 2017
  • May 2017
  • April 2017
  • March 2017
  • February 2017
  • January 2017
  • December 2016
  • November 2016
  • October 2016
  • September 2016
  • August 2016
  • July 2016
  • June 2016
  • May 2016
  • April 2016
  • March 2016
  • January 2016
  • December 2015
  • November 2013
Support

Report Abuse
Help Center
Contact Us

Resources

WHOIS Lookup
Maintenance Alerts
Developers
Products & Services

Domain Name Search
Premium Domains
Web Hosting
SSL Certificates
Website Builder
Basic Email
Bulk Tools

© 2021 Enom Blog |