It's been pretty flaky from here in the US too (at least from NY).
But I was eventually able to commit some things yesterday.
On Tue, Apr 29, 2008 at 06:07:00PM +0100, Chris Withers wrote:
Hey All,
Can't contact svn.zope.org, it dead?
cheers,
Chris
--
Simplistix - Content Management,
There still appear to be some outstanding dns issues...
Chris
Wichert Akkerman wrote:
Is something happening with svn.zope.org? I haven't been able to use
anonymous or authorized svn for two days.
Wichert.
--
Simplistix - Content Management, Zope Python Consulting
-
Did svn.zope.org move to a new server? If so and if if someone knows the
new IP address I can stick it in my /etc/hosts for now.
Wichert.
Previously Chris Withers wrote:
There still appear to be some outstanding dns issues...
Chris
Wichert Akkerman wrote:
Is something happening with
I did a bit of checking: zope.org has a crazy number of DNS servers
and they are not all in sync. Particularly
seconly.rackspace.com (69.20.0.180) and cabana.palladion.com
(64.34.177.88) are not authorative for the zope.org domain and will just
refer back to the root servers.
This shows some
On 12 Oct 2006, at 09:32, Wichert Akkerman wrote:
I did a bit of checking: zope.org has a crazy number of DNS servers
and they are not all in sync. Particularly
seconly.rackspace.com (69.20.0.180) and cabana.palladion.com
(64.34.177.88) are not authorative for the zope.org domain and will
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12 Oct 2006, at 09:36, Justizin wrote:
That record comes from zoneedit.com, noone should be using those
servers for lookups AFAIK because zoneedit.com is not authoritative
for the NS records.
These are slaves which have not coordinated with me