Ubuntu server 16.04.1 LTS VPS, unable to resolve or ping any hostname or ip

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
0
down vote

favorite












I have a problem with my VPS: I can't resolve any hostnames. I can't do apt-get update or anything else that involves hostname resolution.



Output of apt-get update:



Err:1 http://security.ubuntu.com/ubuntu xenial-security InRelease
 Temporary failure resolving 'security.ubuntu.com'
Err:2 http://archive.ubuntu.com/ubuntu xenial InRelease
 Temporary failure resolving 'archive.ubuntu.com'
Err:3 http://archive.canonical.com/ubuntu xenial InRelease
 Temporary failure resolving 'archive.canonical.com'
Err:4 http://archive.ubuntu.com/ubuntu xenial-updates InRelease
 Temporary failure resolving 'archive.ubuntu.com'
Reading package lists... Done
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial/InRelease Temporary failure resolving 'archive.ubuntu.com'
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease Temporary failure resolving 'archive.ubuntu.com'
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease Temporary failure resolving 'security.ubuntu.com'
W: Failed to fetch http://archive.canonical.com/ubuntu/dists/xenial/InRelease Temporary failure resolving 'archive.canonical.com'
W: Some index files failed to download. They have been ignored, or old ones used instead.


Output of cat /etc/network/interfaces:



# Auto generated lo interface
auto lo
iface lo inet loopback

# Auto generated venet0 interface
auto venet0
iface venet0 inet manual
 up ifconfig venet0 up
 up ifconfig venet0 127.0.0.2
 up route add default dev venet0
 down route del default dev venet0
 down ifconfig venet0 down


iface venet0 inet6 manual
 up route -A inet6 add default dev venet0
 down route -A inet6 del default dev venet0

auto venet0:0
iface venet0:0 inet static
 address 23.94.xxx.xxx
 netmask 255.255.255.255

auto venet0:1
iface venet0:1 inet static
 address 23.94.xxx.xxx
 netmask 255.255.255.255


Output of iptables -L:



Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination


Output of ifconfig:



lo Link encap:Local Loopback
 inet addr:127.0.0.1 Mask:255.0.0.0
 inet6 addr: ::1/128 Scope:Host
 UP LOOPBACK RUNNING MTU:65536 Metric:1
 RX packets:0 errors:0 dropped:0 overruns:0 frame:0
 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
 collisions:0 txqueuelen:0
 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
 inet addr:127.0.0.2 P-t-P:127.0.0.2 Bcast:0.0.0.0 Mask:255.255.255.255
 UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
 RX packets:1176 errors:0 dropped:0 overruns:0 frame:0
 TX packets:1233 errors:0 dropped:0 overruns:0 carrier:0
 collisions:0 txqueuelen:0
 RX bytes:65749 (65.7 KB) TX bytes:136176 (136.1 KB)

venet0:0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
 inet addr:23.94.xxx.xxx P-t-P:23.94.xxx.xxx Bcast:23.94.xxx.xxx Mask:255.255.255.255
 UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1

venet0:1 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
 inet addr:23.94.xxx.xxx P-t-P:23.94.xxx.xxx Bcast:23.94.xxx.xxx Mask:255.255.255.255
 UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1



ubuntu networking dns network-interface host-name-resolution




share|improve this question





















  • Have you tried pinging something that doesn't require DNS resolution? e.g. 8.8.8.8 or 1.1.1.1?
    – py4on
    May 9 at 14:44










  • yes, but this is the ruslut: ping -c 3 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. --- 8.8.8.8 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 1999ms
    – Lorenzo Piccinini
    May 9 at 14:49











  • Add the output of the route command to your question (and please use code formatting so it's easier to read!)
    – py4on
    May 9 at 15:00






  • 2




    @LorenzoPiccinini no, add it as an edit to your question not as a comment, so that we can apply code formatting and read it better
    – Thomas Ward
    May 9 at 18:06






  • 1




    From the look of the route you posted and the presence of the venet0 interface, I am going to guess this is a virtualized interface using host based routing. If that is the case, the networking, routing and IP setup are all done on the host your VPS is virtualized from. Changing interface settings in your VPS will likely prevent things from working properly.
    – GracefulRestart
    May 9 at 20:03














up vote
0
down vote

favorite












I have a problem with my VPS: I can't resolve any hostnames. I can't do apt-get update or anything else that involves hostname resolution.



Output of apt-get update:



Err:1 http://security.ubuntu.com/ubuntu xenial-security InRelease
 Temporary failure resolving 'security.ubuntu.com'
Err:2 http://archive.ubuntu.com/ubuntu xenial InRelease
 Temporary failure resolving 'archive.ubuntu.com'
Err:3 http://archive.canonical.com/ubuntu xenial InRelease
 Temporary failure resolving 'archive.canonical.com'
Err:4 http://archive.ubuntu.com/ubuntu xenial-updates InRelease
 Temporary failure resolving 'archive.ubuntu.com'
Reading package lists... Done
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial/InRelease Temporary failure resolving 'archive.ubuntu.com'
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease Temporary failure resolving 'archive.ubuntu.com'
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease Temporary failure resolving 'security.ubuntu.com'
W: Failed to fetch http://archive.canonical.com/ubuntu/dists/xenial/InRelease Temporary failure resolving 'archive.canonical.com'
W: Some index files failed to download. They have been ignored, or old ones used instead.


Output of cat /etc/network/interfaces:



# Auto generated lo interface
auto lo
iface lo inet loopback

# Auto generated venet0 interface
auto venet0
iface venet0 inet manual
 up ifconfig venet0 up
 up ifconfig venet0 127.0.0.2
 up route add default dev venet0
 down route del default dev venet0
 down ifconfig venet0 down


iface venet0 inet6 manual
 up route -A inet6 add default dev venet0
 down route -A inet6 del default dev venet0

auto venet0:0
iface venet0:0 inet static
 address 23.94.xxx.xxx
 netmask 255.255.255.255

auto venet0:1
iface venet0:1 inet static
 address 23.94.xxx.xxx
 netmask 255.255.255.255


Output of iptables -L:



Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination


Output of ifconfig:



lo Link encap:Local Loopback
 inet addr:127.0.0.1 Mask:255.0.0.0
 inet6 addr: ::1/128 Scope:Host
 UP LOOPBACK RUNNING MTU:65536 Metric:1
 RX packets:0 errors:0 dropped:0 overruns:0 frame:0
 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
 collisions:0 txqueuelen:0
 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
 inet addr:127.0.0.2 P-t-P:127.0.0.2 Bcast:0.0.0.0 Mask:255.255.255.255
 UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
 RX packets:1176 errors:0 dropped:0 overruns:0 frame:0
 TX packets:1233 errors:0 dropped:0 overruns:0 carrier:0
 collisions:0 txqueuelen:0
 RX bytes:65749 (65.7 KB) TX bytes:136176 (136.1 KB)

venet0:0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
 inet addr:23.94.xxx.xxx P-t-P:23.94.xxx.xxx Bcast:23.94.xxx.xxx Mask:255.255.255.255
 UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1

venet0:1 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
 inet addr:23.94.xxx.xxx P-t-P:23.94.xxx.xxx Bcast:23.94.xxx.xxx Mask:255.255.255.255
 UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1



ubuntu networking dns network-interface host-name-resolution




share|improve this question





















  • Have you tried pinging something that doesn't require DNS resolution? e.g. 8.8.8.8 or 1.1.1.1?
    – py4on
    May 9 at 14:44










  • yes, but this is the ruslut: ping -c 3 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. --- 8.8.8.8 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 1999ms
    – Lorenzo Piccinini
    May 9 at 14:49











  • Add the output of the route command to your question (and please use code formatting so it's easier to read!)
    – py4on
    May 9 at 15:00






  • 2




    @LorenzoPiccinini no, add it as an edit to your question not as a comment, so that we can apply code formatting and read it better
    – Thomas Ward
    May 9 at 18:06






  • 1




    From the look of the route you posted and the presence of the venet0 interface, I am going to guess this is a virtualized interface using host based routing. If that is the case, the networking, routing and IP setup are all done on the host your VPS is virtualized from. Changing interface settings in your VPS will likely prevent things from working properly.
    – GracefulRestart
    May 9 at 20:03












up vote
0
down vote

favorite









up vote
0
down vote

favorite











I have a problem with my VPS: I can't resolve any hostnames. I can't do apt-get update or anything else that involves hostname resolution.



Output of apt-get update:



Err:1 http://security.ubuntu.com/ubuntu xenial-security InRelease
 Temporary failure resolving 'security.ubuntu.com'
Err:2 http://archive.ubuntu.com/ubuntu xenial InRelease
 Temporary failure resolving 'archive.ubuntu.com'
Err:3 http://archive.canonical.com/ubuntu xenial InRelease
 Temporary failure resolving 'archive.canonical.com'
Err:4 http://archive.ubuntu.com/ubuntu xenial-updates InRelease
 Temporary failure resolving 'archive.ubuntu.com'
Reading package lists... Done
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial/InRelease Temporary failure resolving 'archive.ubuntu.com'
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease Temporary failure resolving 'archive.ubuntu.com'
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease Temporary failure resolving 'security.ubuntu.com'
W: Failed to fetch http://archive.canonical.com/ubuntu/dists/xenial/InRelease Temporary failure resolving 'archive.canonical.com'
W: Some index files failed to download. They have been ignored, or old ones used instead.


Output of cat /etc/network/interfaces:



# Auto generated lo interface
auto lo
iface lo inet loopback

# Auto generated venet0 interface
auto venet0
iface venet0 inet manual
 up ifconfig venet0 up
 up ifconfig venet0 127.0.0.2
 up route add default dev venet0
 down route del default dev venet0
 down ifconfig venet0 down


iface venet0 inet6 manual
 up route -A inet6 add default dev venet0
 down route -A inet6 del default dev venet0

auto venet0:0
iface venet0:0 inet static
 address 23.94.xxx.xxx
 netmask 255.255.255.255

auto venet0:1
iface venet0:1 inet static
 address 23.94.xxx.xxx
 netmask 255.255.255.255


Output of iptables -L:



Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination


Output of ifconfig:



lo Link encap:Local Loopback
 inet addr:127.0.0.1 Mask:255.0.0.0
 inet6 addr: ::1/128 Scope:Host
 UP LOOPBACK RUNNING MTU:65536 Metric:1
 RX packets:0 errors:0 dropped:0 overruns:0 frame:0
 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
 collisions:0 txqueuelen:0
 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
 inet addr:127.0.0.2 P-t-P:127.0.0.2 Bcast:0.0.0.0 Mask:255.255.255.255
 UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
 RX packets:1176 errors:0 dropped:0 overruns:0 frame:0
 TX packets:1233 errors:0 dropped:0 overruns:0 carrier:0
 collisions:0 txqueuelen:0
 RX bytes:65749 (65.7 KB) TX bytes:136176 (136.1 KB)

venet0:0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
 inet addr:23.94.xxx.xxx P-t-P:23.94.xxx.xxx Bcast:23.94.xxx.xxx Mask:255.255.255.255
 UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1

venet0:1 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
 inet addr:23.94.xxx.xxx P-t-P:23.94.xxx.xxx Bcast:23.94.xxx.xxx Mask:255.255.255.255
 UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1



ubuntu networking dns network-interface host-name-resolution




share|improve this question













I have a problem with my VPS: I can't resolve any hostnames. I can't do apt-get update or anything else that involves hostname resolution.



Output of apt-get update:



Err:1 http://security.ubuntu.com/ubuntu xenial-security InRelease
 Temporary failure resolving 'security.ubuntu.com'
Err:2 http://archive.ubuntu.com/ubuntu xenial InRelease
 Temporary failure resolving 'archive.ubuntu.com'
Err:3 http://archive.canonical.com/ubuntu xenial InRelease
 Temporary failure resolving 'archive.canonical.com'
Err:4 http://archive.ubuntu.com/ubuntu xenial-updates InRelease
 Temporary failure resolving 'archive.ubuntu.com'
Reading package lists... Done
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial/InRelease Temporary failure resolving 'archive.ubuntu.com'
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease Temporary failure resolving 'archive.ubuntu.com'
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease Temporary failure resolving 'security.ubuntu.com'
W: Failed to fetch http://archive.canonical.com/ubuntu/dists/xenial/InRelease Temporary failure resolving 'archive.canonical.com'
W: Some index files failed to download. They have been ignored, or old ones used instead.


Output of cat /etc/network/interfaces:



# Auto generated lo interface
auto lo
iface lo inet loopback

# Auto generated venet0 interface
auto venet0
iface venet0 inet manual
 up ifconfig venet0 up
 up ifconfig venet0 127.0.0.2
 up route add default dev venet0
 down route del default dev venet0
 down ifconfig venet0 down


iface venet0 inet6 manual
 up route -A inet6 add default dev venet0
 down route -A inet6 del default dev venet0

auto venet0:0
iface venet0:0 inet static
 address 23.94.xxx.xxx
 netmask 255.255.255.255

auto venet0:1
iface venet0:1 inet static
 address 23.94.xxx.xxx
 netmask 255.255.255.255


Output of iptables -L:



Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination


Output of ifconfig:



lo Link encap:Local Loopback
 inet addr:127.0.0.1 Mask:255.0.0.0
 inet6 addr: ::1/128 Scope:Host
 UP LOOPBACK RUNNING MTU:65536 Metric:1
 RX packets:0 errors:0 dropped:0 overruns:0 frame:0
 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
 collisions:0 txqueuelen:0
 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
 inet addr:127.0.0.2 P-t-P:127.0.0.2 Bcast:0.0.0.0 Mask:255.255.255.255
 UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
 RX packets:1176 errors:0 dropped:0 overruns:0 frame:0
 TX packets:1233 errors:0 dropped:0 overruns:0 carrier:0
 collisions:0 txqueuelen:0
 RX bytes:65749 (65.7 KB) TX bytes:136176 (136.1 KB)

venet0:0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
 inet addr:23.94.xxx.xxx P-t-P:23.94.xxx.xxx Bcast:23.94.xxx.xxx Mask:255.255.255.255
 UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1

venet0:1 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
 inet addr:23.94.xxx.xxx P-t-P:23.94.xxx.xxx Bcast:23.94.xxx.xxx Mask:255.255.255.255
 UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1




ubuntu networking dns network-interface host-name-resolution





share|improve this question












share|improve this question




share|improve this question








edited May 9 at 15:12









py4on

7351521




7351521









asked May 9 at 13:20









Lorenzo Piccinini

1




1











  • Have you tried pinging something that doesn't require DNS resolution? e.g. 8.8.8.8 or 1.1.1.1?
    – py4on
    May 9 at 14:44










  • yes, but this is the ruslut: ping -c 3 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. --- 8.8.8.8 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 1999ms
    – Lorenzo Piccinini
    May 9 at 14:49











  • Add the output of the route command to your question (and please use code formatting so it's easier to read!)
    – py4on
    May 9 at 15:00






  • 2




    @LorenzoPiccinini no, add it as an edit to your question not as a comment, so that we can apply code formatting and read it better
    – Thomas Ward
    May 9 at 18:06






  • 1




    From the look of the route you posted and the presence of the venet0 interface, I am going to guess this is a virtualized interface using host based routing. If that is the case, the networking, routing and IP setup are all done on the host your VPS is virtualized from. Changing interface settings in your VPS will likely prevent things from working properly.
    – GracefulRestart
    May 9 at 20:03
















  • Have you tried pinging something that doesn't require DNS resolution? e.g. 8.8.8.8 or 1.1.1.1?
    – py4on
    May 9 at 14:44










  • yes, but this is the ruslut: ping -c 3 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. --- 8.8.8.8 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 1999ms
    – Lorenzo Piccinini
    May 9 at 14:49











  • Add the output of the route command to your question (and please use code formatting so it's easier to read!)
    – py4on
    May 9 at 15:00






  • 2




    @LorenzoPiccinini no, add it as an edit to your question not as a comment, so that we can apply code formatting and read it better
    – Thomas Ward
    May 9 at 18:06






  • 1




    From the look of the route you posted and the presence of the venet0 interface, I am going to guess this is a virtualized interface using host based routing. If that is the case, the networking, routing and IP setup are all done on the host your VPS is virtualized from. Changing interface settings in your VPS will likely prevent things from working properly.
    – GracefulRestart
    May 9 at 20:03















Have you tried pinging something that doesn't require DNS resolution? e.g. 8.8.8.8 or 1.1.1.1?
– py4on
May 9 at 14:44




Have you tried pinging something that doesn't require DNS resolution? e.g. 8.8.8.8 or 1.1.1.1?
– py4on
May 9 at 14:44












yes, but this is the ruslut: ping -c 3 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. --- 8.8.8.8 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 1999ms
– Lorenzo Piccinini
May 9 at 14:49





yes, but this is the ruslut: ping -c 3 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. --- 8.8.8.8 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 1999ms
– Lorenzo Piccinini
May 9 at 14:49













Add the output of the route command to your question (and please use code formatting so it's easier to read!)
– py4on
May 9 at 15:00




Add the output of the route command to your question (and please use code formatting so it's easier to read!)
– py4on
May 9 at 15:00




2




2




@LorenzoPiccinini no, add it as an edit to your question not as a comment, so that we can apply code formatting and read it better
– Thomas Ward
May 9 at 18:06




@LorenzoPiccinini no, add it as an edit to your question not as a comment, so that we can apply code formatting and read it better
– Thomas Ward
May 9 at 18:06




1




1




From the look of the route you posted and the presence of the venet0 interface, I am going to guess this is a virtualized interface using host based routing. If that is the case, the networking, routing and IP setup are all done on the host your VPS is virtualized from. Changing interface settings in your VPS will likely prevent things from working properly.
– GracefulRestart
May 9 at 20:03




From the look of the route you posted and the presence of the venet0 interface, I am going to guess this is a virtualized interface using host based routing. If that is the case, the networking, routing and IP setup are all done on the host your VPS is virtualized from. Changing interface settings in your VPS will likely prevent things from working properly.
– GracefulRestart
May 9 at 20:03















active

oldest

votes











Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);








 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f442764%2fubuntu-server-16-04-1-lts-vps-unable-to-resolve-or-ping-any-hostname-or-ip%23new-answer', 'question_page');

);

Post as a guest






















active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes










 

draft saved


draft discarded


























 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f442764%2fubuntu-server-16-04-1-lts-vps-unable-to-resolve-or-ping-any-hostname-or-ip%23new-answer', 'question_page');

);

Post as a guest
































































-

Popular posts from this blog

How to check contact read email or not when send email to Individual?

Image
Clash Royale CLAN TAG #URR8PPP up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this question asked Sep 26 at 0:12 ToanLuong 49 9 add a comment  |  up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this questi...
Read more

Displaying single band from multi-band raster using QGIS

Image
Clash Royale CLAN TAG #URR8PPP 1 How can I extract a single band from multi-band raster in QGIS? I have an remote sensed image which has 6 bands (including NDVI band), I want to display each band separately, but have no idea how to do. I have seen some questions similar here but none worked for me. The original image (has 6 bands) is: I want to display the band 6 which should be like this: But I tried gdal_translate, and couldn't get the correct result. What I have got is: qgis raster multi-band share | improve this question edited Mar 5 at 0:53 Summer asked Mar 4 at 6:42 Summer Summer 23 6 Is this any help gis.stackexchange.com/questions/220658/… ? if not gis.stackexchange.com/questions/62133/… might help. – Michael Stimson Mar 4 at 6:46 Thanks for answering but when I used gdal_translate, qgis showed that 'Error 4: Kayena.tif: No such file or directory". Would you know how to fi...
Read more

How many registers does an x86_64 CPU actually have?

Image
Clash Royale CLAN TAG #URR8PPP up vote 2 down vote favorite I am currently learning reverse engineering and am studying the flags register. I had in my mind that rflags was just another name for one of the 16 general purpose registers, for example rax or rbx . But it looks like rflags is actually an additional register. So that makes 17 registers in total... how many more could there be? I have spent at least an hour on this and found numerous different answers. The best answer so far is this, which says that there are 40 registers in total. 16 General Purpose Registers 2 Status Registers 6 Code Segment Registers 16 SSE Registers 8 FPU/MMX Registers But if I add that up, I get 48. Could anybody provide an official answer on how many registers an x86_64 CPU has (e.g. an Intel i7). Additionally, I have seen references to 'hardware' and 'architectural' registers. What are those registers and how many are there? register x86-64 share | improve this...
Read more