My Syslogs are getting flooded with the following message:
%PIX-3-305005: No translation group found for udp src outside:188.8.131.52/62431 dst dmz:184.108.40.206/53
Now according to the PIX syslog messages it means:
%PIX-3-305005: No translation group found for <protocol> src <interface>:<IP_addr>/<port> dst <int_name>:<IP_addr>/<port>.
Explanation An outbound packet does not match any of the outbound nat rules.
Action This message signals a configuration error. If dynamic NAT is desired for the source host, ensure that the nat command matches the source IP address. If static NAT is desired for the source host, ensure that the local IP address of the static command matches. If no NAT is desired for the source host, check the access-list bound to the nat 0 access-list.
OK, I think I understand the explanation, but for the fact the DMZ interface has been shutdown for the last 6 months, I dont know this other IP address so it's not in my access-list and finally we have no DNS servers on our network.
It sounds like you already understand the issue - you are apparently receiving dns requests for a dns server that doesn't exist, and for which you don't have a translation.
1) Contact the source of these dns requests and ask them why they're sending these dns requests to you.
2) If these suddenly began (as opposed to you just starting looking at these and just found them), then you might capture a sniffer trace (free sniffer software available at ethereal.com) and see if these are legitimate DNS requests.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...