<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Trace Route Doesn't Return DNS Name in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/trace-route-doesn-t-return-dns-name/m-p/2264752#M348232</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You could try the following. (Depending if your &lt;STRONG&gt;"policy-map"&lt;/STRONG&gt; configuration is as its default settings)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;policy-map global_policy&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt; class inspection_default&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp; inspect icmp error&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp; inspect icmp&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Then you could add the following to your ACL attached to your &lt;STRONG&gt;"outside"&lt;/STRONG&gt; interface or configure a new ACL to your &lt;STRONG&gt;"outside"&lt;/STRONG&gt; interface if it doesnt yet exist&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;access-list OUTSIDE-IN remark Allow ICMP return messages&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;access-list OUTSIDE-IN permit icmp any any unreachable&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;access-list OUTSIDE-IN permit icmp any any time-exceeded&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;access-list OUTSIDE-IN permit icmp any any echo-reply&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;access-group OUTSIDE-IN in interface outside&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You will naturally use the existing ACL if you have one. If no ACL exists you can use the above configuration as it is.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please remember to mark the reply as the correct answer if it answered your question.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ask more if needed&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 12 Jun 2013 10:35:52 GMT</pubDate>
    <dc:creator>Jouni Forss</dc:creator>
    <dc:date>2013-06-12T10:35:52Z</dc:date>
    <item>
      <title>Trace Route Doesn't Return DNS Name</title>
      <link>https://community.cisco.com/t5/network-security/trace-route-doesn-t-return-dns-name/m-p/2264751#M348231</link>
      <description>&lt;P&gt;I changed from a Linksys E4200 to a 5505 and when I use trace route, it doesn't return a DNS name for each hop.&amp;nbsp;&amp;nbsp; I can see the hops shown as asterisks.&amp;nbsp; Do I have to add something to inspect for this to work?&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 01:56:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/trace-route-doesn-t-return-dns-name/m-p/2264751#M348231</guid>
      <dc:creator>patrick.hurley</dc:creator>
      <dc:date>2019-03-12T01:56:23Z</dc:date>
    </item>
    <item>
      <title>Trace Route Doesn't Return DNS Name</title>
      <link>https://community.cisco.com/t5/network-security/trace-route-doesn-t-return-dns-name/m-p/2264752#M348232</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You could try the following. (Depending if your &lt;STRONG&gt;"policy-map"&lt;/STRONG&gt; configuration is as its default settings)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;policy-map global_policy&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt; class inspection_default&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp; inspect icmp error&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp; inspect icmp&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Then you could add the following to your ACL attached to your &lt;STRONG&gt;"outside"&lt;/STRONG&gt; interface or configure a new ACL to your &lt;STRONG&gt;"outside"&lt;/STRONG&gt; interface if it doesnt yet exist&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;access-list OUTSIDE-IN remark Allow ICMP return messages&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;access-list OUTSIDE-IN permit icmp any any unreachable&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;access-list OUTSIDE-IN permit icmp any any time-exceeded&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;access-list OUTSIDE-IN permit icmp any any echo-reply&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;access-group OUTSIDE-IN in interface outside&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You will naturally use the existing ACL if you have one. If no ACL exists you can use the above configuration as it is.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please remember to mark the reply as the correct answer if it answered your question.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ask more if needed&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Jun 2013 10:35:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/trace-route-doesn-t-return-dns-name/m-p/2264752#M348232</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2013-06-12T10:35:52Z</dc:date>
    </item>
  </channel>
</rss>

