how to disable LLMNR on ubuntu 17.10

My understanding is that if i am using third party dns (google, etc) or dns provided by my ISP(comcast, etc) i do not need this feature on. I am attempting to disable it but setting LLMNR=no in /etc/systemd/resolved.conf and restarting the box does not seem to work.

How can i go about achieving this goal?

Thanks

edited Jan 11 '18 at 13:34

GAD3R

27.3k1858113

asked Jan 11 '18 at 0:32

user964491

1011

bumped to the homepage by Community♦ 7 mins ago

This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

LLMNR and DNS are not mutually exclusive, they complement each other. LLMNR only resolves link-local names, i.e. the names of the computers on your local LAN. A "third-party" DNS server, on the other hand, does not resolve your link-local host names to IP addresses, unless you have registered your own domain and entered records for your hosts.

– Johan Myréen
Jan 11 '18 at 7:45

How did you determine that LLMNR was disabled after editing the config file? Also note that you will have to ensure MulticastDNS is also turned off, since mDNS provides a similar service.

– Johan Myréen
Jan 11 '18 at 7:49

add a comment |

How can i go about achieving this goal?

Thanks

edited Jan 11 '18 at 13:34

GAD3R

27.3k1858113

asked Jan 11 '18 at 0:32

user964491

1011

bumped to the homepage by Community♦ 7 mins ago

This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

LLMNR and DNS are not mutually exclusive, they complement each other. LLMNR only resolves link-local names, i.e. the names of the computers on your local LAN. A "third-party" DNS server, on the other hand, does not resolve your link-local host names to IP addresses, unless you have registered your own domain and entered records for your hosts.

– Johan Myréen
Jan 11 '18 at 7:45

How did you determine that LLMNR was disabled after editing the config file? Also note that you will have to ensure MulticastDNS is also turned off, since mDNS provides a similar service.

– Johan Myréen
Jan 11 '18 at 7:49

add a comment |

How can i go about achieving this goal?

Thanks

edited Jan 11 '18 at 13:34

GAD3R

27.3k1858113

asked Jan 11 '18 at 0:32

user964491

1011

How can i go about achieving this goal?

Thanks

linux ubuntu systemd systemd-resolved

edited Jan 11 '18 at 13:34

GAD3R

27.3k1858113

asked Jan 11 '18 at 0:32

user964491

1011

edited Jan 11 '18 at 13:34

GAD3R

27.3k1858113

asked Jan 11 '18 at 0:32

user964491

1011

edited Jan 11 '18 at 13:34

GAD3R

27.3k1858113

edited Jan 11 '18 at 13:34

GAD3R

27.3k1858113

edited Jan 11 '18 at 13:34

GAD3R

27.3k1858113

asked Jan 11 '18 at 0:32

user964491

1011

asked Jan 11 '18 at 0:32

user964491

1011

asked Jan 11 '18 at 0:32

user964491

1011

bumped to the homepage by Community♦ 7 mins 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♦ 7 mins ago

This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

LLMNR and DNS are not mutually exclusive, they complement each other. LLMNR only resolves link-local names, i.e. the names of the computers on your local LAN. A "third-party" DNS server, on the other hand, does not resolve your link-local host names to IP addresses, unless you have registered your own domain and entered records for your hosts.

– Johan Myréen
Jan 11 '18 at 7:45

How did you determine that LLMNR was disabled after editing the config file? Also note that you will have to ensure MulticastDNS is also turned off, since mDNS provides a similar service.

– Johan Myréen
Jan 11 '18 at 7:49

add a comment |

LLMNR and DNS are not mutually exclusive, they complement each other. LLMNR only resolves link-local names, i.e. the names of the computers on your local LAN. A "third-party" DNS server, on the other hand, does not resolve your link-local host names to IP addresses, unless you have registered your own domain and entered records for your hosts.

– Johan Myréen
Jan 11 '18 at 7:45

How did you determine that LLMNR was disabled after editing the config file? Also note that you will have to ensure MulticastDNS is also turned off, since mDNS provides a similar service.

– Johan Myréen
Jan 11 '18 at 7:49

LLMNR and DNS are not mutually exclusive, they complement each other. LLMNR only resolves link-local names, i.e. the names of the computers on your local LAN. A "third-party" DNS server, on the other hand, does not resolve your link-local host names to IP addresses, unless you have registered your own domain and entered records for your hosts.

– Johan Myréen
Jan 11 '18 at 7:45

How did you determine that LLMNR was disabled after editing the config file? Also note that you will have to ensure MulticastDNS is also turned off, since mDNS provides a similar service.

– Johan Myréen
Jan 11 '18 at 7:49

add a comment |

1 Answer
1

active

oldest

votes

After adding LLMNR=no to /etc/systemd/resolved.conf you should start the systemd-resolved.service service:

sudo systemctl start systemd-resolved.service

Then create a symlink:

sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf

enable the service:

sudo systemctl enable systemd-resolved.service

edited Jan 11 '18 at 13:56

Johan Myréen

7,86211625

answered Jan 11 '18 at 13:40

GAD3R

27.3k1858113

Since the OP was asking how to disable LLMNR, he/she already had systemd-resolved enabled and running. A restart is probably a good idea after changing the configuration, though.

– Johan Myréen
Jan 11 '18 at 14:02

@JohanMyréen By default the systemd-resolved is disable also making the /run/systemd/resolve/resolv.conf accessible from /etc/resolv.conf by creating a symlink.

– GAD3R
Jan 11 '18 at 14:04

The OP asked how to disable LLMNR provided by systemd-resolved, so I don't see how this applies to a situation were systemd-resolved was not enabled, regardless of what the default is.

– Johan Myréen
Jan 11 '18 at 14:09

add a comment |

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',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f416256%2fhow-to-disable-llmnr-on-ubuntu-17-10%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

After adding LLMNR=no to /etc/systemd/resolved.conf you should start the systemd-resolved.service service:

sudo systemctl start systemd-resolved.service

Then create a symlink:

sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf

enable the service:

sudo systemctl enable systemd-resolved.service

edited Jan 11 '18 at 13:56

Johan Myréen

7,86211625

answered Jan 11 '18 at 13:40

GAD3R

27.3k1858113

Since the OP was asking how to disable LLMNR, he/she already had systemd-resolved enabled and running. A restart is probably a good idea after changing the configuration, though.

– Johan Myréen
Jan 11 '18 at 14:02

@JohanMyréen By default the systemd-resolved is disable also making the /run/systemd/resolve/resolv.conf accessible from /etc/resolv.conf by creating a symlink.

– GAD3R
Jan 11 '18 at 14:04

The OP asked how to disable LLMNR provided by systemd-resolved, so I don't see how this applies to a situation were systemd-resolved was not enabled, regardless of what the default is.

– Johan Myréen
Jan 11 '18 at 14:09

add a comment |

After adding LLMNR=no to /etc/systemd/resolved.conf you should start the systemd-resolved.service service:

sudo systemctl start systemd-resolved.service

Then create a symlink:

sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf

enable the service:

sudo systemctl enable systemd-resolved.service

edited Jan 11 '18 at 13:56

Johan Myréen

7,86211625

answered Jan 11 '18 at 13:40

GAD3R

27.3k1858113

Since the OP was asking how to disable LLMNR, he/she already had systemd-resolved enabled and running. A restart is probably a good idea after changing the configuration, though.

– Johan Myréen
Jan 11 '18 at 14:02

@JohanMyréen By default the systemd-resolved is disable also making the /run/systemd/resolve/resolv.conf accessible from /etc/resolv.conf by creating a symlink.

– GAD3R
Jan 11 '18 at 14:04

The OP asked how to disable LLMNR provided by systemd-resolved, so I don't see how this applies to a situation were systemd-resolved was not enabled, regardless of what the default is.

– Johan Myréen
Jan 11 '18 at 14:09

add a comment |

After adding LLMNR=no to /etc/systemd/resolved.conf you should start the systemd-resolved.service service:

sudo systemctl start systemd-resolved.service

Then create a symlink:

sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf

enable the service:

sudo systemctl enable systemd-resolved.service

edited Jan 11 '18 at 13:56

Johan Myréen

7,86211625

answered Jan 11 '18 at 13:40

GAD3R

27.3k1858113

After adding LLMNR=no to /etc/systemd/resolved.conf you should start the systemd-resolved.service service:

sudo systemctl start systemd-resolved.service

Then create a symlink:

sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf

enable the service:

sudo systemctl enable systemd-resolved.service

edited Jan 11 '18 at 13:56

Johan Myréen

7,86211625

answered Jan 11 '18 at 13:40

GAD3R

27.3k1858113

edited Jan 11 '18 at 13:56

Johan Myréen

7,86211625

edited Jan 11 '18 at 13:56

Johan Myréen

7,86211625

edited Jan 11 '18 at 13:56

Johan Myréen

7,86211625

answered Jan 11 '18 at 13:40

GAD3R

27.3k1858113

answered Jan 11 '18 at 13:40

GAD3R

27.3k1858113

answered Jan 11 '18 at 13:40

GAD3R

27.3k1858113

Since the OP was asking how to disable LLMNR, he/she already had systemd-resolved enabled and running. A restart is probably a good idea after changing the configuration, though.

– Johan Myréen
Jan 11 '18 at 14:02

@JohanMyréen By default the systemd-resolved is disable also making the /run/systemd/resolve/resolv.conf accessible from /etc/resolv.conf by creating a symlink.

– GAD3R
Jan 11 '18 at 14:04

The OP asked how to disable LLMNR provided by systemd-resolved, so I don't see how this applies to a situation were systemd-resolved was not enabled, regardless of what the default is.

– Johan Myréen
Jan 11 '18 at 14:09

add a comment |

Since the OP was asking how to disable LLMNR, he/she already had systemd-resolved enabled and running. A restart is probably a good idea after changing the configuration, though.

– Johan Myréen
Jan 11 '18 at 14:02

@JohanMyréen By default the systemd-resolved is disable also making the /run/systemd/resolve/resolv.conf accessible from /etc/resolv.conf by creating a symlink.

– GAD3R
Jan 11 '18 at 14:04

The OP asked how to disable LLMNR provided by systemd-resolved, so I don't see how this applies to a situation were systemd-resolved was not enabled, regardless of what the default is.

– Johan Myréen
Jan 11 '18 at 14:09

Since the OP was asking how to disable LLMNR, he/she already had systemd-resolved enabled and running. A restart is probably a good idea after changing the configuration, though.

– Johan Myréen
Jan 11 '18 at 14:02

@JohanMyréen By default the systemd-resolved is disable also making the /run/systemd/resolve/resolv.conf accessible from /etc/resolv.conf by creating a symlink.

– GAD3R
Jan 11 '18 at 14:04

The OP asked how to disable LLMNR provided by systemd-resolved, so I don't see how this applies to a situation were systemd-resolved was not enabled, regardless of what the default is.

– Johan Myréen
Jan 11 '18 at 14:09

add a comment |

draft saved

draft discarded

Thanks for contributing an answer to Unix & Linux Stack Exchange!

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');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Sstrhsrtj