DNS name resolution problem

[Justin Thomas]

This could be a problem with reverse resolution.  Try either correcting your
reverse zones (i.e. 1.168.192.in-addr.arpa) or disabling reverse resolution
on the firewall.  Many firewalls - especially proxy based firewalls with an
SMTP proxy - attempt to do a reverse lookup on all traffic coming through
the proxy.  This can cause a very noticeable delay if the firewall cannot
find the reverse address.

Justin

-----Original Message-----
From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org]On
Behalf Of Dano
Sent: Monday, June 18, 2001 9:10 AM
To: comp-protocols-dns-bind at moderators.isc.org
Subject: DNS name resolution problem



Hi:

We recently changed ISP's due to the failure of our previous ISP.
Since the change, our E-mail client
takes forever to log into the server. If I ping the DNS name, the ping
returns our firewall IP address.
If I ping the Exchange servers IP address, it returns the correct
address. Since our e-mail server's address
is private, our ISP will not route to that IP address. They are using
the firewall's NAT address. I've attempted to
setup an internal DNS server but have been unsuccessful so far. Is
there anything else I can do to correct the DNS
address? I've also attempted changing the RPC Binding Order but that
didn't work either. Any suggestions?