OpenVZ Forum: Support » DNS resolving bad (((

Home » General » Support » DNS resolving bad (((

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

DNS resolving bad ((( [message #42273]

Tue, 29 March 2011 19:20

yaroslavukr
Messages: 7
Registered: November 2008

Junior Member

Please help. Updated OpenVZ. Rebooted the server and there is a problem. In some VDS lost DNS resolving((( and, in some it is.

OS: CentOS 5.5 Final

[root@hostname log]# uname -a
Linux hostname 2.6.18-238.5.1.el5.028stab085.3PAE #1 SMP Mon Mar 21 21:09:23 MSK 2011 i686 i686 i386 GNU/Linux

dmesg log:
ip_conntrack: parameter ip_conntrack_enable_ve0 is obsoleted. In ovzkernel >= 2. 6.15 connection tracking on hardware node is enabled by default, use ip_conntrac k_disable_ve0=1 parameter to disable.
ip_conntrack version 2.4 (8192 buckets, 65536 max) - 232 bytes per conntrack

[root@hostname log]# vzctl exec 110 ping lxcenter.org
PING lxcenter.org (66.197.145.22) 56(84) bytes of data.
64 bytes from srva.lxcenter.org (66.197.145.22): icmp_seq=1 ttl=47 time=35.7 ms

[root@hostname log]# vzctl exec 13066 ping lxcenter.org
ping: unknown host lxcenter.org

Report message to a moderator

Re: DNS resolving bad ((( [message #42276 is a reply to message #42273]

Wed, 30 March 2011 06:48

gralex
Messages: 62
Registered: December 2008
Location: Russia, Novosibirsk

Member

[root@hostname log]# vzctl exec 110 cat /etc/resolv.conf
[root@hostname log]# vzctl exec 13066 cat /etc/resolv.conf

Is there any difference?

Report message to a moderator

Re: DNS resolving bad ((( [message #42278 is a reply to message #42276]

Wed, 30 March 2011 07:40

yaroslavukr
Messages: 7
Registered: November 2008

Junior Member

[root@hostname log]# vzctl exec 110 cat /etc/resolv.conf
nameserver 64.202.97.1
nameserver 64.202.97.2

[root@hostname log]# vzctl exec 13066 cat /etc/resolv.conf
nameserver 64.202.97.1
nameserver 64.202.97.2

Report message to a moderator

Re: DNS resolving bad ((( [message #42289 is a reply to message #42278]

Wed, 30 March 2011 09:41

gralex
Messages: 62
Registered: December 2008
Location: Russia, Novosibirsk

Member

And what about ping and traceroute from within problem VE to nameservers?

Try to remove all IPs from VE and re-add it again.

Report message to a moderator

Re: DNS resolving bad ((( [message #42292 is a reply to message #42278]

Wed, 30 March 2011 10:36

yaroslavukr
Messages: 7
Registered: November 2008

Junior Member

[root@vds ~]# ping 64.202.97.1
PING 64.202.97.1 (64.202.97.1) 56(84) bytes of data.

--- 64.202.97.1 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2133ms

[root@vds ~]# tracert 64.202.97.1
traceroute to 64.202.97.1 (64.202.97.1), 30 hops max, 40 byte packets
 1   (Nod IP)  0.068 ms  0.044 ms  0.014 ms
 2  * * *
 3  * * *
 4  * * *

Report message to a moderator