@dondos:
Then the problem seems to be caused by squid. Does it read the configuration file correctly? Open cache.log from /var/squid/log/ and look for: Adding nameserver 127.0.0.1 from squid.conf.
If not restart the squid service (or the whole system).
I set again the alternate DNS as 127.0.0.1, but I found many entries in the log file, similar to the one you said, at different times
2010/01/13 09:49:15| Adding domain grupposinergest.local from /etc/resolv.conf
2010/01/13 09:49:15| Adding nameserver 192.168.x.x from /etc/resolv.conf
2010/01/13 09:49:15| Adding nameserver 88.x.x.x from /etc/resolv.conf
2010/01/13 09:49:15| Adding nameserver 88.x.x.x from /etc/resolv.conf
...
2010/01/13 09:49:16| DNS Socket created at 0.0.0.0, port 20715, FD 7
2010/01/13 09:49:16| Adding nameserver 127.0.0.1 from squid.conf
...
2010/01/13 09:49:29| DNS Socket created at 0.0.0.0, port 43916, FD 12
2010/01/13 09:49:29| Adding nameserver 127.0.0.1 from squid.conf
...
2010/01/13 09:50:09| DNS Socket created at 0.0.0.0, port 31716, FD 6
2010/01/13 09:50:09| Adding nameserver 127.0.0.1 from squid.conf
...
The service is running properly, except for the problem we're struggling with.
@mhab12:
Can you try browsing FROM the DNS server? Perhaps it is not allowed on the Squid ACL and is therefore causing problems…
I'm afraid I can't understand what you are saying.
Do you mean I should let the DNS server bypass the proxy? How can it interfere with the DNS resolution of Squid?