[BlueOnyx:05986] Re: 1:1 NAT and DNS - Domains not resolving regularly

[Christoph Schneeberger]

Titus Bolton wrote:
> Greetings and Salutations:
>
> I have an issue with domain names not resolving, and I am pretty sure
> it has something to do with our NAT'ing and our DNS, though I cannot
> be positive.
>
> We host a large number of domains, and we have noticed that the
> domains are not resolving properly outside of the local network.  Two
> of the domains are comsiteconstruction.com
> <http://comsiteconstruction.com> and radiotowerinstallers.com
> <http://radiotowerinstallers.com>.
>
> When I ping them I get something to the extent of:
>
> ping radiotowerinstallers.com <http://radiotowerinstallers.com>
> PING radiotowerinstallers.com <http://radiotowerinstallers.com>
> (10.0.0.200): 56 data bytes
> 64 bytes from *10.0.0.200*: icmp_seq=0 ttl=64 time=50.060 ms
>
> ping comsiteconstruction.com <http://comsiteconstruction.com>
> PING comsiteconstruction.com <http://comsiteconstruction.com>
> (10.0.0.140): 56 data bytes
> 64 bytes from *10.0.0.140*: icmp_seq=0 ttl=64 time=40.006 ms
>
> Pings from outside our network
> http://network-tools.com/default.asp?prog=ping&host=comsiteconstruction.com
> <http://network-tools.com/default.asp?prog=ping&host=comsiteconstruction.com>
>
> Ping 216.132.149.141
>
> [comsiteconstruction.com <http://comsiteconstruction.com>]
>
> Round trip time to 216.132.149.141: 417 ms
> Round trip time to 216.132.149.141: 529 ms
> Round trip time to 216.132.149.141: 723 ms
> Timed out
> Timed out
> Timed out
> Round trip time to 216.132.149.141: 501 ms
> Timed out
> Round trip time to 216.132.149.141: 508 ms
> Round trip time to 216.132.149.141: 173 ms
>
> Average time over 10 pings: 285.1 ms
>
> http://network-tools.com/default.asp?prog=ping&host=radiotowerinstallers.com
> <http://network-tools.com/default.asp?prog=ping&host=radiotowerinstallers.com>
>
> Ping
>
> [radiotowerinstallers.com <http://radiotowerinstallers.com>]
>
> Bad destination
> Bad destination
> Bad destination
> Bad destination
> Bad destination
> Bad destination
> Bad destination
> Bad destination
> Bad destination
> Bad destination
>
> Average time over 10 pings: 0 ms
>
>
> We're using a Cisco 3700 with a 1:1NAT.  The webservers are configured
> with the internal IPs.
>
> Here's a link that gives some more information regarding our DNS issues:
> http://www.dnsstuff.com/tools/dnsreport?domain=comsiteconstruction.com&format=raw&loadresults=true&token=2631b81c48a7cd4d17c01c08180f2013
> <http://www.dnsstuff.com/tools/dnsreport?domain=comsiteconstruction.com&format=raw&loadresults=true&token=2631b81c48a7cd4d17c01c08180f2013>
>

Make sure your DNS records show the external IP addresses (216.x.x.x)
which are portforwarded from the cisco not the internal ones (10.x.x.x).
So in short, all DNS entries should point to addresses on your cisco.

HTH,
Christoph