Operations | Monitoring | ITSM | DevOps | Cloud

This article helps you understand DNS prefetching, one type of resource hint, including what they are, why and how to use them, and best practices for auditing and scaling them.

Whenever an online service goes down, you're likely to hear three words: "it was DNS!" Blaming DNS might be a running joke among network admins and engineers, but it's one rooted in experience. DNS problems are known for causing massive, Internet-wide outages such as the 2021 Akamai outage that temporarily made the websites for Delta Air Lines, American Express, Airbnb, and others unreachable.

Migrating your DNS to a cloud provider like Amazon’s Route53 service can be a daunting task. Thankfully, with dns-tools you can test your DNS records before and after the migration to ensure that everything made it across in one-piece. This is the three steps we follow when migrating to Route 53: Follow along below and in just 10 minutes you’ll know if everything will migrate smoothly for you.

As a software engineer, I admit I am not the best at networking. Can’t connect to your app for some reason, one going joke is to “always blame DNS” e.g the Domain Name System. My personal DNS experience is usually editing a few records for my personal blog and connecting a few tools and that is it. Thanks to distributed systems, had to learn all about SRV records and some more DNS concepts.

While MSPs have been making significant investments in security and offering services, it is a challenge to keep up with the frequency and evolving sophistication of today’s cybersecurity threats. Defense in Depth (DiD) is the foundation on which most MSPs have built a layered security approach for dealing with them.

Last week I created a guide for our users to set up an NGINX service as an API Gateway with Qovery. The API gateway must redirect the incoming traffic to the appropriate service with the correct port. My problem is that the API Gateway does not know the ports exposed for every service. In this post, I will show you a quick tip on finding the port of a Kubernetes service with a single DNS request. Let's go!

We’ve all been there. After countless hours of development, you’re ready to take that app that works awesome on “localhost” live to production, but production services will only interface over https. Or maybe, your DNS is managed on Cycle, but some third-party app you want under the same domain requires a TLS certificate.

We can now notify you of changing DNS records and let you know when we've detected a problem with your domain nameservers. Woohoo! 🥳