If you are running a local DNS server like named/bind and don't want to use the ISPsupplied DNS servers that are announced via a DHCP request (using dhclient) then the solution is simple. The reason should be obvious, but normally running your own DNS server will provide a more reliable, and fast DNS response and you won't have to worry about filtering as much (unless your upstream filters or proxies outgoing DNS requests). Edit /etc/dhcp/dhclient.conf........

Debian based OS's have a similar issue as the behavior in RHEL/CentOS dhclient, which is that if you have an interface that relies on DHCP, if the first attempt fails, it will quit and stop. This is a problem especially if you are using your Linux as a router or something else mission critical, but where the internet for some reason may have been down or the DHCP server it gets a lease from broken. The expected behavior you would hope is that when things are back online that the........

It is very silly but the default on the ifup-eth script tells dhclient ( the program that obtains a DHCP IPaddress if you have selected DHCPin your ifcfg-eth* config file) to EXIT / QUIT if the first attempt to obtain a lease fails. No amount of dhclient.conf settings will fix this because if dhclient is started with -1 (which it is by default)then dhclient will quit. This is obviously very bad for MOST cases. Say for example you have a power outage or........

First we need to create dhclient.conf if it doesn't exist or edit it: vi /etc/dhclient/dhclient.conf #add this line at the top add the IPs as commas they will be the highest priority nameservers and whatever your ISP gives you will be used after these one (good for DNS backup) prepend domain-name-servers 127.0.0.1,10.10.25.8; After you restart your network or run dhclient again you should see the contents of........

[root@localhost:~] BootModuleConfig.sh echo host-ind nfcd........

yum exits in the middle The problem is this VPS seems to be an OpenVZ template from HyperVM. The only way to make it work was to disable i386 packages since this was an x64 kernel. That shouldn't be necessary but it was the only way to make yum stop quitting after the first package or two. I couldn't find any issue by checking the logs either. echo y|yum install vim-minimal telnet expect jwhois net-tools slocate iptables elinks gawk L........