Slashdot Mirror


D-Link Settles Danish Time Dispute

igb writes "The Register reports that DLink has settled the time server dispute described a little over a month ago here on Slashdot. They're going to stop using an NTP server they're not really authorized to chime with, and they've reached an amicable settlement over the use by existing products. The details of the settlement are, not unsurprisingly, somewhat vague, but let's hope that the good guys aren't out of pocket any more."

2 of 192 comments (clear)

  1. Re:Netgear did the same thing a few years ago by wowbagger · · Score: 5, Informative
    It it's because they are clueless or they are cheap?


    Yes, and yes. They are clueless, and they are cheap.

    That is why pool.ntp.org was created - to provide a pool of NTP servers that these bozos can use without hammering anybody's server too badly.
  2. Re:Netgear did the same thing a few years ago by MikeBabcock · · Score: 5, Informative

    These situations make no sense to me. The NTP system is very easy to use properly.

    There's a great little website about how to use ntp.org servers properly.

    For the quick-fix people, point your NTP capable system at pool.ntp.org.

    If you live in north america, you can use the north-america.pool.ntp.org dns name instead, for only north american servers. The same applies to other continents and several country codes.

    Basically, there's no excuse for hard-coding a time server in almost any situation, unless your client is completely incapable of DNS and has no access to external DNS servers.

    --
    - Michael T. Babcock (Yes, I blog)