<div>
Hi,<br />
<br />
This may be missing the point, but why not point the webserver at a DNS server?<br />
<br />
You could give it OpenDNS (for example):<br />
<br />
208.67.222.222<br />
208.67.220.220 <br />
<br />
Hope that helps,<br />
<br />
Alan.
</div>


Hi,

This may be missing the point, but why not point the webserver at a DNS server?

You could give it OpenDNS (for example):

208.67.222.222
208.67.220.220

Hope that helps,

Alan.

<div>
That didn't work. I'm stumped as to why we can't seem to get the webserver to recognize DNS.
</div>


That didn't work. I'm stumped as to why we can't seem to get the webserver to recognize DNS.

<div>
<div class="content wysiwyg-content">
We used to havea firewall that acted as a DNS proxy. We replaced it with a Cisco ASA 5510 that does not have this set up. Now, our webserver is having issues sending meail from teh DMZ because it has no DNS server to use.<br />
<br />
Is there a way to set up a DNS proxy on the ASA 5510?
</div>
</div>


We used to havea firewall that acted as a DNS proxy. We replaced it with a Cisco ASA 5510 that does not have this set up. Now, our webserver is having issues sending meail from teh DMZ because it has no DNS server to use.

Is there a way to set up a DNS proxy on the ASA 5510?

ASA 5510 acting as a DNS proxy

Hardware-based firewalls provide more sophisticated protection for inbound and outbound traffic than the simple Windows software firewall or the basic NAT firewalls found in routers. These devices implement techniques such as stateful packet inspection, deep packet inspection, and content filtering; and may include built-in antivirus and anti-malware protection.