DNS resolving of localhost subdomains stopped working after resolvconf update
For years I'm using Ubuntu (currently on 18.10) to develop PHP applications on domains like foo.bar.localhost for local testing. These domains were resolved to 127.0.0.1 and handled by Apache 2.4. This always worked. The line 127.0.0.1 localhost is in my /etc/hosts like it always was.
Today morning I turned my device on and this did not work anymore. ping localhost is still working, but ping foo.bar.localhost is not (it still was working yesterday). Surprisingly Chromium is still resolving foo.bar.localhost, I assume it's not using the OS for DNS resolving. But I'm mainly using Firefox, which also stopped resolving localhost subdomains.
I didn't change any system-related settings yesterday, but I remember some package updates from yesterday, so I assume there were some changes to some network-related things. Is there any way to get dpgk to list install/update dates so that I can find out the exact packages that were updated?
What settings could I check to make resolving subdomains work again system-wide? Are there any known bugs?
Additional information: In /var/log/dpkg.log I found a recent entry upgrade resolvconf:all 1.79ubuntu10 1.79ubuntu10.18.10.1 which sounds relevant. This and the following subsequent lines are the only lines containing the term "resolv" (found with cat /var/log/dpkg.log | grep resolv). So, in the last hours this DNS-relevant package was updated.
Another information: the manual man systemd-resolved has the following line:
The hostnames "localhost" and "localhost.localdomain" (as well as any
hostname ending in ".localhost" or ".localhost.localdomain") are
resolved to the IP addresses 127.0.0.1 and ::1.
So this well-defined behaviour stopped working. I also can not remember changing anything related to this lowlevel DNS stuff myself.
The exact message when doing ping foo.bar.localhost is
ping: foo.bar.localhost: Name or service not known
Apparently the only bug "fixed" in the new version of resolvconf was this:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1817903
which is related to local resolving.
networking browser localhost web-development resolvconf
asked Mar 12 at 7:10
foobarfoobar
163
New contributor
foobar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
For years I'm using Ubuntu (currently on 18.10) to develop PHP applications on domains like foo.bar.localhost for local testing. These domains were resolved to 127.0.0.1 and handled by Apache 2.4. This always worked. The line 127.0.0.1 localhost is in my /etc/hosts like it always was.
Today morning I turned my device on and this did not work anymore. ping localhost is still working, but ping foo.bar.localhost is not (it still was working yesterday). Surprisingly Chromium is still resolving foo.bar.localhost, I assume it's not using the OS for DNS resolving. But I'm mainly using Firefox, which also stopped resolving localhost subdomains.
I didn't change any system-related settings yesterday, but I remember some package updates from yesterday, so I assume there were some changes to some network-related things. Is there any way to get dpgk to list install/update dates so that I can find out the exact packages that were updated?
What settings could I check to make resolving subdomains work again system-wide? Are there any known bugs?
Additional information: In /var/log/dpkg.log I found a recent entry upgrade resolvconf:all 1.79ubuntu10 1.79ubuntu10.18.10.1 which sounds relevant. This and the following subsequent lines are the only lines containing the term "resolv" (found with cat /var/log/dpkg.log | grep resolv). So, in the last hours this DNS-relevant package was updated.
Another information: the manual man systemd-resolved has the following line:
The hostnames "localhost" and "localhost.localdomain" (as well as any
hostname ending in ".localhost" or ".localhost.localdomain") are
resolved to the IP addresses 127.0.0.1 and ::1.
So this well-defined behaviour stopped working. I also can not remember changing anything related to this lowlevel DNS stuff myself.
The exact message when doing ping foo.bar.localhost is
ping: foo.bar.localhost: Name or service not known
Apparently the only bug "fixed" in the new version of resolvconf was this:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1817903
which is related to local resolving.
networking browser localhost web-development resolvconf
asked Mar 12 at 7:10
foobarfoobar
163
New contributor
foobar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
For years I'm using Ubuntu (currently on 18.10) to develop PHP applications on domains like foo.bar.localhost for local testing. These domains were resolved to 127.0.0.1 and handled by Apache 2.4. This always worked. The line 127.0.0.1 localhost is in my /etc/hosts like it always was.
Today morning I turned my device on and this did not work anymore. ping localhost is still working, but ping foo.bar.localhost is not (it still was working yesterday). Surprisingly Chromium is still resolving foo.bar.localhost, I assume it's not using the OS for DNS resolving. But I'm mainly using Firefox, which also stopped resolving localhost subdomains.
I didn't change any system-related settings yesterday, but I remember some package updates from yesterday, so I assume there were some changes to some network-related things. Is there any way to get dpgk to list install/update dates so that I can find out the exact packages that were updated?
What settings could I check to make resolving subdomains work again system-wide? Are there any known bugs?
Additional information: In /var/log/dpkg.log I found a recent entry upgrade resolvconf:all 1.79ubuntu10 1.79ubuntu10.18.10.1 which sounds relevant. This and the following subsequent lines are the only lines containing the term "resolv" (found with cat /var/log/dpkg.log | grep resolv). So, in the last hours this DNS-relevant package was updated.
Another information: the manual man systemd-resolved has the following line:
The hostnames "localhost" and "localhost.localdomain" (as well as any
hostname ending in ".localhost" or ".localhost.localdomain") are
resolved to the IP addresses 127.0.0.1 and ::1.
So this well-defined behaviour stopped working. I also can not remember changing anything related to this lowlevel DNS stuff myself.
The exact message when doing ping foo.bar.localhost is
ping: foo.bar.localhost: Name or service not known
Apparently the only bug "fixed" in the new version of resolvconf was this:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1817903
which is related to local resolving.
networking browser localhost web-development resolvconf
asked Mar 12 at 7:10
foobarfoobar
163
New contributor
foobar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
For years I'm using Ubuntu (currently on 18.10) to develop PHP applications on domains like foo.bar.localhost for local testing. These domains were resolved to 127.0.0.1 and handled by Apache 2.4. This always worked. The line 127.0.0.1 localhost is in my /etc/hosts like it always was.
Today morning I turned my device on and this did not work anymore. ping localhost is still working, but ping foo.bar.localhost is not (it still was working yesterday). Surprisingly Chromium is still resolving foo.bar.localhost, I assume it's not using the OS for DNS resolving. But I'm mainly using Firefox, which also stopped resolving localhost subdomains.
I didn't change any system-related settings yesterday, but I remember some package updates from yesterday, so I assume there were some changes to some network-related things. Is there any way to get dpgk to list install/update dates so that I can find out the exact packages that were updated?
What settings could I check to make resolving subdomains work again system-wide? Are there any known bugs?
Additional information: In /var/log/dpkg.log I found a recent entry upgrade resolvconf:all 1.79ubuntu10 1.79ubuntu10.18.10.1 which sounds relevant. This and the following subsequent lines are the only lines containing the term "resolv" (found with cat /var/log/dpkg.log | grep resolv). So, in the last hours this DNS-relevant package was updated.
Another information: the manual man systemd-resolved has the following line:
The hostnames "localhost" and "localhost.localdomain" (as well as any
hostname ending in ".localhost" or ".localhost.localdomain") are
resolved to the IP addresses 127.0.0.1 and ::1.
So this well-defined behaviour stopped working. I also can not remember changing anything related to this lowlevel DNS stuff myself.
The exact message when doing ping foo.bar.localhost is
ping: foo.bar.localhost: Name or service not known
Apparently the only bug "fixed" in the new version of resolvconf was this:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1817903
which is related to local resolving.
networking browser localhost web-development resolvconf
networking browser localhost web-development resolvconf
asked Mar 12 at 7:10
foobarfoobar
163
New contributor
foobar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Mar 12 at 7:10
foobarfoobar
163
New contributor
foobar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited Mar 12 at 10:13
foobar
asked Mar 12 at 7:10
foobarfoobar
163
New contributor
foobar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Mar 12 at 7:10
foobarfoobar
163
asked Mar 12 at 7:10
foobarfoobar
163
163
New contributor
foobar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
foobar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
foobar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The problem was having resolveconf installed at all alongside systemd-resolved. I removed it by apt-get purge resolvconf with root rights. Then everything worked again.
I assume having both installed was a left-over from some previous major version update between Ubuntu releases, which now triggered this strange behaviour.
answered Mar 12 at 11:33
foobarfoobar
163
New contributor
foobar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
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
});
}
});
foobar is a new contributor. Be nice, and check out our Code of Conduct.
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%2f1124952%2fdns-resolving-of-localhost-subdomains-stopped-working-after-resolvconf-update%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The problem was having resolveconf installed at all alongside systemd-resolved. I removed it by apt-get purge resolvconf with root rights. Then everything worked again.
I assume having both installed was a left-over from some previous major version update between Ubuntu releases, which now triggered this strange behaviour.
answered Mar 12 at 11:33
foobarfoobar
163
New contributor
foobar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
The problem was having resolveconf installed at all alongside systemd-resolved. I removed it by apt-get purge resolvconf with root rights. Then everything worked again.
I assume having both installed was a left-over from some previous major version update between Ubuntu releases, which now triggered this strange behaviour.
answered Mar 12 at 11:33
foobarfoobar
163
New contributor
foobar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
The problem was having resolveconf installed at all alongside systemd-resolved. I removed it by apt-get purge resolvconf with root rights. Then everything worked again.
I assume having both installed was a left-over from some previous major version update between Ubuntu releases, which now triggered this strange behaviour.
answered Mar 12 at 11:33
foobarfoobar
163
New contributor
foobar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
The problem was having resolveconf installed at all alongside systemd-resolved. I removed it by apt-get purge resolvconf with root rights. Then everything worked again.
I assume having both installed was a left-over from some previous major version update between Ubuntu releases, which now triggered this strange behaviour.
answered Mar 12 at 11:33
foobarfoobar
163
New contributor
foobar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Mar 12 at 11:33
foobarfoobar
163
New contributor
foobar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Mar 12 at 11:33
foobarfoobar
163
answered Mar 12 at 11:33
foobarfoobar
163
163
New contributor
foobar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
foobar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
foobar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
foobar is a new contributor. Be nice, and check out our Code of Conduct.
foobar is a new contributor. Be nice, and check out our Code of Conduct.
foobar is a new contributor. Be nice, and check out our Code of Conduct.
foobar is a new contributor. Be nice, and check out our Code of Conduct.
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%2f1124952%2fdns-resolving-of-localhost-subdomains-stopped-working-after-resolvconf-update%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
