Re: NSLOOKUP don't work

To: debian-user@lists.debian.org
Subject: Re: NSLOOKUP don't work
From: Rob Browning <rlb@cs.utexas.edu>
Date: 26 Jul 1997 03:45:22 -0500
Message-id: <[🔎] 87wwmetd5p.fsf@nevermore.csres.utexas.edu>
In-reply-to: Alex Yukhimets's message of "Tue, 15 Jul 1997 10:54:18 -0400 (EDT)"
References: <[🔎] m0wo8za-000F9eC@alex>

Alex Yukhimets <aqy6633@is5.nyu.edu> writes:

> Before that, I would recommend to change 127.0.0.1 to the address of
> some different nameserver though. You shoud not run your own NS without
> real need.

Depends.  If you're running over a slow link, bind's DNS lookup
caching can help speed up network operations quite a bit.  Note that
you may want to set up forwarders in this case.

-- 
Rob

--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-user-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .

Reply to:

References:
- Re: NSLOOKUP don't work
  - From: Alex Yukhimets <aqy6633@is5.nyu.edu>

Prev by Date: Re: Can you talk to a enet device with just the hardware address?
Next by Date: inn upgrade kills innd!
Previous by thread: Re: NSLOOKUP don't work
Next by thread: Re: NSLOOKUP don't work
Index(es):
- Date
- Thread