From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@9fans.net Date: Wed, 3 Apr 2013 10:39:35 +0000 From: c117152@rmqkr.net Message-ID: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable References: , <30b7dc5f967768a728276851ef507605@hamnavoe.com> Subject: Re: [9fans] [9pi] standardize \ normalize setting dns in Topicbox-Message-UUID: 3ced3f1a-ead8-11e9-9d60-3106f5b1d025 On Thursday, March 28, 2013 2:41:42 PM UTC+2, Richard Miller wrote: > For a machine not receiving net configuration via DHCP, the normal >=20 > place to define dns=3D would be in /lib/ndb/local - 'man 6 ndb' for >=20 > information. Yes. I've already figured out that much: term% cat /lib/ndb/local database=3D file=3D/lib/ndb/local file=3D/lib/ndb/common auth=3Dsources.cd.bell-labs.com authdom=3Doutside.plan9.bell-labs.com ip=3D127.0.0.1 sys=3Dlocalhost dom=3Dlocalhost ipnet=3DHome ip=3D10.0.0.0 ipmask=3D255.255.255.0 ipgw=3D10.0.0.138 dns=3D1.2.3.4 # (my isp's dns) dns=3D8.8.8.8 # (googleA) dns=3D8.8.4.4 # (googleB) dns=3D10.0.0.138 # (my router for when the net is down but I still want lo= cal quarries getting through and local dom - .Home - requests) auth=3D9pi cpu=3D9pi ip=3D10.0.0.13 sys=3D9pi The thing is, the way I understand and implement it, you have your basic ne= tworking split in at least two places: The /lib/ndb/local file and the ip/i= pconfig command arguments (being called from termrc.local...). Now, if ther= e's a DHCP then you can forgo /lib/ndb/local and just specify an empty "ipc= onfig=3D". However, on a static ip you're only allowed to do everything exc= ept feeding it a dns. My idea is to have a line or two added to termrc.local that will parse a si= ngle dns var from the cmdline.txt file. This way you can get the same conve= nience you'd get with DHCP in a static setup. I'm not sure it's a possible needless un +\-foreseen complication, lack of = interest, an oversight, a security concern or whatever... But it seems to m= e that it could simplify things a little. Just a thought really.