This is kind of silly, but:

I just started running ntpd on tick.mattnordhoff.com in Dallas. Are any of you running an NTP server nearby? Do you mind if I configure my ntpd to sync from it?

(Actually, I know someone is, cuz I saw it in the pool, but I feel like getting someone's email address from whois and emailing him just for this would be kind of creepy. )

Edit (2011-03-28T15:41Z): I don't actively maintain this post. You should check my website or the internal services wiki page for current information. For example, one of the IPs listed below is deprecated, though it still works.

Edit (2009-06-14T13:31:35Z): To be more clear, here's a (partial) list of what it's available at:

• tick.mattnordhoff.com / 67.18.187.111, 2001:470:1f0f:b4::123:1
• ipv4.tick.mattnordhoff.com (IPv4-only)
• ipv6.tick.mattnordhoff.com (IPv6-only)
• private.tick.mattnordhoff.com / 192.168.130.4 (Dallas private network)
• NTP pool stats: IPv4, IPv6 (though the NTP pool site doesn't support IPv6 servers)

It's open access; just don't burn through my bandwidth or DoS me, etc.

IPv6 is through an HE tunnel, but I've got very low latency to the tunnel server.

Edit (2009-06-14T17:06:32Z): I put up a web page listing my NTP servers. (Well, currently just server, since there's only this one.)

_________________
Matt Nordhoff (aka Peng on IRC)

I just added tick.mikeshoup.com to the pool. The server is on dallas150. You're welcome to synch off of it, though give it a day or so for the time on it to stabilize.

Yay, thanks.

Since I didn't make it clear, anyone can feel free to use my server as well. As long as you're not horribly abusive or whatever. It has more or less stabilized by now.

I just added myself as time.jedsmith.org. Not in Dallas, but Fremont.

I have it set to sync to all Stratum 1 servers with extremely low latency, so depending on how this bandwidth works out, I might consider opening it up as a Stratum 2. I'm not using the bandwidth anyway.

Sooo...you'd be fine if I used it, right?

Forgot to mention, if you guys are running kernel 2.6.18, be sure to set clock independent from the host.

Set the sysctl,
xen.independent_wallclock=1

Absolutely, knock yourself out! I woke up to a 16.3 this morning, so it would appear that I am evened out. I synced fast with the quick latency to Hurricane's Stratum 1 servers.

My traffic's already picking up, too, finally I can use more than 0% of my bandwidth in a month :D

From your wording, I'm assuming that doesn't apply to pv_ops kernels?

I have no idea.

I was having the problem where my clock would get set back to host time.

I would think with the pv_ops kernels, since they drift on their own, they're not synchronized to host time and it doesn't matter.

time.jedsmith.org is now a Stratum 2 source: http://support.ntp.org/bin/view/Servers/TimeJedsmithOrg
Pool statistics: http://www.ntppool.org/scores/64.62.228.129

Feel free to sync against it. Fellow Linode customers get $10 off an annual subscription to UDP packets!

The xen sysctls don't exist on pv_ops, so whether or not you need to make the clock independent, you can't do it that way. The pv_ops kernels are known for drifting, so whether or not they should be independent, it seems they are.

Added its IPv6 address to the pool! http://www.ntppool.org/scores/2001:470:1f0e:68a::2