🚀 go-pugleaf

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)...


-----
 Bob Zimmerman       ~  bobzim@metaworld.com ~  http://www.wwa.com/~bobzim/
 Ask me about Grep For Windows, or get it from my WWW page

 MetaWorld           ~  PO Box 261               ~  Grayslake, IL 60030
 info@metaworld.com  ~  http://www.metaworld.com ~  (708) 223-6753

 Internet Consulting, Training and Support
 World Wide Web Design and Consulting