Go Back   HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials > Linux Forums > Installation/Configuration

Do you like HowtoForge? Please consider supporting us by becoming a subscriber.
Thread Tools Display Modes
Old 3rd April 2013, 15:52
arisystems arisystems is offline
Junior Member
Join Date: Nov 2009
Location: Eagan, MN
Posts: 6
Thanks: 0
Thanked 0 Times in 0 Posts
Send a message via Skype™ to arisystems
Default Try this

The file looks correct assuming the IPs are right. I always add a comma between the IPs after dns-nameservers. You could try the Google nameservers of,

You can try this:

... and on some Zoneminder installs when moving the hard drive to a new physical CPU I have had problems get the "new" network cards to work properly and find that if I delete the /etc/udev/rules.d/70-persistent-net.rules and then power down (not restart) the system the two cars are then detected as eth0 and eth1. I know that this is not the specific thing you face but that file seems to have some hold-over on the interfaces configutation.

Please repost what you find.
Reply With Quote
Sponsored Links
Old 3rd April 2013, 19:07
sheshes sheshes is offline
Senior Member
Join Date: Aug 2009
Location: Nicosia
Posts: 123
Thanks: 2
Thanked 0 Times in 0 Posts

Thanks for your suggestion. Unfortunately neither the comma between IPs in /etc/network/interfaces work neither the post with the modification of NetworkManager.
as I am running the server edition of Ubuntu and not LTS so network manager is not installed
Reply With Quote
Old 20th June 2013, 16:37
bgardner bgardner is offline
Junior Member
Join Date: Jun 2013
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Default local nameserver

I think this is caused by the way resolvconf treats local nameservers. Checking the man page, I noticed this:


If set to "yes" then the libc script will include no more nameserver addresses after the first nameserver address that is a loopback address. (In IPv4 a loopback address is any one that starts with "127.". In IPv6 the loopback address is "::1".)

The advantage of truncating the nameserver list after a loopback address is that doing so inhibits unnecessary changes to resolv.conf and thus reduces the number of instances in which the update-libc.d/ scripts have to be run. When an interface is brought up or down the local caching nameserver that listens on the loopback address is still informed of the change and adapts accordingly; the clients of the resolver which use the local caching nameserver do not need to be notified of the change. A disadvantage of this mode of operation is that applications have no secondary or tertiary nameserver address to fall back on should the local caching nameserver crash. Insofar as a local nameserver crash can be regarded as an unlikely event, this is a relatively minor disadvantage. Set to "no" to disable truncation. The default is "yes".

A deprecated synonym for this variable is TRUNCATE_NAMESERVER_LIST_AFTER_127."
Reply With Quote


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Sending email issue lezelf Installation/Configuration 15 9th August 2011 12:20
setup-swraid1-on-a-running-lvm-system-ubuntu-10.04 - SDB dont boot but SDA yes lucho115 HOWTO-Related Questions 11 20th June 2011 18:22
Unable send receive emails vassilis3 Installation/Configuration 15 19th May 2007 15:34
No SPF record. beryl Installation/Configuration 6 17th May 2007 20:52
newbie ububtu 6.0.6 error PHP binary line 816 davidsky73 Installation/Configuration 8 17th September 2006 12:51

All times are GMT +2. The time now is 10:10.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.