From: franciscojose ballesteros <nemo.mbox@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] lsub.org seems down
Date: Sat, 3 Jul 2010 10:39:09 +0200 [thread overview]
Message-ID: <-6542783778117336437@unknownmsgid> (raw)
In-Reply-To: <AANLkTily9sdjqmi4QPN3HRUGeaGvrlSxtLPzjWdD6nvn@mail.gmail.com>
The power is down. It should be ok
on monday.
On Jul 3, 2010, at 4:11 AM, "Razvan Musaloiu-E." <razvan@musaloiu.com> wrote:
> On Fri, Jul 2, 2010 at 6:29 PM, Scott Sullivan <scott@ss.org> wrote:
>> At the time of this writing I've been unable to reach lsub.org for the
>> latter half of the day.
>>
>> DNS resolution is failing so I can't conduct a traceroute.
>> 'dig' returns no results, and I verified against:
>> http://downforeveryoneorjustme.com/lsub.org
>>
>> Does anyone have any additional information?
>>
>
> The nameservers are probably colocated. None of them seems to be up.
>
> $ host -t NS -v lsub.org 199.19.56.1
> Trying "lsub.org"
> Using domain server:
> Name: 199.19.56.1
> Address: 199.19.56.1#53
> Aliases:
>
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 27644
> ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 2
>
> ;; QUESTION SECTION:
> ;lsub.org. IN NS
>
> ;; AUTHORITY SECTION:
> lsub.org. 86400 IN NS ns2.lsub.org.
> lsub.org. 86400 IN NS ns1.lsub.org.
>
> ;; ADDITIONAL SECTION:
> ns1.lsub.org. 86400 IN A 212.128.4.205
> ns2.lsub.org. 86400 IN A 193.147.71.86
>
> Received 94 bytes from 199.19.56.1#53 in 68 ms
>
> -- Razvan ME
>
prev parent reply other threads:[~2010-07-03 8:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-03 1:29 Scott Sullivan
2010-07-03 2:11 ` Razvan Musaloiu-E.
2010-07-03 8:39 ` franciscojose ballesteros [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=-6542783778117336437@unknownmsgid \
--to=nemo.mbox@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).