Path: csiph.com!aioe.org!.POSTED!not-for-mail From: Rod Pemberton Newsgroups: comp.lang.forth Subject: Re: Forth.org status Date: Fri, 17 Feb 2017 19:25:27 -0500 Organization: Aioe.org NNTP Server Lines: 27 Message-ID: <20170217192527.26c97a67@_> References: NNTP-Posting-Host: ZTD62cW/Uw8bymX5ok+0NA.user.gioia.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org X-Notice: Filtered by postfilter v. 0.8.2 Xref: csiph.com comp.lang.forth:54946 On Fri, 17 Feb 2017 11:14:32 -0800 (PST) Julian Fondren wrote: > On Friday, February 17, 2017 at 10:34:02 AM UTC-6, Cecil - k5nwa > wrote: > > I see that forth.org is no longer resolved to a valid address. So > > does anyone know if it's temporary or are they gone for good? > > The registered nameservers don't resolve forth.org to anything. One > of them is ns1.taygeta.com, which responds to pings at > but doesn't respond to DNS queries. > > So forth.org is probably down intentionally. Or it's down > deliberately but it was too much trouble to ask Metron Computerware > to update their DNS records. Various DNS servers are still returning 206.55.232.90 for forth.org. However, all ports are currently closed. It always seems to come back online though ... Rod Pemberton -- All it takes for humanity to conquer the world's toughest problems is to hope, to believe, to share, and to do, in cooperation.