# [EMAIL PROTECTED] / 2002-10-14 20:02:11 +0100:
> I've got named configured as a caching nameserver in a sandbox on my
> gateway as per the Handbook. However when I run nslookup on other
> machines on my network, I get this:
> # nslookup
> Server:
> Address: upstream NS IP>
>
> *** can't fi
On Mon, Oct 14, 2002 at 09:30:51PM +0100, Stacey Roberts wrote:
> >From what I've learnt here, it would seem as if I've not thought this
> one out completely, and haven't got the "right kind" of nameserver
> set-up.
Not yet, but you're 90% of the way there.
> You mentioned that it'd be better t
Hi Ceri,
Thanks for getting back to me (Nick as well!), and sorry about the
"top-post" for this one.
>From what I've learnt here, it would seem as if I've not thought this
one out completely, and haven't got the "right kind" of nameserver
set-up.
You mentioned that it'd be better to explain w
On Mon, Oct 14, 2002 at 08:02:11PM +0100, Stacey Roberts wrote:
> Hi,
> I thought I had this one licked, but I may have ommited some step that
> I'd like to get some info on, please.
>
> I've got named configured as a caching nameserver in a sandbox on my
> gateway as per the Handbook. However
On 14 Oct 2002, Stacey Roberts wrote:
> Hi,
> I thought I had this one licked, but I may have ommited some step that
> I'd like to get some info on, please.
>
> I've got named configured as a caching nameserver in a sandbox on my
> gateway as per the Handbook. However when I run nslookup on oth
Hi,
I thought I had this one licked, but I may have ommited some step that
I'd like to get some info on, please.
I've got named configured as a caching nameserver in a sandbox on my
gateway as per the Handbook. However when I run nslookup on other
machines on my network, I get this:
# nslookup
