systemd starts dnsmasq before starting network manager?
1
Looks to me that my systemd starts dnsmasq before starting network manager. How can I confirm this? How can I force systemd starts dnsmasq after starting network manager?
Reason behind this is, as explained in NetworkManager not updating /var/run/networkmanager/resolv.conf,
- I'm using dnsmasq as my LAN DNS server, and
- I defined my two IP addresses in NetworkManager.
When my system started my dnsmasq is not working, and I found that the reason is it is not listening to my two IP addresses at all. Only after restarting it, it started to listen to my two IP addresses:
$ lsof -i tcp:53
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
systemd-r 544 systemd-resolve 13u IPv4 18667 0t0 TCP 127.0.0.53:domain (LISTEN)
dnsmasq 793 dnsmasq 5u IPv4 23719 0t0 TCP localhost.my.box.name:domain (LISTEN)
dnsmasq 793 dnsmasq 7u IPv6 23721 0t0 TCP ip6-localhost:domain (LISTEN)
/etc/init.d/dnsmasq restart
[ ok ] Restarting dnsmasq (via systemctl): dnsmasq.service.
$ lsof -i tcp:53
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
systemd-r 544 systemd-resolve 13u IPv4 18667 0t0 TCP 127.0.0.53:domain (LISTEN)
dnsmasq 17895 dnsmasq 5u IPv4 601091 0t0 TCP 192.168.0.10:domain (LISTEN)
dnsmasq 17895 dnsmasq 7u IPv4 601093 0t0 TCP 192.168.0.11:domain (LISTEN)
dnsmasq 17895 dnsmasq 9u IPv4 601095 0t0 TCP localhost...
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
# my systemd is not the latest but I think that shouldn't matter:
$ apt-cache policy systemd
systemd:
Installed: 237-3ubuntu10
Candidate: 237-3ubuntu10.9
Version table:
237-3ubuntu10.9 500
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
*** 237-3ubuntu10 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
Update:
@heynnema, Thanks for the systemd-analyze --no-pager blame, I've confirmed that the start order is as expected
NetworkManager -> systemd-resolved -> dnsmasq.
So indeed, it is about dnsmasq and systemd-resolved stepping on each others toes. I've added DNSStubListener=no since. I have two following up questions now.
- Why it is OK for dnsmasq
restartto work just fine? Its working fine gave me the impression that it is OK to have them both working. - Actually, I used
systemctl stop systemd-resolvedandsystemctl disable systemd-resolvedto completely disable systemd-resolved, instead of just stopping its listener previously. I don't know why it does not persist over reboot.
networking network-manager dns systemd dnsmasq
asked Mar 10 at 13:31
xptxpt
1247
|
show 3 more comments
1
Looks to me that my systemd starts dnsmasq before starting network manager. How can I confirm this? How can I force systemd starts dnsmasq after starting network manager?
Reason behind this is, as explained in NetworkManager not updating /var/run/networkmanager/resolv.conf,
- I'm using dnsmasq as my LAN DNS server, and
- I defined my two IP addresses in NetworkManager.
When my system started my dnsmasq is not working, and I found that the reason is it is not listening to my two IP addresses at all. Only after restarting it, it started to listen to my two IP addresses:
$ lsof -i tcp:53
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
systemd-r 544 systemd-resolve 13u IPv4 18667 0t0 TCP 127.0.0.53:domain (LISTEN)
dnsmasq 793 dnsmasq 5u IPv4 23719 0t0 TCP localhost.my.box.name:domain (LISTEN)
dnsmasq 793 dnsmasq 7u IPv6 23721 0t0 TCP ip6-localhost:domain (LISTEN)
/etc/init.d/dnsmasq restart
[ ok ] Restarting dnsmasq (via systemctl): dnsmasq.service.
$ lsof -i tcp:53
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
systemd-r 544 systemd-resolve 13u IPv4 18667 0t0 TCP 127.0.0.53:domain (LISTEN)
dnsmasq 17895 dnsmasq 5u IPv4 601091 0t0 TCP 192.168.0.10:domain (LISTEN)
dnsmasq 17895 dnsmasq 7u IPv4 601093 0t0 TCP 192.168.0.11:domain (LISTEN)
dnsmasq 17895 dnsmasq 9u IPv4 601095 0t0 TCP localhost...
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
# my systemd is not the latest but I think that shouldn't matter:
$ apt-cache policy systemd
systemd:
Installed: 237-3ubuntu10
Candidate: 237-3ubuntu10.9
Version table:
237-3ubuntu10.9 500
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
*** 237-3ubuntu10 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
Update:
@heynnema, Thanks for the systemd-analyze --no-pager blame, I've confirmed that the start order is as expected
NetworkManager -> systemd-resolved -> dnsmasq.
So indeed, it is about dnsmasq and systemd-resolved stepping on each others toes. I've added DNSStubListener=no since. I have two following up questions now.
- Why it is OK for dnsmasq
restartto work just fine? Its working fine gave me the impression that it is OK to have them both working. - Actually, I used
systemctl stop systemd-resolvedandsystemctl disable systemd-resolvedto completely disable systemd-resolved, instead of just stopping its listener previously. I don't know why it does not persist over reboot.
networking network-manager dns systemd dnsmasq
asked Mar 10 at 13:31
xptxpt
1247
First verify the start order withsystemd-analyze --no-pager blame- You seem to believe that the issue you dont describe comes from the start order. Maybe it just related to some misconfiguration?... Anyway, you can try to modify start order (ie: services/units dependencies) according to the freedesktop reference freedesktop.org/software/systemd/man/systemd.unit.html
– cmak.fr
Mar 10 at 14:12
1
As I answered in your TWO prior questions regarding your network configuration... you have to disable systemd-resolvedDNSStubListener=nowhen also running dnsmasq. If you don't want to do that, dnsmasq and systemd-resolved WILL step on each others toes. Is there some reason why you don't seem to want to do this?
– heynnema
Mar 10 at 15:33
@heynnema, thanks for helping, please see my updated OP.
– xpt
Mar 10 at 21:06
I read your update. And no... you don't "added DNSStubListener=no" to anything, you just edit /etc/systemd/resolved.conf. And no... you don't try and systemctl stop/disable systemd-resolved. You just need to follow my instructions and then leave it alone. Sorry if I sound a little miffed... this is the third time I'm recommending this, and that you stop trying to defeat the system. It was designed to work as it is... not some "customized" vision in your head. Sorry...
– heynnema
Mar 11 at 0:34
Sorry to be dense @heynnema, hmm... in my defense, I think the problem is that the question "Replace systemd-resolved with dnsmasq" was not fully answered, as I've explained better to "list the correct steps on how to replace systemd-resolved with dnsmasq, instead of correcting what I've been doing wrong". So I have to rely on steps in askubuntu.com/questions/898605 to cover the missing pieces, and systemctl stop/disable systemd-resolved was the accepted answer. I was not dong some "customized" vision in my head but following instructions.
– xpt
Mar 11 at 14:30
|
show 3 more comments
1
1
1
Looks to me that my systemd starts dnsmasq before starting network manager. How can I confirm this? How can I force systemd starts dnsmasq after starting network manager?
Reason behind this is, as explained in NetworkManager not updating /var/run/networkmanager/resolv.conf,
- I'm using dnsmasq as my LAN DNS server, and
- I defined my two IP addresses in NetworkManager.
When my system started my dnsmasq is not working, and I found that the reason is it is not listening to my two IP addresses at all. Only after restarting it, it started to listen to my two IP addresses:
$ lsof -i tcp:53
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
systemd-r 544 systemd-resolve 13u IPv4 18667 0t0 TCP 127.0.0.53:domain (LISTEN)
dnsmasq 793 dnsmasq 5u IPv4 23719 0t0 TCP localhost.my.box.name:domain (LISTEN)
dnsmasq 793 dnsmasq 7u IPv6 23721 0t0 TCP ip6-localhost:domain (LISTEN)
/etc/init.d/dnsmasq restart
[ ok ] Restarting dnsmasq (via systemctl): dnsmasq.service.
$ lsof -i tcp:53
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
systemd-r 544 systemd-resolve 13u IPv4 18667 0t0 TCP 127.0.0.53:domain (LISTEN)
dnsmasq 17895 dnsmasq 5u IPv4 601091 0t0 TCP 192.168.0.10:domain (LISTEN)
dnsmasq 17895 dnsmasq 7u IPv4 601093 0t0 TCP 192.168.0.11:domain (LISTEN)
dnsmasq 17895 dnsmasq 9u IPv4 601095 0t0 TCP localhost...
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
# my systemd is not the latest but I think that shouldn't matter:
$ apt-cache policy systemd
systemd:
Installed: 237-3ubuntu10
Candidate: 237-3ubuntu10.9
Version table:
237-3ubuntu10.9 500
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
*** 237-3ubuntu10 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
Update:
@heynnema, Thanks for the systemd-analyze --no-pager blame, I've confirmed that the start order is as expected
NetworkManager -> systemd-resolved -> dnsmasq.
So indeed, it is about dnsmasq and systemd-resolved stepping on each others toes. I've added DNSStubListener=no since. I have two following up questions now.
- Why it is OK for dnsmasq
restartto work just fine? Its working fine gave me the impression that it is OK to have them both working. - Actually, I used
systemctl stop systemd-resolvedandsystemctl disable systemd-resolvedto completely disable systemd-resolved, instead of just stopping its listener previously. I don't know why it does not persist over reboot.
networking network-manager dns systemd dnsmasq
asked Mar 10 at 13:31
xptxpt
1247
Looks to me that my systemd starts dnsmasq before starting network manager. How can I confirm this? How can I force systemd starts dnsmasq after starting network manager?
Reason behind this is, as explained in NetworkManager not updating /var/run/networkmanager/resolv.conf,
- I'm using dnsmasq as my LAN DNS server, and
- I defined my two IP addresses in NetworkManager.
When my system started my dnsmasq is not working, and I found that the reason is it is not listening to my two IP addresses at all. Only after restarting it, it started to listen to my two IP addresses:
$ lsof -i tcp:53
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
systemd-r 544 systemd-resolve 13u IPv4 18667 0t0 TCP 127.0.0.53:domain (LISTEN)
dnsmasq 793 dnsmasq 5u IPv4 23719 0t0 TCP localhost.my.box.name:domain (LISTEN)
dnsmasq 793 dnsmasq 7u IPv6 23721 0t0 TCP ip6-localhost:domain (LISTEN)
/etc/init.d/dnsmasq restart
[ ok ] Restarting dnsmasq (via systemctl): dnsmasq.service.
$ lsof -i tcp:53
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
systemd-r 544 systemd-resolve 13u IPv4 18667 0t0 TCP 127.0.0.53:domain (LISTEN)
dnsmasq 17895 dnsmasq 5u IPv4 601091 0t0 TCP 192.168.0.10:domain (LISTEN)
dnsmasq 17895 dnsmasq 7u IPv4 601093 0t0 TCP 192.168.0.11:domain (LISTEN)
dnsmasq 17895 dnsmasq 9u IPv4 601095 0t0 TCP localhost...
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
# my systemd is not the latest but I think that shouldn't matter:
$ apt-cache policy systemd
systemd:
Installed: 237-3ubuntu10
Candidate: 237-3ubuntu10.9
Version table:
237-3ubuntu10.9 500
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
*** 237-3ubuntu10 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
Update:
@heynnema, Thanks for the systemd-analyze --no-pager blame, I've confirmed that the start order is as expected
NetworkManager -> systemd-resolved -> dnsmasq.
So indeed, it is about dnsmasq and systemd-resolved stepping on each others toes. I've added DNSStubListener=no since. I have two following up questions now.
- Why it is OK for dnsmasq
restartto work just fine? Its working fine gave me the impression that it is OK to have them both working. - Actually, I used
systemctl stop systemd-resolvedandsystemctl disable systemd-resolvedto completely disable systemd-resolved, instead of just stopping its listener previously. I don't know why it does not persist over reboot.
networking network-manager dns systemd dnsmasq
networking network-manager dns systemd dnsmasq
asked Mar 10 at 13:31
xptxpt
1247
asked Mar 10 at 13:31
xptxpt
1247
edited Mar 10 at 21:06
xpt
asked Mar 10 at 13:31
xptxpt
1247
asked Mar 10 at 13:31
xptxpt
1247
asked Mar 10 at 13:31
xptxpt
1247
1247
First verify the start order withsystemd-analyze --no-pager blame- You seem to believe that the issue you dont describe comes from the start order. Maybe it just related to some misconfiguration?... Anyway, you can try to modify start order (ie: services/units dependencies) according to the freedesktop reference freedesktop.org/software/systemd/man/systemd.unit.html
– cmak.fr
Mar 10 at 14:12
1
As I answered in your TWO prior questions regarding your network configuration... you have to disable systemd-resolvedDNSStubListener=nowhen also running dnsmasq. If you don't want to do that, dnsmasq and systemd-resolved WILL step on each others toes. Is there some reason why you don't seem to want to do this?
– heynnema
Mar 10 at 15:33
@heynnema, thanks for helping, please see my updated OP.
– xpt
Mar 10 at 21:06
I read your update. And no... you don't "added DNSStubListener=no" to anything, you just edit /etc/systemd/resolved.conf. And no... you don't try and systemctl stop/disable systemd-resolved. You just need to follow my instructions and then leave it alone. Sorry if I sound a little miffed... this is the third time I'm recommending this, and that you stop trying to defeat the system. It was designed to work as it is... not some "customized" vision in your head. Sorry...
– heynnema
Mar 11 at 0:34
Sorry to be dense @heynnema, hmm... in my defense, I think the problem is that the question "Replace systemd-resolved with dnsmasq" was not fully answered, as I've explained better to "list the correct steps on how to replace systemd-resolved with dnsmasq, instead of correcting what I've been doing wrong". So I have to rely on steps in askubuntu.com/questions/898605 to cover the missing pieces, and systemctl stop/disable systemd-resolved was the accepted answer. I was not dong some "customized" vision in my head but following instructions.
– xpt
Mar 11 at 14:30
|
show 3 more comments
First verify the start order withsystemd-analyze --no-pager blame- You seem to believe that the issue you dont describe comes from the start order. Maybe it just related to some misconfiguration?... Anyway, you can try to modify start order (ie: services/units dependencies) according to the freedesktop reference freedesktop.org/software/systemd/man/systemd.unit.html
– cmak.fr
Mar 10 at 14:12
1
As I answered in your TWO prior questions regarding your network configuration... you have to disable systemd-resolvedDNSStubListener=nowhen also running dnsmasq. If you don't want to do that, dnsmasq and systemd-resolved WILL step on each others toes. Is there some reason why you don't seem to want to do this?
– heynnema
Mar 10 at 15:33
@heynnema, thanks for helping, please see my updated OP.
– xpt
Mar 10 at 21:06
I read your update. And no... you don't "added DNSStubListener=no" to anything, you just edit /etc/systemd/resolved.conf. And no... you don't try and systemctl stop/disable systemd-resolved. You just need to follow my instructions and then leave it alone. Sorry if I sound a little miffed... this is the third time I'm recommending this, and that you stop trying to defeat the system. It was designed to work as it is... not some "customized" vision in your head. Sorry...
– heynnema
Mar 11 at 0:34
Sorry to be dense @heynnema, hmm... in my defense, I think the problem is that the question "Replace systemd-resolved with dnsmasq" was not fully answered, as I've explained better to "list the correct steps on how to replace systemd-resolved with dnsmasq, instead of correcting what I've been doing wrong". So I have to rely on steps in askubuntu.com/questions/898605 to cover the missing pieces, and systemctl stop/disable systemd-resolved was the accepted answer. I was not dong some "customized" vision in my head but following instructions.
– xpt
Mar 11 at 14:30
First verify the start order with
systemd-analyze --no-pager blame - You seem to believe that the issue you dont describe comes from the start order. Maybe it just related to some misconfiguration?... Anyway, you can try to modify start order (ie: services/units dependencies) according to the freedesktop reference freedesktop.org/software/systemd/man/systemd.unit.html– cmak.fr
Mar 10 at 14:12
First verify the start order with
systemd-analyze --no-pager blame - You seem to believe that the issue you dont describe comes from the start order. Maybe it just related to some misconfiguration?... Anyway, you can try to modify start order (ie: services/units dependencies) according to the freedesktop reference freedesktop.org/software/systemd/man/systemd.unit.html– cmak.fr
Mar 10 at 14:12
1
1
As I answered in your TWO prior questions regarding your network configuration... you have to disable systemd-resolved
DNSStubListener=no when also running dnsmasq. If you don't want to do that, dnsmasq and systemd-resolved WILL step on each others toes. Is there some reason why you don't seem to want to do this?– heynnema
Mar 10 at 15:33
As I answered in your TWO prior questions regarding your network configuration... you have to disable systemd-resolved
DNSStubListener=no when also running dnsmasq. If you don't want to do that, dnsmasq and systemd-resolved WILL step on each others toes. Is there some reason why you don't seem to want to do this?– heynnema
Mar 10 at 15:33
@heynnema, thanks for helping, please see my updated OP.
– xpt
Mar 10 at 21:06
@heynnema, thanks for helping, please see my updated OP.
– xpt
Mar 10 at 21:06
I read your update. And no... you don't "added DNSStubListener=no" to anything, you just edit /etc/systemd/resolved.conf. And no... you don't try and systemctl stop/disable systemd-resolved. You just need to follow my instructions and then leave it alone. Sorry if I sound a little miffed... this is the third time I'm recommending this, and that you stop trying to defeat the system. It was designed to work as it is... not some "customized" vision in your head. Sorry...
– heynnema
Mar 11 at 0:34
I read your update. And no... you don't "added DNSStubListener=no" to anything, you just edit /etc/systemd/resolved.conf. And no... you don't try and systemctl stop/disable systemd-resolved. You just need to follow my instructions and then leave it alone. Sorry if I sound a little miffed... this is the third time I'm recommending this, and that you stop trying to defeat the system. It was designed to work as it is... not some "customized" vision in your head. Sorry...
– heynnema
Mar 11 at 0:34
Sorry to be dense @heynnema, hmm... in my defense, I think the problem is that the question "Replace systemd-resolved with dnsmasq" was not fully answered, as I've explained better to "list the correct steps on how to replace systemd-resolved with dnsmasq, instead of correcting what I've been doing wrong". So I have to rely on steps in askubuntu.com/questions/898605 to cover the missing pieces, and systemctl stop/disable systemd-resolved was the accepted answer. I was not dong some "customized" vision in my head but following instructions.
– xpt
Mar 11 at 14:30
Sorry to be dense @heynnema, hmm... in my defense, I think the problem is that the question "Replace systemd-resolved with dnsmasq" was not fully answered, as I've explained better to "list the correct steps on how to replace systemd-resolved with dnsmasq, instead of correcting what I've been doing wrong". So I have to rely on steps in askubuntu.com/questions/898605 to cover the missing pieces, and systemctl stop/disable systemd-resolved was the accepted answer. I was not dong some "customized" vision in my head but following instructions.
– xpt
Mar 11 at 14:30
|
show 3 more comments
1 Answer
1
active
oldest
votes
0
I had the same issue, but only on 16.04 systems updated to 18.04. I am also using dnsmasq as my LAN DNS and DHCP server.
On a freshly installed 18.04, it is working out of the box, without having to modify /etc/systemd/resolved.conf (DNSStubListener).
edited Mar 11 at 19:59
cmak.fr
2,1541021
answered Mar 11 at 17:03
M-JackM-Jack
1013
New contributor
M-Jack 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
});
}
});
draft saved
draft discarded
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%2f1124530%2fsystemd-starts-dnsmasq-before-starting-network-manager%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
0
I had the same issue, but only on 16.04 systems updated to 18.04. I am also using dnsmasq as my LAN DNS and DHCP server.
On a freshly installed 18.04, it is working out of the box, without having to modify /etc/systemd/resolved.conf (DNSStubListener).
edited Mar 11 at 19:59
cmak.fr
2,1541021
answered Mar 11 at 17:03
M-JackM-Jack
1013
New contributor
M-Jack 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 |
0
I had the same issue, but only on 16.04 systems updated to 18.04. I am also using dnsmasq as my LAN DNS and DHCP server.
On a freshly installed 18.04, it is working out of the box, without having to modify /etc/systemd/resolved.conf (DNSStubListener).
edited Mar 11 at 19:59
cmak.fr
2,1541021
answered Mar 11 at 17:03
M-JackM-Jack
1013
New contributor
M-Jack 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 |
0
0
0
I had the same issue, but only on 16.04 systems updated to 18.04. I am also using dnsmasq as my LAN DNS and DHCP server.
On a freshly installed 18.04, it is working out of the box, without having to modify /etc/systemd/resolved.conf (DNSStubListener).
edited Mar 11 at 19:59
cmak.fr
2,1541021
answered Mar 11 at 17:03
M-JackM-Jack
1013
New contributor
M-Jack is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I had the same issue, but only on 16.04 systems updated to 18.04. I am also using dnsmasq as my LAN DNS and DHCP server.
On a freshly installed 18.04, it is working out of the box, without having to modify /etc/systemd/resolved.conf (DNSStubListener).
edited Mar 11 at 19:59
cmak.fr
2,1541021
answered Mar 11 at 17:03
M-JackM-Jack
1013
New contributor
M-Jack is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited Mar 11 at 19:59
cmak.fr
2,1541021
edited Mar 11 at 19:59
cmak.fr
2,1541021
edited Mar 11 at 19:59
cmak.fr
2,1541021
2,1541021
answered Mar 11 at 17:03
M-JackM-Jack
1013
New contributor
M-Jack is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Mar 11 at 17:03
M-JackM-Jack
1013
answered Mar 11 at 17:03
M-JackM-Jack
1013
1013
New contributor
M-Jack is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
M-Jack is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
M-Jack 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 |
draft saved
draft discarded
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.
draft saved
draft discarded
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%2f1124530%2fsystemd-starts-dnsmasq-before-starting-network-manager%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
First verify the start order with
systemd-analyze --no-pager blame- You seem to believe that the issue you dont describe comes from the start order. Maybe it just related to some misconfiguration?... Anyway, you can try to modify start order (ie: services/units dependencies) according to the freedesktop reference freedesktop.org/software/systemd/man/systemd.unit.html– cmak.fr
Mar 10 at 14:12
1
As I answered in your TWO prior questions regarding your network configuration... you have to disable systemd-resolved
DNSStubListener=nowhen also running dnsmasq. If you don't want to do that, dnsmasq and systemd-resolved WILL step on each others toes. Is there some reason why you don't seem to want to do this?– heynnema
Mar 10 at 15:33
@heynnema, thanks for helping, please see my updated OP.
– xpt
Mar 10 at 21:06
I read your update. And no... you don't "added DNSStubListener=no" to anything, you just edit /etc/systemd/resolved.conf. And no... you don't try and systemctl stop/disable systemd-resolved. You just need to follow my instructions and then leave it alone. Sorry if I sound a little miffed... this is the third time I'm recommending this, and that you stop trying to defeat the system. It was designed to work as it is... not some "customized" vision in your head. Sorry...
– heynnema
Mar 11 at 0:34
Sorry to be dense @heynnema, hmm... in my defense, I think the problem is that the question "Replace systemd-resolved with dnsmasq" was not fully answered, as I've explained better to "list the correct steps on how to replace systemd-resolved with dnsmasq, instead of correcting what I've been doing wrong". So I have to rely on steps in askubuntu.com/questions/898605 to cover the missing pieces, and systemctl stop/disable systemd-resolved was the accepted answer. I was not dong some "customized" vision in my head but following instructions.
– xpt
Mar 11 at 14:30