[CentOS] resolving names it is really slow slow with CentOS5.x using named (SOLVED)

[carlopmart]

Victor Padro wrote:
> 
> 
> On Mon, May 25, 2009 at 4:23 PM, carlopmart <carlopmart at gmail.com 
> <mailto:carlopmart at gmail.com>> wrote:
> 
>     Victor Padro wrote:
>      >
>      >
>      > On Mon, May 25, 2009 at 4:05 PM, carlopmart <carlopmart at gmail.com
>     <mailto:carlopmart at gmail.com>
>      > <mailto:carlopmart at gmail.com <mailto:carlopmart at gmail.com>>> wrote:
>      >
>      >     RobertH wrote:
>      >      > ive read most of the thread, yet not all. forgive me as i
>     might
>      >     have missed
>      >      > some of this below in helping...
>      >      >
>      >      > carlopmart,
>      >      >
>      >      > what is in your /etc/resolv.conf
>      >
>      >     search hpulabs.org <http://hpulabs.org> <http://hpulabs.org>
>      >     nameserver 127.0.0.1
>      >
>      >      >
>      >      > is it configured correctly?
>      >      >
>      >      > are you using ipv6?
>      >
>      >     no.
>      >
>      >      >
>      >      > if not, is it fully disabled / turned off?
>      >      >
>      >      > in modprobe.conf put
>      >      >
>      >      > alias net-pf-10 off
>      >      > alias ipv6 off
>      >
>      >     I have configured this previously ..
>      >
>      >
>      >      >
>      >      > reboot...
>      >      >
>      >      > also, are you loading those other opsys on the same
>     machine and
>      >     getting good
>      >      > results or different machines?
>      >
>      >     I have good results using different operating systems but
>     using same
>      >     hardware ..
>      >
>      >
>      >      >
>      >      > testing other opsys on different hardware could be
>     problematic.
>      >      >
>      >      > did you bother to check the physical ports to see if any
>     problems
>      >     in the
>      >      > switch or with ethtool on the server interface ?
>      >
>      >     No, I didn't do it because i have good results using other
>     opsys ...
>      >      >
>      >      > thoughtfully consinder following advise of others re: tcp
>     and dns
>      >      >
>      >      > cables...
>      >      >
>      >      >  - rh
>      >      >
>      >      > _______________________________________________
>      >      > CentOS mailing list
>      >      > CentOS at centos.org <mailto:CentOS at centos.org>
>     <mailto:CentOS at centos.org <mailto:CentOS at centos.org>>
>      >      > http://lists.centos.org/mailman/listinfo/centos
>      >      >
>      >
>      >
>      >     --
>      >     CL Martinez
>      >     carlopmart {at} gmail {d0t} com
>      >     _______________________________________________
>      >     CentOS mailing list
>      >     CentOS at centos.org <mailto:CentOS at centos.org>
>     <mailto:CentOS at centos.org <mailto:CentOS at centos.org>>
>      >     http://lists.centos.org/mailman/listinfo/centos
>      >
>      >
>      > Have you double checked your SELinux config?
> 
>     SeLinux is disabled on both CentOS servers ...
> 
>      >
>      > You said you tested different OS'es on the same hardware?  or tested
>      > different OS'es on the same hardware but different servers?
> 
>     Same hardware and same server, because all opsys are installed on a
>     ESXi 3.5u4
>     server with vmware tools ...
> 
>      >
>      > Maybe remotely could be a faulty NIC.
> 
>     Maybe, but why only centos have problems??
> 
> 
>      >
>      >
>      >
>      > --
>      > "It is human nature to think wisely and act in an absurd fashion."
>      >
>      > "Todo el desorden del mundo proviene de las profesiones mal o
>      > mediocremente servidas"
>      >
>      >
>      >
>     ------------------------------------------------------------------------
>      >
>      > _______________________________________________
>      > CentOS mailing list
>      > CentOS at centos.org <mailto:CentOS at centos.org>
>      > http://lists.centos.org/mailman/listinfo/centos
> 
> 
>     --
>     CL Martinez
>     carlopmart {at} gmail {d0t} com
>     _______________________________________________
>     CentOS mailing list
>     CentOS at centos.org <mailto:CentOS at centos.org>
>     http://lists.centos.org/mailman/listinfo/centos
> 
> 
> 
> So, the problem resides on an ESXi CentOS VM?
> 
> I thought you were using a dedicated server though.
> 
> If so, what are you using as a NIC?
> 
> Sometimes the driver for e1000 gets faulty on RHEL/CentOS VMs, happened 
> to me a couple times, just add a new NIC to solve that.
> 
> 
> -- 
> "It is human nature to think wisely and act in an absurd fashion."
> 
> "Todo el desorden del mundo proviene de las profesiones mal o 
> mediocremente servidas"
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> http://lists.centos.org/mailman/listinfo/centos

You are right, Victor. Very very strange, but using vmxnet driver problems 
disappears on these centos vms ... I don't understand why, because windows vms 
and ubuntu vms uses e1000 driver without problems ....

Many thanks to all for your help.

-- 
CL Martinez
carlopmart {at} gmail {d0t} com