[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Freetype] Re: DNS + list subscription
From: |
David Turner |
Subject: |
Re: [Freetype] Re: DNS + list subscription |
Date: |
Wed, 15 Nov 2000 16:18:28 +0100 |
Hi Tom,
>
> David,
>
> I can get to the www.freetype.org, but Apache returns a not found pge for the
> link listed in the "canned" footer that goes out with each list mailing. I
> think Pavel Kankovsky already pointed this out. It would seem that the list
> archive is not properly setup for the web server (or vice versa)... :(
>
OK, here are a few explanations on the setup:
- The new server is located at 193.251.34.63 (a.k.a. henzai.com by the way)
and contains the web pages + the mailman server. It is known as:
www.freetype.org, ftp.freetype.org, mail.freetype.org
- The old server is still at 193.154.213.72 (a.k.a. serveur.soremo.com)
and contains the web pages and ViewCVS, _not_ Mailman. It is know as:
cvs.freetype.org
If you DNS resolves to the old server, you won't be able to see the
Mailman pages. It seems these pages are working extremely well if
you connect the good server (and I'm speaking of the addresses given
in the mailing list footers).
The old machine also holds the primary DNS server for the freetype.org
domain. The secondary name server is ns.isdnet.net and ZoneCheck doesn't
report any bugs
I also noticed two strange facts:
- most people are able to send email to the new server, or even to
FTP from it. The problem only occurs with "www.freetype.org".
- on Windows NT, something strange happened yesterday. From the command
line:
C:>ping www.freetype.org => returned the old address 195.154.213.72
C:>ping ftp.freetype.org => returned the new address 193.251.34.63
C:>ping www.freetype.org => returned this time the _new_ address !!
// then launch Netscape or IE, it will find the new site..
The problem never occurs with Linux on the exact same network..
It seems that some caches, somewhere, are really, really broken.
As said before. I've fixed a bug in the zone file yesterday. Maybe
the cache haven't been updated yet in your area ??
Any ideas ?
- David