Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17


Deny inbound UDP  due to DNS Response

Posted on 2006-06-16
Medium Priority
Last Modified: 2011-09-29
Does anyone have an idea as to what the following message is:-
It appears in my CISCO fireall log several times a day!
2006-06-15 12:37:35      Local4.Critical      Jun 15 2006 11:37:35: %PIX-2-106007: Deny inbound UDP from to due to DNS Response
where is my modem connected to the internet!
I know the /53 is DNS - I have a Win 2003k set up for my network DNS
Question by:Mawallace
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
  • 2
  • +1

Expert Comment

ID: 16919318
Explanation:   This is a connection-related message. This message is logged if
a UDP packet containing a DNS query or response is denied. The flag variable
is either Response or Query.

Action: If the inside port number is 53, it is likely that the inside host is
set up as a caching nameserver. Add an access-list command statement to
permit traffic on UDP port 53. If the outside port number is 53, the most
likely cause is that a DNS server was too slow to respond, and the query was
answered by another server.

If your internal DNS server is supposed to answer to public requests, add the
access-list. I would strongly advise removing the conduits and only using
access-lists. As I understand, that is the only way to provide outbound
packet filtering.

access-list udp_bound deny protocol source mask dest mask eq port
access-group udp_bound in interface inside



Author Comment

ID: 16919345
The /53 is  outside.
Does this mean I need to open up the network so that all /53 requests are passed inbound? Seems a bit dangerous to let anyone connect to the network via port 53?
LVL 51

Expert Comment

by:Keith Alabaster
ID: 16922305
First, Are you hosting internally a dns service that needs to be referenced by the Internet population? If no, then no you don't.

As a caveat to Renill's suggestions, if you do not already have an ACL associated with outbound traffic, be aware that once you apply an outbound acl you will need to specifically allow all of the outbound traffic you wish to permit.  ie no outbound acl means all outgoing is allowed (subject to there being a suitable nat/global configuration statement in place).  Apply an outbound acl then you need to tell it all of the allowed traffic, not just DNS  ie web, mail, ftp icmp etc.

I agree that the source port being from /53 sounds like it is a response that may well have timed out. If the original request had come from your internal network then the PIX (I assume its PIX) would still have an entry in its tables for that request going out so the response would be 'expected'.

You could temporarily raise the reporting level on your syslog to see if you get more detailed information but be aware that this will also put more load on your firewall.
Are You Ready for GDPR?

With the GDPR deadline set for May 25, 2018, many organizations are ill-prepared due to uncertainty about the criteria for compliance. According to a recent WatchGuard survey, a staggering 37% of respondents don't even know if their organization needs to comply with GDPR. Do you?

LVL 79

Expert Comment

ID: 16927054
Renill posted directly from Cisco's Error Message Decoder. I think the important part is this:
" If the outside port number is 53, the most likely cause is that a DNS server was too slow to respond, and the query was answered by another server."

>%PIX-2-106007: Deny inbound UDP from to
In your log entry, it is clearly the outside host with port# 53 and is most likely that this is a delayed response that has already been answered and the client no longer needs it. The PIX is smart enough to deny this packet because the client already has the answer. It is part of normal operation. You can disable this particular error message # in the syslog setup.

Q: Does your internal DNS server use specified forwarders, or root hints only for unknown zones?


Author Comment

ID: 16927524
My DNS server uses root hints, not a specified forwarder
LVL 79

Accepted Solution

lrmoore earned 375 total points
ID: 16927694
I suggest just supressing this particular message and getting on with life.
LVL 51

Expert Comment

by:Keith Alabaster
ID: 16929084
lol @ LR

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

To setup a SonicWALL for policy based routing to be used with the Websense Content Gateway there are several steps that need to be completed. Below is a rough guide for accomplishing this. One thing of note is this guide is intended to assist in the…
This article offers some helpful and general tips for safe browsing and online shopping. It offers simple and manageable procedures that help to ensure the safety of one's personal information and the security of any devices.
Have you created a query with information for a calendar? ... and then, abra-cadabra, the calendar is done?! I am going to show you how to make that happen. Visualize your data!  ... really see it To use the code to create a calendar from a q…
How to fix incompatible JVM issue while installing Eclipse While installing Eclipse in windows, got one error like above and unable to proceed with the installation. This video describes how to successfully install Eclipse. How to solve incompa…
Suggested Courses

721 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question