DNS Issue?

[Neil Sheth]

I just added the following in the /etc/hosts file for each of my servers:

10.0.0.2        mydomain.com
10.0.0.3        mydomain.com
10.0.0.4        mydomain.com
10.0.0.5        mydomain.com
10.0.0.6        mydomain.com
10.0.0.7        mydomain.com
10.0.0.8        mydomain.com
(repeated for each IP I have assigned)

A bit tedious, but seems to have solved the issue.  Any downsides to this?

Thanks!


On Thu, Oct 16, 2008 at 2:04 AM, CryptWizard <cryptwizard at gmail.com> wrote:
> Try adding an entry for it in /etc/hosts
>
> On Thu, Oct 16, 2008 at 7:13 PM, Neil Sheth <nsheth at gmail.com> wrote:
>>
>> I think this IS the issue, Kon.  For example, I do:
>> traceroute -n 10.0.0.2
>> Returns immediately
>>
>> I do
>> traceroute 10.0.0.2
>> Takes quite some time.
>>
>> Thoughts on how to resolve this?  Perhaps my settings in ifcfg-eth1
>> aren't complete?
>>
>> On Wed, Oct 15, 2008 at 11:23 PM, Kon Wilms <konfoo at gmail.com> wrote:
>> > On Wed, Oct 15, 2008 at 11:16 PM, Neil Sheth <nsheth at gmail.com> wrote:
>> >> Hmmm, it appears we have general problems with using our 10.0.0.x
>> >> addresses.  For example, doing something like:
>> >> ssh 10.0.0.2
>> >> takes a LONG time to return.
>> >>
>> >> If I do something like
>> >> 123.123.123 (my public IP),
>> >> things return promptly.
>> >>
>> >> Perhaps this is a general networking question less than
>> >> nginx-specific, but thought I'd check if anyone has any good
>> >> suggestions!  Thanks!
>> >
>> > Let me guess your sshd is doing reverse DNS lookups and you have no
>> > internal DNS serving your 10.x.x.x network.
>> >
>> > Cheers
>> > Kon
>> >
>> >
>>
>
>