Chapter 47. Everything Is a DNS Problem: How to (Im)prove
Michael Friedrich
“Everything is a DNS problem.” This likely sounds familiar, and you’ve probably heard it from your team members during an incident. Customers say that your shop website is not working. You have verified it in your browser, and it seems fine.
DNS relies on a distributed environment, which makes it highly available and sometimes hard to debug. The problem is not necessarily bound to resolving a domain name. Instead, you need to get the whole picture with network routing and analyze the packet path with a client’s point of view.
If the website is not reachable, is it a DNS problem? It could also be related to a specific location, where the client is trying to fetch the content behind a firewall or proxy. This needs more investigative work. Being the detective when your customers call can be a challenge.
Before you start analyzing the problem, stop for a moment and breathe. You cannot know everything. The documentation and Google are both your best friends. Forget what others say about “read the f***ing manual” (RTFM); the documentation should always be your first entry point. Maybe a friendly developer added a troubleshooting section, or you’ll find a link to a page that explains the problem you’re facing.
Accelerate your “Google-fu” by searching for the full error message and ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access