From: Skip Tavakkolian <9nut@9netics.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Plan9 DNS server
Date: Sun, 21 Jun 2015 14:46:05 -0700 [thread overview]
Message-ID: <1e00221d35d7e33e92717614265bd84f@9netics.com> (raw)
In-Reply-To: <538B6965-0AA3-4216-AE29-04E109C70A4B@ar.aichi-u.ac.jp>
are you handing out IP configuration via dhcp?
i have a mixed plan9, linux, mac os x, windows environment. my
/lib/ndb/local is based on /n/sources/plan9/lib/ndb/local.complicated.
there are at least two cpu's that serve as dns and dhcp servers. some
non-plan9 systems have entires in ndb (i.e. by MAC address); the rest
get their IP's assigned from a pool. dhcp correctly hands out dom,
smtp, dns, auth, etc. as configured in the ndb.
> Hello,
>
> how to make DNS server that serves for computers on my home network?
> I tried:
> ndb/dns -rs
>
> 192.168.0.3 is my server’s IP.
> the name is “maia” and registered /lib/ndb/local as
> sys=maia dom=maia.local
>
> -bash$ nslookup
>> www.google.com
> Server: 192.168.0.3
> Address: 192.168.0.3#53
>
> Non-authoritative answer:
> Name: www.google.com
> Address: 216.58.220.228
>> maia
> Server: 192.168.0.3
> Address: 192.168.0.3#53
>
> ** server can't find maia: NXDOMAIN
>> maia.local
> Server: 192.168.0.3
> Address: 192.168.0.3#53
>
> ** server can't find maia.local: NXDOMAIN
>>
>
> how to enable locally assigned name resolution such as maia?
> I have many computers on my home network. currently I am registering them to /etc/hosts.
> but that is a pain.
>
> Kenji Arisawa
next prev parent reply other threads:[~2015-06-21 21:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-21 8:37 arisawa
2015-06-21 21:46 ` Skip Tavakkolian [this message]
2015-06-22 10:34 ` lucio
2015-06-22 11:21 ` Steve Simon
2015-06-22 11:40 ` lucio
2015-06-22 12:21 ` Steve Simon
2015-06-23 3:46 ` lucio
2015-06-22 22:29 ` arisawa
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=1e00221d35d7e33e92717614265bd84f@9netics.com \
--to=9nut@9netics.com \
--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).