Ubuntu 18.04 avahi-daemon unstable hostname.local resolution
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
On a local network im using a PC with Ubuntu 18.04 and i have two raspberry pi one of which is running pi-hole as DNS server (im not using its DHCP) and the other one has just a web server on it.
All the devices uses avahi-daemon.
The problem is pione.local
or pitwo.local
are not always resolved either via http or ssh.
Sometimes works then stops working and then works again ...
I tried several thing including :
- Playing with /etc/nsswitch.conf (tried a lot of combinations)
- Deactivating completely pi-hole to use the box DNS
- Editing hosts file to remove
127.0.1.1 pione
(for example) - Editing /etc/avahi/avahi-daemon.conf to change some parameters like publish-workstation, publish-domain, publish-addresses, ... none of it changed anything. (and avahi out of the box should just work i think)
- Tried to change the orginal ubuntu symlink of /etc/resolve.conf
/etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf
/etc/resolv.conf -> /run/systemd/resolve/resolv.conf
None of these seems to work ... resolution with hostname.local sometimes works and sometimes i have to enter the local ip of the device to access it.
Im getting out of ideas with this problem and i tend to think it's because of Ubuntu 18.04 settings which i haven't changed a lot from original settings.
Ideas are welcome !
Thanks.
18.04 raspberrypi avahi
add a comment |
On a local network im using a PC with Ubuntu 18.04 and i have two raspberry pi one of which is running pi-hole as DNS server (im not using its DHCP) and the other one has just a web server on it.
All the devices uses avahi-daemon.
The problem is pione.local
or pitwo.local
are not always resolved either via http or ssh.
Sometimes works then stops working and then works again ...
I tried several thing including :
- Playing with /etc/nsswitch.conf (tried a lot of combinations)
- Deactivating completely pi-hole to use the box DNS
- Editing hosts file to remove
127.0.1.1 pione
(for example) - Editing /etc/avahi/avahi-daemon.conf to change some parameters like publish-workstation, publish-domain, publish-addresses, ... none of it changed anything. (and avahi out of the box should just work i think)
- Tried to change the orginal ubuntu symlink of /etc/resolve.conf
/etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf
/etc/resolv.conf -> /run/systemd/resolve/resolv.conf
None of these seems to work ... resolution with hostname.local sometimes works and sometimes i have to enter the local ip of the device to access it.
Im getting out of ideas with this problem and i tend to think it's because of Ubuntu 18.04 settings which i haven't changed a lot from original settings.
Ideas are welcome !
Thanks.
18.04 raspberrypi avahi
add a comment |
On a local network im using a PC with Ubuntu 18.04 and i have two raspberry pi one of which is running pi-hole as DNS server (im not using its DHCP) and the other one has just a web server on it.
All the devices uses avahi-daemon.
The problem is pione.local
or pitwo.local
are not always resolved either via http or ssh.
Sometimes works then stops working and then works again ...
I tried several thing including :
- Playing with /etc/nsswitch.conf (tried a lot of combinations)
- Deactivating completely pi-hole to use the box DNS
- Editing hosts file to remove
127.0.1.1 pione
(for example) - Editing /etc/avahi/avahi-daemon.conf to change some parameters like publish-workstation, publish-domain, publish-addresses, ... none of it changed anything. (and avahi out of the box should just work i think)
- Tried to change the orginal ubuntu symlink of /etc/resolve.conf
/etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf
/etc/resolv.conf -> /run/systemd/resolve/resolv.conf
None of these seems to work ... resolution with hostname.local sometimes works and sometimes i have to enter the local ip of the device to access it.
Im getting out of ideas with this problem and i tend to think it's because of Ubuntu 18.04 settings which i haven't changed a lot from original settings.
Ideas are welcome !
Thanks.
18.04 raspberrypi avahi
On a local network im using a PC with Ubuntu 18.04 and i have two raspberry pi one of which is running pi-hole as DNS server (im not using its DHCP) and the other one has just a web server on it.
All the devices uses avahi-daemon.
The problem is pione.local
or pitwo.local
are not always resolved either via http or ssh.
Sometimes works then stops working and then works again ...
I tried several thing including :
- Playing with /etc/nsswitch.conf (tried a lot of combinations)
- Deactivating completely pi-hole to use the box DNS
- Editing hosts file to remove
127.0.1.1 pione
(for example) - Editing /etc/avahi/avahi-daemon.conf to change some parameters like publish-workstation, publish-domain, publish-addresses, ... none of it changed anything. (and avahi out of the box should just work i think)
- Tried to change the orginal ubuntu symlink of /etc/resolve.conf
/etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf
/etc/resolv.conf -> /run/systemd/resolve/resolv.conf
None of these seems to work ... resolution with hostname.local sometimes works and sometimes i have to enter the local ip of the device to access it.
Im getting out of ideas with this problem and i tend to think it's because of Ubuntu 18.04 settings which i haven't changed a lot from original settings.
Ideas are welcome !
Thanks.
18.04 raspberrypi avahi
18.04 raspberrypi avahi
asked Feb 10 at 14:36
ThomasThomas
1014
1014
add a comment |
add a comment |
0
active
oldest
votes
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%2f1117150%2fubuntu-18-04-avahi-daemon-unstable-hostname-local-resolution%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f1117150%2fubuntu-18-04-avahi-daemon-unstable-hostname-local-resolution%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