zlacker

Understanding DNS Resolution on Linux and Kubernetes

submitted by fanf2+(OP) on 2025-03-23 09:42:03 | 74 points 33 comments
[view article] [source] [go to bottom]

NOTE: showing posts with links only show all posts
7. AndyMc+FM7[view] [source] 2025-03-26 13:00:19
>>fanf2+(OP)
People need to stop using .local or .dev for stuff like this. .dev is an actual TLD in the root zone and .local is for multicast DNS.

ICANN has said they will never delegate .internal and it should be used for these kinds of private uses.

I'm a coauthor on this Internet draft so I'm ofc rather biased.

https://datatracker.ietf.org/doc/draft-davies-internal-tld/

◧◩◪◨
9. weinzi+BO7[view] [source] [discussion] 2025-03-26 13:11:50
>>CableN+zE7
Let's encrypt public internet certs can have IPs in them.

https://letsencrypt.org/2025/01/16/6-day-and-ip-certs/

◧◩
11. cduzz+bS7[view] [source] [discussion] 2025-03-26 13:35:25
>>zokier+xB7
Unix predates DNS; the nsswitch.conf tells the c libraries how to convert names to IP addresses. This behavior is actually dependent on which libc you're using...

To resolve names, you can ask /etc/hosts for the name / IP conversion; you can also ask DNS, or ldap or NIS; probably there are many I've forgotten about.

solaris: https://docs.oracle.com/cd/E19683-01/806-4077/6jd6blbbe/inde...

glibc: https://man7.org/linux/man-pages/man5/nsswitch.conf.5.html

musl appears to not have an nsswitch.conf or a way to configure name to number resolution behavior?

[go to top]