Hello all I am running into the most curious of problems on the boxes I build. One of the last things I do is to run netconfig to set the tcp/ip props according to the customers wishes. This works fine for all items _except_ the nameserver! The really odd thing is this: if I run netconfig a second time then the nameserver change will stick. Very irritating to say the least. Any ideas on why this might be occuring?

What distro r u running? Slackware? I have no problem with netconfig. I have even tried it through ssh. All ok. Were u setting up the machine to use dhcp?

The distro is Fedora Core 4. Usually I am setting up the unit to use static, and I am moving away from DHCP.

i have netconfig on slackware
for fedora core 4 go to root konsol

# setup > network configuration > ethernet > configure

edit /etc/resolv.conf by hand add your isp nameserver or any as u wish

for my isp i use this

[root@nc rou]# cat /etc/resolv.conf
nameserver 202.188.0.132

Thanks routers, I will try editing the resolv.conf file directly, but my understanding is that the netconfig utility is supposed to be able to do all that for you. And it DOES do it for you the second time around. Why doesn't it work the first time? Does it have something to do with the fact that the previous nameserver ip was gotten via dhcp, and is thus more resistant to change somehow?

from my experience its not change the resolv.conf if you first starting using
dhcp , this one i not sure why, but since i can edit resolv.conf directly
so i have no big deal for this issue

today I ran another test where I built a linux box to use dhcp:

$ more /etc/resolv.conf
search domainname.com
nameserver 192.168.1.1

I run netconfig, changing all settings to static:

10.0.0.10
255.0.0.0
10.255.255.254
10.0.01 (namesever)

I immediately run:

$ more /etc/resolv.conf
nameserver 10.0.0.1

which shows that netconfig did indeed change the nameserver there as it is supposed to. I then rebooted, and did another more /etc/resolv.conf, and guess what? This is what I get:

$ more /etc/resolv.conf
search domainname.com
nameserver 192.168.1.1

Why is the nameserver reverting back to it's previous dhcp settings after a reboot?

so use whichever work for you

/etc/resolv.conf sould contain your isp name nameserver

if u getting whatever router/gateway ip just comment it

That is not a solution. I am trying to discover why the nameserver is reverting back to it's DHCP settings after a reboot.

looks like you have two (2) devices in your network (LAN) which is distribute dhcp
maybe one router and one AP which is connected to the same network
you need to check it

Thanks for the suggestion, but as it happens I only have one device handing out IP addresses via DHCP. But even if I had one hundred devices running DHCP, if I tell an interface not to use DHCP, but rather to use static info, then it should not matter how many DHCP services I have running on my network, right?

In this instance, the linux box is built from scratch with DHCP configured eth0, then once I am done with the system and need to assign static info, I use netconfig to do so, in effect telling the interface I am configuring not to use DHCP assigned info anymore. Then on reboot only the nameserver reverts to it's previous DHCP setting, not the rest.

I think this has to be a bug in netconfig, or maybe a bug in fedora core 4.

Who are the maintainers of netconfig? I am running netconfig-0.8.22-1 and according to yum there is not update for it at all. So it would seem this is the latest version. Perhaps the maintainers of that package would have some insight.