Boost logo

Boost :

From: John Maddock (john_at_[hidden])
Date: 2006-10-26 04:40:24

Matt Doyle wrote:
> Well, here are some clues about the problem.
> First problem is in the dns configuration, and
> have different A records. resolves to and
> resolves to, that's wrong,
> should
> be the A record and should be an alias to the A record,
> there shouldn't be two different ip's. What this is going to give you
> is
> that depending where you're at and the mood of the NS you might get
> sent
> to 209 or 210, 209 generates an error message.

You're right: I updated, but not (as that was
apparently working at the time). They're both now pointing to where SF says
they should point (, so hopefully this issue will resolve

Many thanks for the diagnosis, John.

> Second problem is when I look up the registration for it
> lists as the primary NS however if I query that server
> directly it has no record of either url's so the NS can't resolve the
> discrepancy there either. This record needs to be updated to reflect
> the
> true primary name server.
> Hope this helps,
> Matt
>> -----Original Message-----
>> From: boost-bounces_at_[hidden]
>> [mailto:boost-bounces_at_[hidden]] On Behalf Of Jan Stetka
>> The error page I got gave the time at which I typed the URL
>> (different
>> because of time zone) so its not a browser refresh problem,
>> maybe your
>> browser didn't have a fresh copy. Anyhow its fixed now but it
>> was down
>> earlier.
>> Jeff Garland wrote:
>>> Jan Stetka wrote:
>>>> is still giving an error message, so
>> whatever john maddock
>>>> did last time, can he do it again. Also we need to find out what
>>>> un-fixed it!
>>> It's working for me. Maybe try refreshing your browser?
>>> Jeff
> Scanned by McAfee GroupShield {X3BTB534}
> _______________________________________________
> Unsubscribe & other changes:

Boost list run by bdawes at, gregod at, cpdaniel at, john at