ASA config

[BumblingBlunderbuss]

Hello,

Per my original post, I decided to factory reset my ASA 5510 running version 8.2(5) and ran into the exact same issue - no DNS translation for clients. The firewall itself can hit stuff fun, but the devices themselves. Does anyone know of a default config I should try to get these devices communicating normally?

For the sake of argument, here is my most recent config. I'm willing to try just about anything at this point.

ciscoasa(config)# show run
: Saved
:
ASA Version 8.2(5)
!
hostname ciscoasa
enable password 8Ry2YjIyt7RRXU24 encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
names
!
interface Ethernet0/0
 nameif outside
 security-level 0
 ip address 192.168.5.254 255.255.255.0
!
interface Ethernet0/1
 nameif inside
 security-level 100
 ip address 192.168.100.254 255.255.255.0
!
interface Ethernet0/2
 shutdown
 no nameif
 no security-level
 no ip address
!              
interface Ethernet0/3
 shutdown
 no nameif
 no security-level
 no ip address
!
interface Management0/0
 nameif management
 security-level 100
 ip address 192.168.1.1 255.255.255.0
 management-only
!
ftp mode passive
dns domain-lookup outside
dns domain-lookup inside
dns server-group DefaultDNS
 name-server 8.8.8.8
 name-server 4.2.2.2
object-group network INSIDE_LAN
pager lines 24
logging asdm informational
mtu management 1500
mtu outside 1500
mtu inside 1500           
no failover
icmp unreachable rate-limit 1 burst-size 1
no asdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 1 192.168.100.0 255.255.255.0
route outside 0.0.0.0 0.0.0.0 192.168.5.1 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
timeout tcp-proxy-reassembly 0:01:00
timeout floating-conn 0:00:00
dynamic-access-policy-record DfltAccessPolicy
http server enable
http 192.168.1.0 255.255.255.0 management
no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart
crypto ipsec security-association lifetime seconds 28800
crypto ipsec security-association lifetime kilobytes 4608000
telnet timeout 5
ssh timeout 5
console timeout 0
dhcpd address 192.168.1.2-192.168.1.254 management
dhcpd enable management
!
dhcpd address 192.168.100.100-192.168.100.200 inside
dhcpd enable inside
!
threat-detection basic-threat
threat-detection statistics access-list
no threat-detection statistics tcp-intercept
webvpn
username admin password Rmrc8sBcdjisO3if encrypted privilege 15
!
class-map inspection_default
 match default-inspection-traffic
!
!
policy-map type inspect dns preset_dns_map
 parameters
  message-length maximum client auto
  message-length maximum 512
policy-map global_policy
 class inspection_default
  inspect dns preset_dns_map
  inspect ftp
  inspect h323 h225
  inspect h323 ras
  inspect rsh
  inspect rtsp
  inspect esmtp
  inspect sqlnet
  inspect skinny  
  inspect sunrpc
  inspect xdmcp
  inspect sip  
  inspect netbios
  inspect tftp
  inspect ip-options
!
service-policy global_policy global
prompt hostname context
no call-home reporting anonymous
Cryptochecksum:f98ae3bb4cf3da96ee5d75a4d7781126
: end

[Francesco Molino]

Hi

What dns server the client has today?
Can you add the following command and test again:
dhcpd dns x.x.x.x --> You can test by giving google dns server (dhcpd dns 8.8.8.8 8.8.4.4)

[BumblingBlunderbuss]

I was using external DNS for all clients. Both manually configured, and from DHCP.

I ran the command you recommended. No change. The Firewall can ping by ip and DNS name. Clients can ping by IP, but not by DNS name.

[Francesco Molino]

Hi

can you add for test an acl inside with permit ip any any like:
access-list inside_in extended permit ip any any
access-group inside_in in interface inside

Also while you're trying to access internet, can you check asa logs and share them with us?

Can you run the following command and share the result please:
packet-tracer input inside tcp 192.168.100.2 12345 8.8.8.8 80