Pilora,
Your first guess was right for the static arp entry ..
190.34.22.140 00:23:A3:23:23:83
... to allow the firewall to ARP for another address not belonging to the firewall object. However, the entries in local.arp have nothing to do with NAT.
To NAT on FW-1 4.1 and previous you had to add a static route to the firewall. The reason for this was that when packets hit the outside of the firewall they would be routed before being NATed, so the firewall would need to know where to route them. You also need the NAT rule in the NAT rule base, of course.
So, to add a new rule to allow traffic to an object that would be NATed to an internal address you would have to create the object and the rule in the rule base, add and entry in local.arp to allow the firewall to ARP for that object, create the NAT rule in the rulebase (or use automatic NAT) and also put in a persistant static route to allow the firewall to route the packets to the correct interface before they are NATed.
On NG this works a bit differntly. Now the firewall NATs before it routes the packets to the static routes are no longer needed. Also, if using automatic NAT rules the arp enteries can be created automatically, negating the need for local.arp, unless you do manual NAT rules.
So, back to the original question. What is your problem?
"I need to be able to resolve the DNS for external in off of my webserver."
This doesn't make a whole lot of sense to me. Are you trying to allow the web server to do external DNS queries?
Chris.
**********************
Chris Andrew, CCNA, CCSA
chris@iproute.co.uk
**********************