Conversation

Notices

1. Embed this notice
   Hugo 雨果 (whynothugo@fosstodon.org)'s status on Sunday, 21-Dec-2025 10:42:28 JST Hugo 雨果

   in reply to

   • Willow

   @stacyharper I like the idea of it. Are this kind of "configuration packages" generally acceptable upstream?

   • Embed this notice
     Hugo 雨果 (whynothugo@fosstodon.org)'s status on Sunday, 21-Dec-2025 10:42:28 JST Hugo 雨果

     in reply to

     • Willow

     @stacyharper Tangential: I don't like resolvconf at all: it blindly trusts any DNS server provided and terrible fit for any network where you don't have absolute trust on every other host on the network.

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Willow (stacyharper@soc.punktrash.club)'s status on Sunday, 21-Dec-2025 10:42:29 JST Willow

     in reply to
     @whynothugo Maybe we could try to upstream this kind of package:
     
     https://git.sr.ht/~stacyharper/personal-aports/tree/main/item/stacy/mdns
   • Embed this notice
     Hugo 雨果 (whynothugo@fosstodon.org)'s status on Sunday, 21-Dec-2025 10:42:30 JST Hugo 雨果

     Configuring #alpine to resolve .local domains via mDNS was far simpler: https://whynothugo.nl/journal/2025/12/16/resolve-.local-mdns-domains-via-avahi-using-unbound/

     Also dirtier than I expected. We need dedicated mDNS<>DNS bridges without so many moving parts.