[2607] in SIPB_Linux_Development
Re: /etc/resolv.conf
daemon@ATHENA.MIT.EDU (Erik Nygren)
Sat Feb 13 12:19:38 1999
To: Salvatore Valente <svalente@MIT.EDU>
Cc: warlord@MIT.EDU, linux-dev@MIT.EDU
In-Reply-To: Your message of "Sat, 13 Feb 1999 01:26:18 EST."
<199902130626.BAA24895@x15-cruise-basselope>
Date: Sat, 13 Feb 1999 12:19:23 EST
From: Erik Nygren <nygren@MIT.EDU>
> cat > resolv.conf <<EOF
> domain MIT.EDU
> nameserver 127.0.0.1
> nameserver 18.70.0.160
> nameserver 18.71.0.151
> EOF
>[...]
> So, given all this, does anyone object to putting /etc/resolv.conf
> back in the named.conf package? If you do object, you should suggest
> a better way to get 127.0.0.1 in /etc/resolv.conf when the named.conf
> package is installed.
I sufficient portion of the machines that will be installing
are in AI.MIT.EDU, LCS.MIT.EDU, NE.MEDIAONE.NET, etc that
having "domain MIT.EDU" is probably a poor idea...
(Although having MIT.EDU at the end of a "search" line
may not be a horrible idea.)
Maybe something that gets DOMAINNAME out of /etc/sysconfig/network
and uses that when generating resolv.conf? (Where it would
put in "domain MIT.EDU" if DOMAINNAME is MIT.EDU and
it would put in "search ${DOMAINNAME} MIT.EDU" otherwise?
Erik
