Erik Hatcher wrote:
Yes, I'm also experiencing spotty DNS issues with lucene.apache.org -
I can browse to it through the web, but my e-mail server cannot send
to the new e-mail lists (for svn commits and PMC only right now).
Shouldn't DNS updates be quicker than this? It's been a week since it
Hello All,
I'm not sure what's going on here, but of the four nameservers for
apache.org (ns1.us.bitnames.com, ns1,eu.bitnames.com, ns.hyperreal.org
and ns2.surfnet.nl) only the last two know about lucene.apache.org. If
the two bitnames.com DNS servers haven't spotted the existence of
luce
Erik Hatcher wrote:
I've seen that too it worked fine for a while, and then no
longer. I thought it might be a temporary DNS thing.
I think it is. The DNS does take a little while to settle down when a
new name appears: it's only just appeared in my ISP. When I was
managing my (old) com
If you'll excuse me just diving in, but my own experiences are relevant
here:
Otis Gospodnetic wrote:
Any such custom hack requires maintenance, even
if it's auto-generated.
The corollary of which is that if the version number is in two places,
one of them will be wrong.
jch
---
