Koozali.org: home of the SME Server

resolv.conf file creating

Nate

resolv.conf file creating
« on: October 16, 2002, 07:01:39 PM »
My ISP's name server isn't working correctly.  I connect via a cable modem.  Some sites, such as www.ravantivirus.com, won't show up because of the nameserver.  To test this I added nameserver 127.0.0.1 to resolv.conf and everything works great.  So I though I would do a custom template--but the file resolv.conf is created at start time not using the templates.  If I do an expand-template /etc/resolv.conf, resolv.conf is created with 127.0.0.1 already in the file--without a custom template.  How is the resolv.conf file created at boot up?  How can I add "nameserver 127.0.0.1" on a more permanent basis?
thanks,
Nate

Bill Talcott

Re: resolv.conf file creating
« Reply #1 on: October 16, 2002, 09:48:45 PM »
/etc/e-smith/templates/etc/resolv.conf/20nameserver contains the line "nameserver 127.0.0.1" already. On 5.0U6 with a few minor addons...

Nate

Re: resolv.conf file creating
« Reply #2 on: October 17, 2002, 01:27:37 AM »
Yes I know, and mine is the same way.  The problem is that the server isn't using the templates to create resolv.conf, it's using info from the dhcp server in the resolv.conf during reboot.
Nate

Charlie Brady

Re: resolv.conf file creating
« Reply #3 on: October 17, 2002, 06:59:58 PM »
Nate wrote:

> Yes I know, and mine is the same way.  The problem is that
> the server isn't using the templates to create resolv.conf,
> it's using info from the dhcp server in the resolv.conf
> during reboot.

That would be a bug if that were the case. And lo! Here it is:

http://www.e-smith.org/bugs/index.php3?op=showBug&bugID=67

Charlie

Nate

Re: resolv.conf file creating
« Reply #4 on: October 18, 2002, 12:16:10 AM »
I know the work-around: expand the template.
I like the fix:  Upgrade to the current supported release of SME Server.
Not really a helpful solution.

Charlie Brady

Re: resolv.conf file creating
« Reply #5 on: October 18, 2002, 02:07:22 AM »
Nate wrote:

> I like the fix:  Upgrade to the current supported release of
> SME Server.

It works.

You could try:

rpm -Uhv \
ftp://ftp.e-smith.org/pub/e-smith/updates/5.5/Update2/RPMS/\
initscripts-5.83-1es5.i386.rpm

Charlie