Your message dated Sun, 29 Mar 2015 05:57:22 +0200
with message-id <[email protected]>
and subject line Re: Bug#761658: Please do not default to using Google
nameservers
has caused the Debian Bug report #761658,
regarding Please do not default to using Google nameservers
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
761658: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761658
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 215-3
Severity: wishlist
From a cursory look over the sources, I am led to believe that
resolved defaults to using Google nameservers.
I would like to propose that we either provide no default fallback,
or chose to support OpenNIC that way.
Thank you for your consideration.
-- Package-specific info:
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages systemd depends on:
ii acl 2.2.52-2
ii adduser 3.113+nmu3
ii initscripts 2.88dsf-53.4
ii libacl1 2.2.52-2
ii libaudit1 1:2.4-1
ii libblkid1 2.20.1-5.8
ii libc6 2.19-11
ii libcap2 1:2.24-4
ii libcap2-bin 1:2.24-4
ii libcryptsetup4 2:1.6.6-1
ii libgcrypt11 1.5.4-3
ii libkmod2 18-1
ii liblzma5 5.1.1alpha+20120614-2
ii libpam0g 1.1.8-3.1
ii libselinux1 2.3-2
ii libsystemd0 215-3
ii sysv-rc 2.88dsf-53.4
ii udev 208-8
ii util-linux 2.20.1-5.8
Versions of packages systemd recommends:
ii dbus 1.8.6-2
ii libpam-systemd 215-3
Versions of packages systemd suggests:
pn systemd-ui <none>
-- no debconf information
--
.''`. martin f. krafft <[email protected]> @martinkrafft
: :' : proud Debian developer
`. `'` http://people.debian.org/~madduck
`- Debian - when you have better things to do than fixing systems
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
--- End Message ---
--- Begin Message ---
Control: tag -1 wontfix
On Sep 15, martin f krafft <[email protected]> wrote:
> From a cursory look over the sources, I am led to believe that
> resolved defaults to using Google nameservers.
From resolved.conf(5):
Any per-interface DNS servers obtained from
systemd-networkd.service(8) take precedence over this setting, as do
any servers set via DNS= above or /etc/resolv.conf. This setting is
hence only used if no other DNS server information is known.
> I would like to propose that we either provide no default fallback,
> or chose to support OpenNIC that way.
This default is not used as long as a resolver has been configured by
the system administrator or provided by DHCP, and I see no value in
allocating development time to break cases which currently work by
removing support for a default.
Since the Google resolvers are a very reliable widely anycasted service
which third parties are encouraged to use they actually look like a sane
fail-safe default, hence I am closing this bug.
--
ciao,
Marco
pgp_pVwSrqqPk.pgp
Description: PGP signature
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
