[Xitami] FW: Website using Xitami

Spyman xitami@lists.xitami.org
Wed, 9 Jan 2002 19:23:12 -0500


By name or number. I had them try both.

I have had a few people try and hit the site since I sent the first email
and no one has successfully connected.

They are showing up in the Wallwatcher log and in the Xitami access log.

I usually keep the same ip for approximately two-three days. I haven't kept
full track. Only the one minute check time is when the server is not
available during this change. One of the people that can connect hit during
that minute once but waited and was able to get in right after TZO actually
updated.

-----Original Message-----
From: xitami-admin@lists.xitami.org
[mailto:xitami-admin@lists.xitami.org]On Behalf Of Paul Reid
Sent: Wednesday, January 09, 2002 7:14 PM
To: xitami@lists.xitami.org
Subject: Re: [Xitami] FW: Website using Xitami


> Is a static ip necessary? I use TZO

Nice but not necessary. Using TZO to associate your name address to your
hopping IP number will give momentary glitches, but works well for many
people.

In particular: if someone hits right after your IP number changes, they
won't
connect until TZO gets updated. Since you say "checks it once a minute",
that
should never leave you invisible for long.

A bigger issue, and I am not sure how this works, is that various ISPs may
cache DNS records on their own DNS servers rather than keep going to a DNS
server in authority. That's standard practice, the authoritative DNS record
can give a suggested time of updating, and I suppose TZO must be setting
their
update suggestion shorter than a DNS system full of hard-wired "permanent
IP"
machines like mine. But other ISP DNS servers are free to ignore it, and use
cached DNS records as long as they want.

>  Ping and tracert

By name, I assume. What happens if you call them on the phone, tell them the
IP number you are on at that moment, and they ping that number? i.e. is it a
DNS issue or is your IP number just not reachable?

FWIW: ping 66.32.68.16 at 7:10 PM EST fails for me; tracert stops tracking
after three hops inside MindSpring. Omitting known route through my campus
routers and my usual ALTER.NET backbone routers:

 16    195.ATM4-0.GW6.ATL3.ALTER.NET [146.188.233.217]
 17    foundry-86-p3-2.atl2.mindspring.net [157.130.29.194]
 18    foundry-22-ve3.atl2.mindspring.net [207.69.223.163]
 19    redback-1-e2-0.atl2.mindspring.net [207.69.143.4]
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *     ^C

 -PRR

--
Xitami Users Mailing List -- For Xitami support
To unsubscribe: http://lists.xitami.org/mailman/listinfo/xitami