<div dir="ltr">Try adding an entry for it in /etc/hosts<br><br><div class="gmail_quote">On Thu, Oct 16, 2008 at 7:13 PM, Neil Sheth <span dir="ltr"><<a href="mailto:nsheth@gmail.com">nsheth@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I think this IS the issue, Kon. For example, I do:<br>
traceroute -n <a href="http://10.0.0.2" target="_blank">10.0.0.2</a><br>
Returns immediately<br>
<br>
I do<br>
traceroute <a href="http://10.0.0.2" target="_blank">10.0.0.2</a><br>
Takes quite some time.<br>
<br>
Thoughts on how to resolve this? Perhaps my settings in ifcfg-eth1<br>
aren't complete?<br>
<div><div></div><div class="Wj3C7c"><br>
On Wed, Oct 15, 2008 at 11:23 PM, Kon Wilms <<a href="mailto:konfoo@gmail.com">konfoo@gmail.com</a>> wrote:<br>
> On Wed, Oct 15, 2008 at 11:16 PM, Neil Sheth <<a href="mailto:nsheth@gmail.com">nsheth@gmail.com</a>> wrote:<br>
>> Hmmm, it appears we have general problems with using our 10.0.0.x<br>
>> addresses. For example, doing something like:<br>
>> ssh <a href="http://10.0.0.2" target="_blank">10.0.0.2</a><br>
>> takes a LONG time to return.<br>
>><br>
>> If I do something like<br>
>> 123.123.123 (my public IP),<br>
>> things return promptly.<br>
>><br>
>> Perhaps this is a general networking question less than<br>
>> nginx-specific, but thought I'd check if anyone has any good<br>
>> suggestions! Thanks!<br>
><br>
> Let me guess your sshd is doing reverse DNS lookups and you have no<br>
> internal DNS serving your 10.x.x.x network.<br>
><br>
> Cheers<br>
> Kon<br>
><br>
><br>
<br>
</div></div></blockquote></div><br></div>