Temporary failure in name resolution in 17.10 distros
ubuntu 17.10, kubuntu 17.10, ubuntu server 17.10
From newly installed virtual machines with 17.10, when pinging some devices in my local network there is a problem with name resolution.
Pinging the IP address works. But pinging them by their hostname does not always work. I can ping by name between the new linux VMs, as well Windows machines, but pinging by name older linux devices, e.g. router, leads to the message :"Temporary failure in name resolution".
That problem does not exist when pinging from VMs with older Linux installations.
Something that affects name resolution must have changed in the 17.10 versions. (the problem is not ping, it is name resolution)
Can anybody confirm this or help figure out what the reason is?
Can this be considered a bug?
17.10
asked Oct 31 '17 at 7:24
JoergJoerg
1612
bumped to the homepage by Community♦ 2 days ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
ubuntu 17.10, kubuntu 17.10, ubuntu server 17.10
From newly installed virtual machines with 17.10, when pinging some devices in my local network there is a problem with name resolution.
Pinging the IP address works. But pinging them by their hostname does not always work. I can ping by name between the new linux VMs, as well Windows machines, but pinging by name older linux devices, e.g. router, leads to the message :"Temporary failure in name resolution".
That problem does not exist when pinging from VMs with older Linux installations.
Something that affects name resolution must have changed in the 17.10 versions. (the problem is not ping, it is name resolution)
Can anybody confirm this or help figure out what the reason is?
Can this be considered a bug?
17.10
asked Oct 31 '17 at 7:24
JoergJoerg
1612
bumped to the homepage by Community♦ 2 days ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
I have the same problem on my Ubuntu laptop. Name resolution doesn't work. It happened out of the blue a few hours ago and still exists.
– vahid-dan
Oct 31 '17 at 21:47
add a comment |
ubuntu 17.10, kubuntu 17.10, ubuntu server 17.10
From newly installed virtual machines with 17.10, when pinging some devices in my local network there is a problem with name resolution.
Pinging the IP address works. But pinging them by their hostname does not always work. I can ping by name between the new linux VMs, as well Windows machines, but pinging by name older linux devices, e.g. router, leads to the message :"Temporary failure in name resolution".
That problem does not exist when pinging from VMs with older Linux installations.
Something that affects name resolution must have changed in the 17.10 versions. (the problem is not ping, it is name resolution)
Can anybody confirm this or help figure out what the reason is?
Can this be considered a bug?
17.10
asked Oct 31 '17 at 7:24
JoergJoerg
1612
ubuntu 17.10, kubuntu 17.10, ubuntu server 17.10
From newly installed virtual machines with 17.10, when pinging some devices in my local network there is a problem with name resolution.
Pinging the IP address works. But pinging them by their hostname does not always work. I can ping by name between the new linux VMs, as well Windows machines, but pinging by name older linux devices, e.g. router, leads to the message :"Temporary failure in name resolution".
That problem does not exist when pinging from VMs with older Linux installations.
Something that affects name resolution must have changed in the 17.10 versions. (the problem is not ping, it is name resolution)
Can anybody confirm this or help figure out what the reason is?
Can this be considered a bug?
17.10
17.10
asked Oct 31 '17 at 7:24
JoergJoerg
1612
asked Oct 31 '17 at 7:24
JoergJoerg
1612
asked Oct 31 '17 at 7:24
JoergJoerg
1612
asked Oct 31 '17 at 7:24
JoergJoerg
1612
asked Oct 31 '17 at 7:24
JoergJoerg
1612
1612
bumped to the homepage by Community♦ 2 days ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 2 days ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
I have the same problem on my Ubuntu laptop. Name resolution doesn't work. It happened out of the blue a few hours ago and still exists.
– vahid-dan
Oct 31 '17 at 21:47
add a comment |
I have the same problem on my Ubuntu laptop. Name resolution doesn't work. It happened out of the blue a few hours ago and still exists.
– vahid-dan
Oct 31 '17 at 21:47
I have the same problem on my Ubuntu laptop. Name resolution doesn't work. It happened out of the blue a few hours ago and still exists.
– vahid-dan
Oct 31 '17 at 21:47
I have the same problem on my Ubuntu laptop. Name resolution doesn't work. It happened out of the blue a few hours ago and still exists.
– vahid-dan
Oct 31 '17 at 21:47
add a comment |
2 Answers
2
active
oldest
votes
I downloaded Ubuntu 17.10 and ran it from RAM to test. Worked OK. I installed 17.10 on drive.
Installed couldn't reach the net:
"Temporary failure in name resolution".
A few days of fruitless "fixes" led to the discovery that in my 17.10, /etc/resov.conf was a link of /run/systemd/resolve/stub-resolv.conf. But /run/systemd/resolve did not exist (I think [most of] "run" is populated at boot time).
I rebooted the ram version and found that resolv.conf contained (unique to my installation):
# Generated by NetworkManager
search fios-router.home
nameserver 192.168.1.1
Put this my installed resolv.conf. Problem solved.
edited Feb 10 '18 at 8:15
galoget
2,1362920
answered Feb 10 '18 at 2:43
arnoldarnold
1
add a comment |
I've experienced it after upgrading (server edition) from 16.04 to 18.04, and apparently solution was to disable systemd-resolved as:
sudo systemctl disable systemd-resolved
and then reboot
sudo reboot
I found info about that here: https://ubuntuforums.org/showthread.php?t=2391351&s=adb88d3358fcc695b8480334fcbe2ba9&p=13765197#post13765197
It appears that on server edition, systemd-resolved is conflicting with netplan.
edited Aug 22 '18 at 9:40
Melebius
4,59651839
answered Aug 22 '18 at 8:48
Mariusz NowakMariusz Nowak
1012
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f971195%2ftemporary-failure-in-name-resolution-in-17-10-distros%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
I downloaded Ubuntu 17.10 and ran it from RAM to test. Worked OK. I installed 17.10 on drive.
Installed couldn't reach the net:
"Temporary failure in name resolution".
A few days of fruitless "fixes" led to the discovery that in my 17.10, /etc/resov.conf was a link of /run/systemd/resolve/stub-resolv.conf. But /run/systemd/resolve did not exist (I think [most of] "run" is populated at boot time).
I rebooted the ram version and found that resolv.conf contained (unique to my installation):
# Generated by NetworkManager
search fios-router.home
nameserver 192.168.1.1
Put this my installed resolv.conf. Problem solved.
edited Feb 10 '18 at 8:15
galoget
2,1362920
answered Feb 10 '18 at 2:43
arnoldarnold
1
add a comment |
I downloaded Ubuntu 17.10 and ran it from RAM to test. Worked OK. I installed 17.10 on drive.
Installed couldn't reach the net:
"Temporary failure in name resolution".
A few days of fruitless "fixes" led to the discovery that in my 17.10, /etc/resov.conf was a link of /run/systemd/resolve/stub-resolv.conf. But /run/systemd/resolve did not exist (I think [most of] "run" is populated at boot time).
I rebooted the ram version and found that resolv.conf contained (unique to my installation):
# Generated by NetworkManager
search fios-router.home
nameserver 192.168.1.1
Put this my installed resolv.conf. Problem solved.
edited Feb 10 '18 at 8:15
galoget
2,1362920
answered Feb 10 '18 at 2:43
arnoldarnold
1
add a comment |
I downloaded Ubuntu 17.10 and ran it from RAM to test. Worked OK. I installed 17.10 on drive.
Installed couldn't reach the net:
"Temporary failure in name resolution".
A few days of fruitless "fixes" led to the discovery that in my 17.10, /etc/resov.conf was a link of /run/systemd/resolve/stub-resolv.conf. But /run/systemd/resolve did not exist (I think [most of] "run" is populated at boot time).
I rebooted the ram version and found that resolv.conf contained (unique to my installation):
# Generated by NetworkManager
search fios-router.home
nameserver 192.168.1.1
Put this my installed resolv.conf. Problem solved.
edited Feb 10 '18 at 8:15
galoget
2,1362920
answered Feb 10 '18 at 2:43
arnoldarnold
1
I downloaded Ubuntu 17.10 and ran it from RAM to test. Worked OK. I installed 17.10 on drive.
Installed couldn't reach the net:
"Temporary failure in name resolution".
A few days of fruitless "fixes" led to the discovery that in my 17.10, /etc/resov.conf was a link of /run/systemd/resolve/stub-resolv.conf. But /run/systemd/resolve did not exist (I think [most of] "run" is populated at boot time).
I rebooted the ram version and found that resolv.conf contained (unique to my installation):
# Generated by NetworkManager
search fios-router.home
nameserver 192.168.1.1
Put this my installed resolv.conf. Problem solved.
edited Feb 10 '18 at 8:15
galoget
2,1362920
answered Feb 10 '18 at 2:43
arnoldarnold
1
edited Feb 10 '18 at 8:15
galoget
2,1362920
edited Feb 10 '18 at 8:15
galoget
2,1362920
edited Feb 10 '18 at 8:15
galoget
2,1362920
2,1362920
answered Feb 10 '18 at 2:43
arnoldarnold
1
answered Feb 10 '18 at 2:43
arnoldarnold
1
answered Feb 10 '18 at 2:43
arnoldarnold
1
1
add a comment |
add a comment |
I've experienced it after upgrading (server edition) from 16.04 to 18.04, and apparently solution was to disable systemd-resolved as:
sudo systemctl disable systemd-resolved
and then reboot
sudo reboot
I found info about that here: https://ubuntuforums.org/showthread.php?t=2391351&s=adb88d3358fcc695b8480334fcbe2ba9&p=13765197#post13765197
It appears that on server edition, systemd-resolved is conflicting with netplan.
edited Aug 22 '18 at 9:40
Melebius
4,59651839
answered Aug 22 '18 at 8:48
Mariusz NowakMariusz Nowak
1012
add a comment |
I've experienced it after upgrading (server edition) from 16.04 to 18.04, and apparently solution was to disable systemd-resolved as:
sudo systemctl disable systemd-resolved
and then reboot
sudo reboot
I found info about that here: https://ubuntuforums.org/showthread.php?t=2391351&s=adb88d3358fcc695b8480334fcbe2ba9&p=13765197#post13765197
It appears that on server edition, systemd-resolved is conflicting with netplan.
edited Aug 22 '18 at 9:40
Melebius
4,59651839
answered Aug 22 '18 at 8:48
Mariusz NowakMariusz Nowak
1012
add a comment |
I've experienced it after upgrading (server edition) from 16.04 to 18.04, and apparently solution was to disable systemd-resolved as:
sudo systemctl disable systemd-resolved
and then reboot
sudo reboot
I found info about that here: https://ubuntuforums.org/showthread.php?t=2391351&s=adb88d3358fcc695b8480334fcbe2ba9&p=13765197#post13765197
It appears that on server edition, systemd-resolved is conflicting with netplan.
edited Aug 22 '18 at 9:40
Melebius
4,59651839
answered Aug 22 '18 at 8:48
Mariusz NowakMariusz Nowak
1012
I've experienced it after upgrading (server edition) from 16.04 to 18.04, and apparently solution was to disable systemd-resolved as:
sudo systemctl disable systemd-resolved
and then reboot
sudo reboot
I found info about that here: https://ubuntuforums.org/showthread.php?t=2391351&s=adb88d3358fcc695b8480334fcbe2ba9&p=13765197#post13765197
It appears that on server edition, systemd-resolved is conflicting with netplan.
edited Aug 22 '18 at 9:40
Melebius
4,59651839
answered Aug 22 '18 at 8:48
Mariusz NowakMariusz Nowak
1012
edited Aug 22 '18 at 9:40
Melebius
4,59651839
edited Aug 22 '18 at 9:40
Melebius
4,59651839
edited Aug 22 '18 at 9:40
Melebius
4,59651839
4,59651839
answered Aug 22 '18 at 8:48
Mariusz NowakMariusz Nowak
1012
answered Aug 22 '18 at 8:48
Mariusz NowakMariusz Nowak
1012
answered Aug 22 '18 at 8:48
Mariusz NowakMariusz Nowak
1012
1012
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f971195%2ftemporary-failure-in-name-resolution-in-17-10-distros%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I have the same problem on my Ubuntu laptop. Name resolution doesn't work. It happened out of the blue a few hours ago and still exists.
– vahid-dan
Oct 31 '17 at 21:47