9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Benjamin Huntsman" <BHuntsman@mail2.cu-portland.edu>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] DNS dynamic update
Date: Wed, 17 Mar 2010 15:50:24 -0700	[thread overview]
Message-ID: <621112A569DAE948AD25CCDCF1C0753329990B@dolly.ntdom.cupdx> (raw)
In-Reply-To: <37253397a2546c809c04ab86f7e2b009@yyc.orthanc.ca>

[-- Attachment #1: Type: text/plain, Size: 793 bytes --]

>> (because it supplies the correct info for non-Plan 9 hosts).
>
>What info did your hosts need that Plan 9's dhcpd didn't supply?

Specifically, Plan 9's dhcpd does not supply a context-specific DNS suffix (ie, default domain name), which Windows systems need in order to resolve hosts by short name.  That is, if my internal DNS zone is home.local, and I have a system ns2.home.local, if dhcpd doesn't tell a Windows box that it's dns suffix should be home.local, then it will be able to resolve ns2.home.local, but not just ns2.

I looked at the dhcpd code, but it was easier to just have ISC dhcpd do the work on a FreeBSD system, since I already had it set up.  Plan 9's DNS does what I need it to (except the dynamic updates) and was easier to set up than BIND.

Thanks!
-Ben

[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 2731 bytes --]

  reply	other threads:[~2010-03-17 22:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-17 21:43 Benjamin Huntsman
2010-03-17 22:15 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2010-03-17 22:50   ` Benjamin Huntsman [this message]
2010-03-17 23:35     ` Steve Simon
2010-03-18 14:29       ` erik quanstrom

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=621112A569DAE948AD25CCDCF1C0753329990B@dolly.ntdom.cupdx \
    --to=bhuntsman@mail2.cu-portland.edu \
    --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).