I changed the Name server addresses order and added an additional domain name to the list but /etc/resolv.conf does not reflect the change. When I do a NSLookup it still shows the previous Name server that was configured.
Can the /etc/resolv.conf file be edited manually without screwing up the network configs or it there a command to force the change?
Just wondering,
Ken
Hi Ken,
I changed the Name server addresses order and added an additional domain name to the list but /etc/resolv.conf does not reflect the change.
how did you change the address order? If it doesn’t reflect in /etc/resolv.conf, I’d say something went wrong. You might want to run “rcnetwork restart” manually, but make sure you can access console in case something screws up (and you end without network access to the system).
Can the /etc/resolv.conf file be edited manually without screwing up the network configs or it there a command to force the change?
If I ever have to change these settings, I do so in the file directly. Unless you use DHCP, it should not screw things up, and the worst that may happen according to my experience is that YaST will create it’s own version of /etc/resolv.conf and put that into /etc with a suffix to the file name. If you’re the only admin, then this can be handled - if others administer the system as well, it can be pretty confusing that they change settings and this don’t reflect in the actual config files.
Come to think of it… maybe that’s just what happened in your case: have a look at /etc/resolv.conf*, maybe there’s such a newer (and suffixed) version because the original file was manually changed.
You can recover this by moving away the manually changed version (/etc/resolv.conf) and replace it by the generated version.
Regards,
Jens
On 07/09/2013 07:34 AM, RLMILLIES wrote:[color=blue]
I changed the Name server addresses order and added an additional domain
name to the list but /etc/resolv.conf does not reflect the change. When
I do a NSLookup it still shows the previous Name server that was
configured.Can the /etc/resolv.conf file be edited manually without screwing up
the network configs or it there a command to force the change?Just wondering,
Ken[/color]
Do you have both the domain and search lines in resolv.conf? IIRC,
they’re mutually exclusive. You get to pick one or the other.
–
Kevin Miller
Juneau, Alaska
http://www.alaska.net/~atftb
“In the history of the world, no one has ever washed a rented car.”
[QUOTE=Kevin Miller;14365]On 07/09/2013 07:34 AM, RLMILLIES wrote:[color=blue]
I changed the Name server addresses order and added an additional domain
name to the list but /etc/resolv.conf does not reflect the change. When
I do a NSLookup it still shows the previous Name server that was
configured.Can the /etc/resolv.conf file be edited manually without screwing up
the network configs or it there a command to force the change?Just wondering,
Ken[/color]
Do you have both the domain and search lines in resolv.conf? IIRC,
they’re mutually exclusive. You get to pick one or the other.
–
Kevin Miller
Juneau, Alaska
http://www.alaska.net/~atftb
“In the history of the world, no one has ever washed a rented car.”
I have been using Yast to config the Network Interfaces and there is a /etc/resolv.conf.netconfig file that does have all the changes listed in it. There is also a /etc/resolv.conf file that has the old information.
I am the only admin person who works on the servers.
As for the resolv.conf file, it has the original search domain name and ip address.
resolv.conf.netconfig shows all search domain names and addresses show in the Yast.
Sincerely,
Ken
On 07/10/2013 07:54 AM, RLMILLIES wrote:
[color=blue]
I have been using Yast to config the Network Interfaces and there is a
/etc/resolv.conf.netconfig file that does have all the changes listed in
it. There is also a /etc/resolv.conf file that has the old
information.[/color]
Odd. I don’t have /etc/resolv.conf.netconfig on any of my SLES systems.
I’d do:
mv /etc/resolv.conf /etc/resolv.conf.old
mv /etc/resolv.conf.netconfig /etc/resolv.conf
Then I’d make a slight change via Yast and see if it creates a new
/etc/resolv.conf.netconfig file or edits the newly renamed /etc/resolv.conf.
One other thought - in the Yast network manager module, I have a choice
between using “User Controlled with NetworkManager” or “Traditional
Method with ifup”
I use the latter, . It may be that NetworkManager is creating the
netconfig file. Can you switch to the ifup method and give it a try?
[color=blue]
I am the only admin person who works on the servers.
As for the resolv.conf file, it has the original search domain name and
ip address.resolv.conf.netconfig shows all search domain names and addresses show
in the Yast.[/color]
HTH…
Kevin Miller
Juneau, Alaska
http://www.alaska.net/~atftb
“In the history of the world, no one has ever washed a rented car.”
Thanks for the reply. I checked and it is using Traditional with ifup.
I’m a little leary about messing with the resolv files cause I read somewhere that once it is manually messed with, it may stop being able to be modified with Yast.
Sincerely,
Ken
On 07/10/2013 02:04 PM, RLMILLIES wrote:[color=blue]
Thanks for the reply. I checked and it is using Traditional with ifup.
I’m a little leary about messing with the resolv files cause I read
somewhere that once it is manually messed with, it may stop being able
to be modified with Yast.[/color]
I can’t imagine why, but before I make changes I often make a copy or
rename the file so I can roll back easily. What I have seen is Yast or
other tools overwriting a manually configured file.
The thing about resolv.conf is, its such a simple file it’s not hard to
create by hand and rarely would be changed.
Kevin Miller
Juneau, Alaska
http://www.alaska.net/~atftb
“In the history of the world, no one has ever washed a rented car.”
I’m a little leary about messing with the resolv files cause I read somewhere that once it is manually messed with, it may stop being able to be modified with Yast.
which seems to be what you’re seeing in the first place. +1 for “the rename route”, which basically was meant in my first reply, too.
Regards,
Jens