Live data from Hacker News

DNS is for people, not for IT infrastructure

louwrentius.com

101–102 of 102 posts

Re: DNS is for people, not for IT infrastructure

#101
This has a serious case of in-housing the edge cases that I don’t think many would want to pay the price for.

The problem with DNS per the haiku isn’t that it’s difficult to understand, or even that running your own DNS server is particularly difficult. It’s that coordinating information and exchange at scale is a tricky problem with a lot of non-obvious edge cases and foot guns.

So trying to reduce complexity by sidestepping DNS really doesn’t do that, it just leaves you holding the bag on all the problems that DNS was quietly solving for you in the background.

Re: DNS is for people, not for IT infrastructure

#102
post #28

DNS is merely one implementation of service discovery; even without DNS, some other form of service discovery would still be needed.

Why would some form of service discovery be required? No need to discover things if you can push said information in configuration updates using tools like Ansible, pyinfra, and so on?

I think the essential difference between these two approaches lies in whether the complexity is placed at update time or query time. When updates are infrequent, or when the number of machines that need to apply the update is small, this is certainly reasonable.
Post reply on HN