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 question asked Se
Read more

Bahrain

Image
For other uses, see Bahrain (disambiguation). Sovereign island state in the Persian Gulf Kingdom of Bahrain مملكة البحرين   (Arabic) Mamlakat al-Baḥrayn Flag Coat of arms Anthem:  نشيد البحرين الوطني Bahrainona Our Bahrain Location of   Bahrain    (circled in red) Capital and largest city Manama 26°13′N 50°35′E  /  26.217°N 50.583°E  / 26.217; 50.583 Official languages Arabic Ethnic groups (2010 [1] ) 50.7% Arab (46% Bahrani, 4.7% other Arabs) 45.5% Asian 1% European 1.2% Others Religion Islam Demonym(s) Bahraini Government Unitary constitutional monarchy • King Hamad bin Isa Al Khalifa • Crown Prince Salman bin Hamad bin Isa Al Khalifa • Prime Minister Khalifa bin Salman Al Khalifa Legislature National Assembly • Upper house Consultative Council • Lower house Council of Representatives Independence • Declared Independence [2] 14 August 1971 • from United Kingdom [1] 15 August 1971 • Admitted to the United Nations 21 September 1971 • Kingdom of Bahrain 14 February 2002
Read more

Postfix configuration issue with fips on centos 7; mailgun relay

Image
Clash Royale CLAN TAG #URR8PPP up vote 0 down vote favorite I am trying to setup postfix to relay all mail generated on the local machine via SMTP to a mailgun relay. I have used the mailgun relay before with success on an ubuntu server, but I am migrating to a Centos 7 server which I will be running in FIPS mode. There error log is below, slightly sanitized. I have a small enough network that I choose to have each machine reach out to mailgun individually (this the loopback-only, 127.0.0.0/8 restrictions) and no firewall open port allowing smtp in to the machine. I assume the FIPS mode (and with it disabling of MD5) is causing problems, but I don't know how to overcome it or if it is even possible for tls_fprint to use some supported hash such as sha256 or sha512. However, the relay=none is slightly concerning since I have relayhost set, but perhaps that is because the smtp process is failing? Any help would be appreciated! postconf -n: alias_database = hash:/etc/alia
Read more