From: "Darrell Shandrow" <nu7i@azboss.net>
To: <speakup@braille.uwo.ca>
Subject: Re: dns problem
Date: Mon, 14 Oct 2002 05:58:01 -0700 [thread overview]
Message-ID: <000901c27381$56df5ed0$0201a8c0@NU7I> (raw)
In-Reply-To: <20021014102531.GA13750@lrxms.net>
Hi Scott,
You can ping me. Ping borg.shandrow.com, or the IP address 206.124.184.77.
Check your /etc/named.conf carefully. Look for the zone file that is named
just ".". Make sure that really does point to a valid root servers hints
file...
----- Original Message -----
From: "Scott Howell" <showell@lrxms.net>
To: <speakup@braille.uwo.ca>
Sent: Monday, October 14, 2002 3:25 AM
Subject: Re: dns problem
> Greg,
>
> That very well could be the problem. I am running bind 8.something on my
> old box and bind 9 on the new box. I simply used the same configuration
> file with a few minor changes to paths etc. Being that I can't contact
> any root servers, that probably would indicate there being some problem
> with the configuration.
> What is interesting is that at one point it seem to work, but to be
> honest I haven't absolutely any clue what would have broken in such
> short order. I think what compounds the problem is I can't think of
> anything to ping beyond my own network just to be sure my packets are
> flowing as they should be. Yes, I can use netwatch, but it tends to be a
> bit to verbose just to get some simple info. I used to be able to ping
> the ISP's dns server, but guess they decided to block pings now.<grin>
>
> Tnx will have to keep hacking this problem.
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
Scott Howell
` Gregory Nowak
` Scott Howell
` Gregory Nowak
` Scott Howell
` Jude DaShiell
` Scott Howell
` Igor Gueths
` Scott Howell
` Darrell Shandrow [this message]
` Gregory Nowak
` Darrell Shandrow
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='000901c27381$56df5ed0$0201a8c0@NU7I' \
--to=nu7i@azboss.net \
--cc=speakup@braille.uwo.ca \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).