All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

Why DNS should be reserved for human-facing services, not internal infrastructure

By

louwrentius

1d ago· 5 min readenOpinion

Summary

The article argues that DNS (Domain Name System) should primarily be used for human-facing services (websites, APIs) because it helps people remember names instead of IP addresses. However, the author questions whether DNS should be used for internal IT infrastructure, where machines communicate with other machines and don't benefit from human-readable names. The piece suggests that relying on DNS for internal infrastructure adds unnecessary complexity, latency, and points of failure, advocating for more direct service discovery and communication methods for machine-to-machine interactions.

Key quotes

· 4 pulled
The Domain Name System exists because it's difficult for people to remember IP addresses (185.15.59.224) and much easier to remember domain names (wikipedia.org).
This article isn't against DNS for public services, but it questions if we should use DNS for internal IT infrastructure (independent of cloud vs
Regarding internet-accessible services, it makes sense to publish websites, API endpoints or similar services using DNS, as people have to interface with them.
The added benefit of a domain name is that the associated IP address can change without the client being affected.
Snippet from the RSS feed
The Domain Name System exists because it's difficult for people to remember IP addresses (185.15.59.224) and much easier to remember domain names (wikipedia.org).

You might also wanna read