Pix 501 messing with DNS?

I finally have everything swapped over.  I have internet traffic going thru my pix no problem and access lists working passing thru my mail, web, etc. traffic to my server.  However, the odd thing is once I switched to the 501, it seems that my DNS server isn't resolving requests in a timely fashion.  If you give it a few tries and wait upwards of a minute (trying the entire time with nslookup) it finally resolves it.  

For example, I can surf EE.com and even post here now once the IP resolves, however it took a while before this happened.  I am just starting to learn how to configure cisco firewalls and am not sure what is going on.  My previous firewall was a netgear wireless router.  Before switching to the pix, I never encountered this issue.  Please let me know if you want me to capture traffic or something.  I'm trying to get this and VPN figured out before I try to configure a 506E for one of my companies sites.

Here is my config:

interface ethernet0 auto
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password 8Ry2YjIyt7RRXU24 encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
hostname pixfirewall
domain-name ciscopix.com
fixup protocol ftp 21
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
no fixup protocol http 80
fixup protocol ils 389
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol sip 5060
fixup protocol sip udp 5060
fixup protocol skinny 2000
no fixup protocol smtp 25
fixup protocol sqlnet 1521
names
access-list acl_allow permit tcp any interface outside eq smtp
access-list acl_allow permit tcp any interface outside eq 1022
access-list acl_allow permit tcp any interface outside eq pop3
access-list acl_allow permit tcp any interface outside eq imap4
access-list acl_allow permit tcp any interface outside eq 465
access-list acl_allow permit tcp any interface outside eq 993
access-list acl_allow permit tcp any interface outside eq 995
access-list acl_allow permit tcp any interface outside eq ftp
access-list acl_allow permit tcp any interface outside eq www
access-list acl_allow permit tcp any interface outside eq https
pager lines 24
mtu outside 1500
mtu inside 1500
ip address outside dhcp setroute
ip address inside 192.168.3.1 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
pdm location 192.168.3.254 255.255.255.255 inside
pdm logging informational 100
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
static (inside,outside) tcp interface 1022 192.168.3.254 1022 netmask 255.255.255.255 0 0
static (inside,outside) tcp interface smtp 192.168.3.254 smtp netmask 255.255.255.255 0 0
static (inside,outside) tcp interface pop3 192.168.3.254 pop3 netmask 255.255.255.255 0 0
static (inside,outside) tcp interface imap4 192.168.3.254 imap4 netmask 255.255.255.255 0 0
static (inside,outside) tcp interface 465 192.168.3.254 465 netmask 255.255.255.255 0 0
static (inside,outside) tcp interface 993 192.168.3.254 993 netmask 255.255.255.255 0 0
static (inside,outside) tcp interface 995 192.168.3.254 995 netmask 255.255.255.255 0 0
static (inside,outside) tcp interface www 192.168.3.254 www netmask 255.255.255.255 0 0
static (inside,outside) tcp interface https 192.168.3.254 https netmask 255.255.255.255 0 0
static (inside,outside) tcp interface ftp 192.168.3.254 ftp netmask 255.255.255.255 0 0
access-group acl_allow in interface outside
timeout xlate 0:05:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h225 1:00:00
timeout h323 0:05:00 mgcp 0:05:00 sip 0:30:00 sip_media 0:02:00
timeout uauth 0:05:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server RADIUS protocol radius
aaa-server LOCAL protocol local
http server enable
http 192.168.3.0 255.255.255.0 inside
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
telnet timeout 5
ssh timeout 5
console timeout 0
dhcpd address 192.168.3.100-192.168.3.150 inside
dhcpd lease 3600
dhcpd ping_timeout 750
dhcpd auto_config outside
dhcpd enable inside
terminal width 80
LVL 25
Cyclops3590Sr Software EngineerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Cyclops3590Sr Software EngineerAuthor Commented:
okay, I think I figured it out, will test later tonight though.

My DNS server acts a caching server mostly, but forwards requests to 192.168.3.1, which the netgear would resolve, but if i'm not mistaken, the pix would just drop.  

I'm going to change the forwarders address to a different external DNS server to see if that fixes it
Les MooreSr. Systems EngineerCommented:
> but forwards requests to 192.168.3.1, which the netgear would resolve, but if i'm not mistaken, the pix would just drop.  
Yep. Pix will not proxy DNS as will the Netgear and most other SOHO routers.
You can remove all forwarders from the dns server and just keep the root hints and you'll be fine.
I don't see the fixup dns in your config. What version PIX OS?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Cyclops3590Sr Software EngineerAuthor Commented:
6.3(1)
Like an idiot I never thought of just removing the forwarders and just using the root hints.  I'll just do that, then I won't have to worry about it again
Learn SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

Cyclops3590Sr Software EngineerAuthor Commented:
ya that was it, forgot to flush the arp entries right away, but after I remembered to do that everything seems to be working flawlessly.
Cyclops3590Sr Software EngineerAuthor Commented:
btw, what exactly would the fixup dns do.
doesn't that just inspect udp/tcp 53 traffic to make sure it follows standards?
Les MooreSr. Systems EngineerCommented:
The standard dns fixup does exactly that..and makes sure that returns are not more than x-number of bytes

This would be the default config
'fixup protocol dns maximum-length 512'
Cyclops3590Sr Software EngineerAuthor Commented:
thanks, i'll give that a try
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Software Firewalls

From novice to tech pro — start learning today.