That will work great. One box...two NICS, running ipchains. If you are looking to resolve your own names locally such as http://intranet (like many places are) but you still want to be forwarded up to your ISP's resolvers, you can just list them in BIND (or your chosen DNS app) as the places to check if your server does not know an answer. I like using the root-hints best, that way there is no risk of an ISP forwarding me to a place that I do not want to be, like for searches.

Larry Kemp Network Engineer U.S. Metropolitan Telecom, LLC Bonita Springs, FL USA

-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Bowie Bailey Sent: Friday, October 09, 2009 12:04 PM To: centos@centos.org Subject: Re: [CentOS] Resolv.conf with multiple adaptors on multiple networks

ML wrote:

Hi All,

I did a clean install of CentOS 5.3 yesterday. During setup I activated both adapters on startup. etho is my public IP and eth1 is my private/internal IP.

It did not let me specify nameservers though.

So I know this is resolv.conf.

I know I put in: nameserver xxx.xxx.xxx.xxx nameserver xxx.xxx.xxx.xxx

But how do I put in nameservers for specific networks? Example, I want my public IP to resolve to the comcast name-servers top get out to things like Google. I want internal to default to my internal DNS once I have it setup.

Just have everything query your internal DNS. It can respond directly for your local domains and then either query the root nameservers or the Comcast nameservers for everything else.