internet explorer cannot open the site, so it says
steven l.
> On 10 Jan 2003 00:53:30 -0600, sierrat...@aol.comnojunk (Steven
> That is only because you have the wrong name now.
> chicago.us.mensa.org is a web page on another server.
>
> Try news.chicago.us.mensa.org
>
> That works as I am connected right now.
Well, on vax/vms, I typed
news/netser=chicago.us.mensa.org/netpro=tcpip
and I got the whole mensa hierarchy.
>
> Mary
>
>
>
>>steven l.
>
--
Cindy Smith I have further observed under the sun that
c...@dragon.com The race is not won by the swift,
c...@5sc.net Nor the battle by the valiant;
c...@romancatholic.org Nor is bread won by the wise,
Me transmitte sursum, Nor wealth by the intelligent,
Caledoni! Nor favor by the learned.
A Real Live Catholic For the time of mischance comes to all.
in Georgia! -- JPS Ecclesiastes 9:11
There seems to be some confusion between browser access (port 80 and 443)
and newsreader access (port 119)
My browser brings up http://chicago.us.mensa.org as a web page on port 80.
My browser does not bring up http://news.chicago.us.mensa.org as a web page
on port 80.
My browser brings up https://mailman.mensa.org/listinfo/mensa-talk-misc as a
secure web page on port 443.
My newsreader Outlook Express can currently access both
news.chicago.us.mensa.org and chicago.us.mensa.org on port 119.
(chicago.us.mensa.org:119 will probably become unavailable)
They are on three different IP addresses and port numbers
C:\>ping news.chicago.us.mensa.org
Pinging mail.chicago.us.mensa.org [207.252.248.9] with 32 bytes of data:
Reply from 207.252.248.9: bytes=32 time=266ms TTL=227
C:\>ping chicago.us.mensa.org
Pinging chicago.us.mensa.org [216.234.238.139] with 32 bytes of data:
Reply from 216.234.238.139: bytes=32 time=250ms TTL=42
C:\>ping mailman.mensa.org
Pinging newserver.mensa.org [216.234.247.242] with 32 bytes of data:
Reply from 216.234.247.242: bytes=32 time=250ms TTL=42
> In article <eas02vsccuopjgc9h...@4ax.com>,
> Mary <devnull@.us.mensa.org> writes:
>
>> On 10 Jan 2003 00:53:30 -0600, sierrat...@aol.comnojunk (Steven
>> L.) wrote:
>>
>>>>
>>>> The link works for me at home on a private ISP, and at work on the
>>>> State network using IE 5.5 and 6.0.
>>>>
>>>
>>> internet explorer cannot open the site, so it says
>>>
>>
>> That is only because you have the wrong name now.
>> chicago.us.mensa.org is a web page on another server.
>>
>> Try news.chicago.us.mensa.org
>>
>> That works as I am connected right now.
>
> Well, on vax/vms, I typed
> news/netser=chicago.us.mensa.org/netpro=tcpip
>
> and I got the whole mensa hierarchy.
Then your DNS is not refreshing properly. Chicago.us.mensa.org points to
216.234.238.139 now.
207.252.248.9 or 207.252.248.102 are the valid addresses for getting news,
currently.
Steve
>> Mary
>>
>>
>>
>>> steven l.
>>
I'm on chicago.us.mensa.org right now (that's what I'm currently reading and
posting on).
--
"This is my father's favorite medical text book. Read it long enough
and it will show you the error of your ways" - Charity Trask, "Dark
Shadows"
>> Then your DNS is not refreshing properly. Chicago.us.mensa.org
>> points to 216.234.238.139 now.
>>
>> 207.252.248.9 or 207.252.248.102 are the valid addresses for getting
>> news, currently.
>
> I'm on chicago.us.mensa.org right now (that's what I'm currently reading and
> posting on).
I'll be happy to repeat myself. If you're getting a news reader to connect
to the name chicago.us.mensa.org, then the DNS you're using has very old
information cached.
What IP address does your DNS return for chicago.us.mensa.org? More
specifically, what DNS servers are you using?
Steve
The IP I get (when I do a ping) is 207.252.248.9 and the DNS servers I'm
using are the AT&T Broadband servers.
I don't know how often they update their DNS list, but I think it's
somewhere around 24 hours because whenever I need to change the DNS entry
for my website, they usually have it changed on their servers within 24
hours.
Okay, no need to yell. I got it now. :)
> Switch the name or as soon as the cauche clears, you will not be able
> to connect. (Bad cauche if it is a week old).
So why did the IP in the DNS entry get changed for the chicago.us.mensa.org?
>From what you're saying you're going to (or, have already) delete that
address, but the IP change (to chicago.us.mensa.org) indicates that someone
changed the IP on the DNS entry, and then presumably (from what you're
saying) deleted it at some point. Why not just delete the entry in the first
place, thereby elimating the cache problem (if it's deleted, all updated DNS
lists won't have the URL, and any old caches will have the old IP, no longer
valid)? Also, is there a problem with keeping the old DNS entry?
Not that it helps in any way, since I'm not a Mensa member, but I'm just
curious.
How can you be sure from where you sit? *My* DNS has updated, and yet I see
new posts, with chicago.us.mensa.org as my newsreader's server. I've even
gotten a post through, with this setup. I've changed to
news.chicago.us.mensa.org with no visible effect, then back. Ping here shows
the ipas that Steven listed. Don't assume that Feek is an idiot, when he's
clearly demonstrated that he isn't. Sometimes things aren't working the way
you think they are.
Joseph
however even the change is not propagating in the expected way. it is
the 16th and i have posted successfully to the old "address" at
mensa.t...@chigago.us.mensa.org today and it even appeared after
approval (if approval is still in issue).
Joseph
Feek O'Hanrahan wrote:
joseph
Joseph
--
Cole's Axiom: The sum of the intelligence on the planet is a constant.
The population is growing.
Rian
"Joseph" <jose...@bigvalley.net> schreef in bericht
news:3E27AB99...@bigvalley.net...
My posts aren't showing up immediately. It still looks moderated to me.
To conveniently know what ipa your DNS has for a machine, in Win* (using a
"DOS" window) or *nix (from a shell) just use "ping". For instance, my
earlier message elsethread was after opening a DOS window and typing "ping
chicago.us.mensa.org", getting the 216 ipa, then typing "ping
news.chicago.us.mensa.org" and getting the 207 ipa (and the name
"mail.chicago.us.mensa.org"). This connection got me the 207 for both.
Apparently, depending on what server I get when I connect to NetZero, I
either get an updated DNS or one that has the old addresses. I'm tempted to
disconnect/reconnect/test until I get an updated one again, and see if the
216 machine still works. Too much trouble, though.
"Joseph" <jose...@bigvalley.net> wrote in message
news:3E27AA2B...@bigvalley.net...
Joseph
> Path:
> chicago.us.mensa.org!mtm.mensa.org!robomod!not-for-mail
> From:
> Joseph <jose...@bigvalley.net>
> Newsgroups:
> mensa.talk.misc
> Subject:
> Re: MTM going Jan 5
> Date:
> 17 Jan 2003 01:10:39 -0600
> Organization:
> Chicago Area Mensa
> Lines:
> 33
> Sender:
> maild...@news.chicago.us.mensa.org
> Approved:
> mensa-t...@newsgate.mensa.org
> Message-ID:
> <3E27AB99...@bigvalley.net>
> References:
> <hagj1v4lhu84c02li...@4ax.com>
> <20030110013953...@mb-mw.aol.com>
> <eas02vsccuopjgc9h...@4ax.com>
> <tokeB1...@cygnus.dragon.com>
> <BA4650ED.7AB0%slevi...@spamstinks.chicago.us.mensa.org.spamstinks>
> <avrdti$l...@chicago.us.mensa.org> <ejt52vspb8l9dt4lb...@4ax.com>
> <avurso$b...@chicago.us.mensa.org>
> Reply-To:
> joseph2...@KillSpambigvalley.net
> NNTP-Posting-Host:
> 207.252.248.9
> Mime-Version:
> 1.0
> Content-Type:
> text/plain; charset=us-ascii
> Content-Transfer-Encoding:
> 7bit
> X-SCRM-Policy:
> http://www.mensa.org/newsgroups
> X-SCRM-Info-1:
> Send submissions to mensa-t...@chicago.us.mensa.org
> X-SCRM-Info-2:
> Send technical complaints to mtm-...@chicago.us.mensa.org
> X-SCRM-Info-3:
> Send complaints about policy to mtm-...@chicago.us.mensa.org
> X-Comment:
> moderators do not necessarily agree or disagree with this article.
> X-Robomod:
> STUMP, ich...@algebra.com (Igor Chudov), C++/Perl/Unix Consulting
> X-Accept-Language:
> en