Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 2 subscribers
  • Views 237 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Problems with DNS proxy

centaur2000
Hello,

for weeks now we encounter problems regarding the DNS proxy. DNS requests time out very often forcing our users to hit the reload button of their browsers very often before the domain name is resolved and the page displayed. The DNS log file shows many of the following messages:

2006:07:25-09:47:46 (none) named[18087]: send_msg: sendmsg([192.168.x.x].40150%0): Operation not permitted
2006:07:25-09:49:45 (none) named[18087]: send_msg: sendmsg([192.168.x.x].23578%0): Operation not permitted
2006:07:25-09:51:25 (none) named[18087]: send_msg: sendmsg([192.168.x.x].1575%0): Operation not permitted
2006:07:25-09:51:55 (none) named[18087]: send_msg: sendmsg([192.168.x.x].1063%0): Operation not permitted
2006:07:25-09:51:59 (none) named[18087]: send_msg: sendmsg([192.168.x.x].2048%0): Operation not permitted

I don't know if this is related to issue ID3933 which is fixed in ASL V6.301.

Bandwidth or CPU/memory power can't be the problem - these are never bottle necks. Currently we're running ASL V.6.203 on an Intel Xeon 2.8 GHz with 1GB RAM.

I'm planning to upgrade to ASL 6.301 today. But I can't be sure that this will solve our problems as they exist since one of the last V5 upgrades. So any hints will be appreciated.

centaur2000


This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to NimmdirKeks
    Thanks, that was the missing piece of information! After having taken a look into the packet filter logs I realized that the firewall's reply to DNS queries where not missing but took too long. As a result the connections initiated by our workstations were already closed and the reply was seen as a new connection by the packet filter resulting in the above mentioned error messages. After getting in touch with our provider to clear the issue with their name servers everything is fine.

    Regards,
    centaur2000