systemd-timesyncd contains a compiled-in list of fall-back NTP servers. These should be set to some sensible defaults. `./configure` without setting time-servers pass issues the warning:

  *** Using Google NTP servers.
      Do not ship OSes or devices with these default settings.
      See DISTRO_PORTING for details!

I checked <http://svnweb.mageia.org/packages/cauldron/systemd/releases/230/3.mga6/SPECS/systemd.spec?revision=1037339&view=markup> and did not find NTP servers to be configured there.

Proposed solution
====================

Mageia should register a "vendor" zone at ntp.org. (e.g 0.mageia.pool.ntp.org) CoreOS seams to have done this, <see https://github.com/systemd/systemd/issues/437#issuecomment-117430662>

From <http://www.pool.ntp.org/en/vendors.html#open-source>:

    Open Source projects are of course particularly welcome to use the pool
    in their default setup, but we ask that you get a vendor zone when
    using the pool as a default configuration.

Applying for a vendor zone seams to be *very* simple, see <http://www.pool.ntp.org/en/vendors.html#vendor-zone>

(Side-note: We could use this pool as default then in all NTP configurations, too)

Rational
==============

Related discussion about which NTP servers to use as default:
<https://github.com/systemd/systemd/issues/437>.

The discussion main points are:
- google does not permit using it's time server
- google time servers are not quite reliable anyway
- systemd was changed to require(?) some default time-servers to be set when
  compiling
- Open source projects can register a "vendor" pool at ntp.org.


This bug is related to bug 19113, which is about drakxconfig not configuring (non-fall-back) NTP servers for systemd-timesyncd.