Skip to main content

Cisco ASA 5505 and EDNS issue

resolution: update your running config on your firewall. See below

issue:
I changed my primary internal DNS to run on a RHEL 6.2 system. After that there were noticeable lags occasionally when I would browse.  Upon review of the syslog I noticed messages like the following;

Jan 31 22:44:41 zion named[26381]: success resolving 'p03-bookmarks.icloud.com/A' (in 'icloud.com'?) after reducing the advertised EDNS UDP packet size to 512 octets

I happen to use a Cisco ASA 5505 and I did some digging around.

firewall(config)# show run | grep mess
  message-length maximum 512

So - it turns out the value is set as part of a policy-map.  Let's tune it.


firewall(config)# policy-map type inspect dns preset_dns_map
firewall(config-pmap)# parameters
firewall(config-pmap-p)# no message-length maximum 512
firewall(config-pmap-p)# message-length maximum 4096
firewall(config-pmap-p)# 
firewall(config-pmap-p)# write mem
Building configuration...
Cryptochecksum: 3a1cdf20 91ce7d1e d8b188fc 1ac006fb 


4215 bytes copied in 1.420 secs (4215 bytes/sec)
[OK]
firewall(config-pmap-p)# 

Everything is better... now I just get these errors (and nothing on my side will fix this issue)
Jan 31 22:46:30 zion named[26381]: error (network unreachable) resolving 'thumbnail.newsinc.com/A/IN': 2001:500:90:1::18#53


Comments

Post a Comment

Popular posts from this blog

Sun USS 7100 foo

TIP: put ALL of your LUNs into a designated TARGET and INITIATOR group when you create them.  If you leave them in the "default" group, then everything that does an discovery against the array will find them :-( I'm struggling to recognize a reason that a default should even be present on the array. Also - who, exactly, is Sun trying to kid.  The USS is simply a box.. running Solaris .. with IPMP and ZFS.  Great.  If you have ever attempted to "break-in" or "p0wn" your IBM HMC, you know that there are people out there that can harden a box - then.. there's Sun.  After a recent meltdown at the office I had to get quite intimate with my USS 7110 and learned quite a bit.  Namely: there's a shell ;-) My current irritation is how they attempt to "warn you" away from using the shell (my coverage expired a long time ago to worry about that) and then how they try to hide things, poorly. I was curious as to what version of SunOS it ...

PXE boot a LiveCD image

Summary: I have wanted to build a kickstart environment which hosted a "rescue CD" or LiveCD to allow you to boot over the network after you blew your stuff up and needed to repair a few things.  Today I have worked through a method of doing so, with the help of the people who published a succinct script with the Red Hat Enterprise Virtualization Hypervisor.  (the script will be at the bottom of this post - if I have somehow not followed the GPL, please let me know and I will correct whatever is necessary) NOTE/Warning: The boot will fail due the initrd being too large (645mb).  I'm not sure how to proceed.  This procedure worked for RHEVh, because it is quite a bit smaller.  Hopefully I can report back with progress on this? :-$ Procedure: download your LiveCD image to /export/isos/RESCUE/Fedora-16-i686-Live-Desktop.iso # cd /var/tmp # vi livecd-iso-to-pxeboot (populate the file with the script shown below) # chmod 754 ./livecd-iso-to-pxeb...

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)"

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)" One issue that may cause this to arise is if you managed to break your /etc/fstab We had an engineer add a line with the intended options of "nfsvers=3" but instead added "-onfsvers=3" and it broke the system fairly catastrophically.