1. 48
  1.  

  2. 23

    Severity: serious

    1. [Comment removed by author]

      1. 4

        In your opinion what is a fast, reliable and secure alternative to Google’s DNS?

        1. 9

          There is no reasonable default DNS server. You should always use the DNS on your local network, which if you use DHCP or some other network autoconfiguration will be provided by that and otherwise must be configured by hand.

        2. 5

          Implicit defaults are essentially always the devil’s playground. The fact it’s Google adds insult to injury, of course.

        3. 1

          It’s too serious not to be!

        4. 15

          According to the thread, it’s not as bad as it sounds:

          1. resolved was not the default DNS daemon
          2. the config in question wasn’t a default config under /etc, but would have to be symlinked by the user/admin to be applied
          1. 2

            Thank you for digging that up. I can see this bug being from 2014 and that comment from 2015. Do you know if things have changed with recent releases from systemd ?

            1. 2

              I don’t know. I’m not affiliated with Debian, just someone reading a bug discussion while trying to relax a bit.

          2. 27

            I see the systemd tire fire continues to burn.

            1. 12

              It’ll burn as long as there’s flammable shit

            2. 9

              Sounds like a top notch friendly community!

              1. 4

                yeah, the debian community is known for being … specific.

              2. 7

                Reminds me of when Google asked them to stop using their timeservers as a default.

                1. 2

                  Although google seems to have changed their mind, since now they say you can use their servers.

                  1. 3

                    Cloud Platform changes a lot of things. It’s now useful to have the same smeared concept of time as Google since you’re interacting with storage systems which also have the same smeared time. Additionally I assume it means SREs support public NTP now vs. potentially a SWE team.

                    I still doubt they’d want it as the default time server for a distro.

                2. 4

                  Just when you thought it couldn’t get any worse…

                  1. 6

                    I suggested a title change for the link to add (2014) to it…

                    1. 2

                      Yes, the bug is from 2014, which makes it all the more “interesting” that it’s still not closed and got the “serious” tag in June 2017.

                    2. 3

                      What a stubborn and unfriendly position from the package maintainers. Not being a systems programmer / linux kernel guy I have no emotional draw for/against systemd, but any time I read any of these threads that bubble up I am left with a bad taste in my mouth. Although I suspect things are much, much worse in the closed-source OS dev teams (MS, Apple, etc)