Conversation

Notices

1. Embed this notice
   Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Thursday, 11-Jan-2024 01:18:17 JST Haelwenn /элвэн/ :triskell:

   • miauz genyau
   @mia I'd also say that *all* machines should have a caching DNS server, even if it's just going to forward to an external DNS server, because then any DNS query is going to be fast, regardless of how your program deals with DNS.
   
   I think some distros do this via dnsmasq with some level of integration for desktops, here I just put unbound everywhere, shitty captive portals be damned.
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Thursday, 11-Jan-2024 01:45:33 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • miauz genyau
     • Glitch

     @glitch @mia I think Windows also has a DNS resolver configuration, it's just either registry bullshit or a file hidden somewhere that basically nobody remembers (like how Windows also has the same file as /etc/hosts but at another location).
     And yes, /etc/resolv.conf is what programs on Unixes use to do DNS resolution, it can correspond to the network you're in with the DHCP client mangling it, but it doesn't have to.

   • Embed this notice
     Glitch (glitch@pl.glitch.pm)'s status on Thursday, 11-Jan-2024 01:45:35 JST Glitch

     in reply to

     • miauz genyau
     @lanodan @mia iirc on some distros this is the default moreso because DNS resolution on Linux isn't determined by what network you're connecting to (like it is on Windows/Mac), but is instead just handled by a simple resolv.conf file.
     
     If you're not using systemd (which messes with resolv.conf via NetworkManager) its usually easier to shoe in dnsmasq and rely on it instead for something more advanced than "set an IP and forget".
   • Embed this notice
     Glitch (glitch@pl.glitch.pm)'s status on Thursday, 11-Jan-2024 01:51:22 JST Glitch

     in reply to

     • miauz genyau
     @lanodan @mia windows' DNS resolution is integrated with the network configuration panel if memory serves me right (which means it dumps things in the registry)
     
     And yeah, it's specifically because the DHCP client mangles resolv.conf that some distros sub in something like Dnsmasq - it's easier to just override it with 127.0.0.1 in all applications and then redirect it to what's needed than trying to untangle which part of the stack set the DNS *this time*.
     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Thursday, 11-Jan-2024 02:23:00 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • miauz genyau
     • Ignas Kiela
     @ignaloidas @mia systemd-resolvd? Not all systems are using it by default, even with using systemd-the-init. (systemd being something you can pick bits and pieces from)
   • Embed this notice
     Ignas Kiela (ignaloidas@not.acu.lt)'s status on Thursday, 11-Jan-2024 02:23:01 JST Ignas Kiela

     in reply to

     • miauz genyau

     @lanodan@queer.hacktivis.me @mia@movsw.0x0.st I'm pretty sure systemd has one by default?