 Re: Destination Name not resolving to Node Name
As I recall, it only looks at the objects primary IP, or extra interfaces if added - so it won't pick up the NAT entry.
If this is causing you a real problem, just create an object with the external NAT address. It's not that big a deal.
Another reason I don't really like auto NAt, although this is pretty low down - I don't really rely on the objects all that much, it's easier to use the IP addresses.
Oh and I think Jim is right about it being the client that does the DNS resolution, not the Server. |