Not working DNS resolver how to set or check?

Try to configure virtualization on the server SoyouStart (OVH) - everything seems set up correctly but does not work resolve addresses. Ping as I understand it from the new path to the Internet, and the virtual machine pinged. FAILOVER_IP - ip address for the virtual machine.
ping -c 2 8.8.8.8 (0% packet loss, time 1001ms)

ping -c 2 google.com
ping: unknown host google.com

Try to ping the address of a path from the desktop computer - seems to work.
To connect to virtual reality via SSH without timeout.
ping -c 2 FAILOVER_IP (0% packet loss, time 1001ms)
debug1: Connecting to FAILOVER_IP [FAILOVER_IP] port 22 (stops)

DNS for ovh vitrually 213.186.33.99 of the path ping and the host machine too. dns nameservers are registered and available.
ping -c 2 213.186.33.99
PING 213.186.33.99 (213.186.33.99) 56(84) bytes of data.
64 bytes from 213.186.33.99: icmp_seq=1 ttl=60 time=1.35 ms
64 bytes from 213.186.33.99: icmp_seq=2 ttl=60 time=1.30 ms

--- 213.186.33.99 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 1.303/1.327/1.352/0.043 ms

vi /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 213.186.33.99
nameserver 8.8.8.8
nameserver 8.8.4.4
search ovh.net

How to find out what's the problem?
June 8th 19 at 16:26
1 answer
June 8th 19 at 16:28
Go through the web console and see that there inclucapa and firewall rules
SoyouStart - there is no such. Install a clean/default.
view to there with nslookup and firewall rules

And what commands must be entered and what should show? - yvonne75 commented on June 8th 19 at 16:31
iptables-L on the dev - everything is open (policy ACCEPT) - yvonne75 commented on June 8th 19 at 16:34
well nslookup domain
ustart based on OVH, and OVH is a web console and probably ustart must also be - Eulalia22 commented on June 8th 19 at 16:37
, nslookup,...;; connection timed out; no servers could be reached - yvonne75 commented on June 8th 19 at 16:40
where you something nakosyachili
the easiest way to rearrange the system
harder to get an admin to have it figured out - Eulalia22 commented on June 8th 19 at 16:43
I use Ansible - that is, in parallel with another hoster (online) all make a half-turn - all actions are identical. I would hire a admin, if he does and explain what's wrong, where to find it? - yvonne75 commented on June 8th 19 at 16:46
there plugging in ipitables host machine. What IPTABLES rule prevents the new path? - yvonne75 commented on June 8th 19 at 16:49
go to apwork there is a lot of admins - Eulalia22 commented on June 8th 19 at 16:52

Find more questions by tags Ubuntu ServerNetwork equipmentUbuntu