From: forsyth@plan9.cs.york.ac.uk forsyth@plan9.cs.york.ac.uk
Subject: domain name services from unix?
Date: Thu, 24 Aug 1995 12:30:30 -0400 [thread overview]
Message-ID: <19950824163030.XZn_48quX4BNJs_MOKfHg_Ztx1jH8s2Q265pMAVuw_g@z> (raw)
yes, i quite agree, and that's what i usually do.
you can also import just /net/dns.
i'd assumed he might not (yet) have a CPU server,
but even so i ought to have mentioned it!
------ original message follows ------
>From cse.psu.edu!9fans-outgoing-owner Thu Aug 24 16:55:09 BST 1995
Received: by colossus.cse.psu.edu id <45565>; Thu, 24 Aug 1995 11:32:06 -0400
Received: from galapagos.cse.psu.edu ([130.203.2.12]) by colossus.cse.psu.edu with SMTP id <45691>; Thu, 24 Aug 1995 11:27:27 -0400
Received: from localhost by galapagos.cse.psu.edu with SMTP id <12709>; Thu, 24 Aug 1995 11:14:40 -0400
To: 9fans@cse.psu.edu
Subject: Re: domain name services from unix?
In-reply-to: Your message of "Thu, 24 Aug 1995 07:02:54 EDT."
<95Aug24.071351edt.45578@colossus.cse.psu.edu>
Date: Thu, 24 Aug 1995 11:14:27 -0400
From: Scott Schwartz <schwartz@galapagos.cse.psu.edu>
Message-Id: <95Aug24.111440edt.12709@galapagos.cse.psu.edu>
Sender: owner-9fans@cse.psu.edu
Precedence: bulk
Reply-To: 9fans@cse.psu.edu
forsyth@plan9.cs.york.ac.uk writes:
| the short answer to kiran's question is that he probably
| isn't running ndb/dns on the terminal.
I kind of like the idea of importing the cpu server's /net/cs to get
the nameserver. For one thing, that puts all the dns caching in one
place. There is the overhead of exports, but if you've got a
distributed system isn't it worth exercising it?
next reply other threads:[~1995-08-24 16:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-08-24 16:30 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-08-24 15:34 Kiran
1995-08-24 15:14 Scott
1995-08-24 11:02 forsyth
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=19950824163030.XZn_48quX4BNJs_MOKfHg_Ztx1jH8s2Q265pMAVuw_g@z \
--to=forsyth@plan9.cs.york.ac.uk \
/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).