Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

So I am currently migrating our office away from the current proxy (Squid running in Windows on our Mail server...I did not set it up...) to a new one, Squid running on Vyatta.

So far I have everything setup and working perfectly, however im having trouble getting it to use two different DNS servers, one for internet ( and another for internal domain name sites.

If I set our internal DNS ip first with:

set system name-server
set system name-server

Then it does seem to resolve everything, however any public websites on the internet take an incredibly long time to resolve. However, if I switch it around so the public DNS is first, websites load incredibly quick but it will only load records in the public DNS.

Using nslookup with either setting only seems to use the first name server.

Anyone dealt with this before?

share|improve this question
up vote 2 down vote accepted

What is happening with the squid config above is that it's trying to resolve public DNS via your internal server, then waiting for it to fail, then trying public DNS.

I would suggest running a separate DNS proxy on the system and tell squid to use that. Something nice and easy like dnsmasq allows you to set different DNS servers for internal domains, but everything else goes to public internet DNS. Looks like Vyatta includes dnsmasq.

Alternatively, set up forwarding on whatever your internal DNS server is to allow it to resolve internet domain names, then just use the one DNS server in squid.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.