🚀 go-pugleaf

In article <40osh1$d5v@sake.wwa.com>,
   bobzim@metaworld.com (Bob Zimmerman) wrote:
>In article <40olvr$kl9@Venus.mcs.com>, karl@MCS.COM (Karl Denninger) wrote:
>
>>
>>No, the problem is that WWA's nameserver had (and may still have) old cache 
>>data.
>>
>>Of course, if you called WWA and asked them to look into this, they could
>>have reloaded the nameserver and fixed it.
>>
>>We have *not* blocked anyone from access to our web server.   In fact, its 
>>darn difficult to do the way our network is architected without seriously
>>impacting performance for everyone.
>>
>>We are not responsible for nameserver caches on other systems, only on 
>>our own.  We've made a number of changes in the web server architecture, 
>>and this has involved moving the www.mcs.net address (twice in fact).
>>
>>The proper course of action for other ISP customers who experience this kind
>>of thing is to contact *your ISPs* tech desk.  They can answer these
>>questions and take care of the problem.
>>
>
>One other note that has nothing to do with WWA's (or anyone elses 
nameserver), 
>that MCS is not supporting www.mcs.com anymore. They will only support 
>www.mcs.net... According to a post, www.mcs.com was never supported 
>
>So if you have bookmarks or URLs pointing to the www.mcs.com, you will need 
to 
>update them to use www.mcs.net... this may also solve problems (once the 
>nameservers caches are refreshed)...
>
The www.mcs.com was a typo. The URLs I have in my bookmarks are all 
www.mcs.net. Anyway, I noticed access was restored to the MCS web pages this 
morning on or before 9:00 am.

Coincidently, on the previous occassion when I posted loss of access to the 
MCS web pages in chi.internet, access was restored in less than one day.


_____________________________
Murray Arnow (marnow@wwa.com)