Getaddrinfo() on glibc calls getenv(), oh boy

Re:Getaddrinfo() on glibc calls getenv(), oh boy by nomadluap on Monday October 16, 2023 @10:49PM (#37909929)

For one thing, it could delegate to a local service. Granted, the communication to this service is probably still be over a socket interface, but at least as a purely-local connection you would hopefully have some better worst-case performance characteristics.

This is basically what dnsmasq does when you use it as a local DNS cache.

[ Parent | on HN ]

Re:Getaddrinfo() on glibc calls getenv(), oh boy by kccqzy on Monday October 16, 2023 @11:20PM (#37910161)

Completely agree. Just use systemd-resolved which is the recommended way of doing DNS anyway.

[ Parent | on HN ]

Re:Getaddrinfo() on glibc calls getenv(), oh boy by guappa on Tuesday October 17, 2023 @03:25AM (#37911659)

And how do you communicate with systemd-resolved?

[ Parent | on HN ]

Re:Getaddrinfo() on glibc calls getenv(), oh boy by mambru on Tuesday October 17, 2023 @05:16AM (#37912394)

Via DBus:

https://www.freedesktop.org/software/systemd/man/org.freedes...

[ Parent | on HN ]

Re:Getaddrinfo() on glibc calls getenv(), oh boy by guappa on Tuesday October 17, 2023 @09:27AM (#37914692)

dbus is just a protocol that needs something else to actually transfer the data.

Normally, that's a socket in /run/dbus/system_bus_socket

[ Parent | on HN ]

Re:Getaddrinfo() on glibc calls getenv(), oh boy by kccqzy on Tuesday October 17, 2023 @01:09PM (#37918176)

And guess what. A UNIX socket does not use DNS or the damned getaddrinfo() function that's the ire of the article.

[ Parent | on HN ]