Can't resolve hostname in local network - whats wrong with my resolver configuration?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
3
down vote

favorite












I'm using kubuntu 18.04 (upgraded from various previous versions (non-LTS)) and have problems to resolv hostnames in my local network. No DNS query is sent to the resolver for local names (confirmed by wireshark).
If I direcly ask the resolver, the name is resolved:



ian@martok:~$ host cubietruck
Host cubietruck not found: 2(SERVFAIL)

ian@martok:~$ host cubietruck 192.168.0.5
Using domain server:
Name: 192.168.0.5
Address: 192.168.0.5#53
Aliases:

cubietruck has address 192.168.0.220


The systemd resolver configuration looks fine:



ian@martok:~$ systemd-resolve --status 
Global
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
[...]
corp
d.f.ip6.arpa
home
internal
intranet
lan
local
private
test

Link 2 (eth0)
Current Scopes: DNS
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
DNS Servers: 192.168.0.5


I also changed /etc/nsswitch.conf, but that does no change the behaviour (even after reboot) (old line commented out):



#hosts: files mdns4_minimal resolve [!UNAVAIL=return] dns mdns4
hosts: files mdns4_minimal resolve dns [!UNAVAIL=return] mdns4


Other device in my network can resolv local hostnames correctly.







share|improve this question
















  • 1




    host does not use NSS. It directly queries DNS servers specified in /etc/resolv.conf. Please show your /etc/resolv.conf contents.
    – intelfx
    May 11 at 16:03










  • /etc/resolv.conf: nameserver 127.0.0.53 However, the problem is not only the host command - I can't resolve cubietruck at all, e.g ping cubietruck doesn't work, too.
    – IanH
    May 13 at 18:15











  • does it work with systemd-resolve cubietruck?
    – intelfx
    May 13 at 18:38










  • Nope: ian@martok:~$ systemd-resolve cubietruck : cubietruck: resolve call failed: No appropriate name servers or networks for name found
    – IanH
    May 13 at 19:08















up vote
3
down vote

favorite












I'm using kubuntu 18.04 (upgraded from various previous versions (non-LTS)) and have problems to resolv hostnames in my local network. No DNS query is sent to the resolver for local names (confirmed by wireshark).
If I direcly ask the resolver, the name is resolved:



ian@martok:~$ host cubietruck
Host cubietruck not found: 2(SERVFAIL)

ian@martok:~$ host cubietruck 192.168.0.5
Using domain server:
Name: 192.168.0.5
Address: 192.168.0.5#53
Aliases:

cubietruck has address 192.168.0.220


The systemd resolver configuration looks fine:



ian@martok:~$ systemd-resolve --status 
Global
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
[...]
corp
d.f.ip6.arpa
home
internal
intranet
lan
local
private
test

Link 2 (eth0)
Current Scopes: DNS
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
DNS Servers: 192.168.0.5


I also changed /etc/nsswitch.conf, but that does no change the behaviour (even after reboot) (old line commented out):



#hosts: files mdns4_minimal resolve [!UNAVAIL=return] dns mdns4
hosts: files mdns4_minimal resolve dns [!UNAVAIL=return] mdns4


Other device in my network can resolv local hostnames correctly.







share|improve this question
















  • 1




    host does not use NSS. It directly queries DNS servers specified in /etc/resolv.conf. Please show your /etc/resolv.conf contents.
    – intelfx
    May 11 at 16:03










  • /etc/resolv.conf: nameserver 127.0.0.53 However, the problem is not only the host command - I can't resolve cubietruck at all, e.g ping cubietruck doesn't work, too.
    – IanH
    May 13 at 18:15











  • does it work with systemd-resolve cubietruck?
    – intelfx
    May 13 at 18:38










  • Nope: ian@martok:~$ systemd-resolve cubietruck : cubietruck: resolve call failed: No appropriate name servers or networks for name found
    – IanH
    May 13 at 19:08













up vote
3
down vote

favorite









up vote
3
down vote

favorite











I'm using kubuntu 18.04 (upgraded from various previous versions (non-LTS)) and have problems to resolv hostnames in my local network. No DNS query is sent to the resolver for local names (confirmed by wireshark).
If I direcly ask the resolver, the name is resolved:



ian@martok:~$ host cubietruck
Host cubietruck not found: 2(SERVFAIL)

ian@martok:~$ host cubietruck 192.168.0.5
Using domain server:
Name: 192.168.0.5
Address: 192.168.0.5#53
Aliases:

cubietruck has address 192.168.0.220


The systemd resolver configuration looks fine:



ian@martok:~$ systemd-resolve --status 
Global
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
[...]
corp
d.f.ip6.arpa
home
internal
intranet
lan
local
private
test

Link 2 (eth0)
Current Scopes: DNS
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
DNS Servers: 192.168.0.5


I also changed /etc/nsswitch.conf, but that does no change the behaviour (even after reboot) (old line commented out):



#hosts: files mdns4_minimal resolve [!UNAVAIL=return] dns mdns4
hosts: files mdns4_minimal resolve dns [!UNAVAIL=return] mdns4


Other device in my network can resolv local hostnames correctly.







share|improve this question












I'm using kubuntu 18.04 (upgraded from various previous versions (non-LTS)) and have problems to resolv hostnames in my local network. No DNS query is sent to the resolver for local names (confirmed by wireshark).
If I direcly ask the resolver, the name is resolved:



ian@martok:~$ host cubietruck
Host cubietruck not found: 2(SERVFAIL)

ian@martok:~$ host cubietruck 192.168.0.5
Using domain server:
Name: 192.168.0.5
Address: 192.168.0.5#53
Aliases:

cubietruck has address 192.168.0.220


The systemd resolver configuration looks fine:



ian@martok:~$ systemd-resolve --status 
Global
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
[...]
corp
d.f.ip6.arpa
home
internal
intranet
lan
local
private
test

Link 2 (eth0)
Current Scopes: DNS
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
DNS Servers: 192.168.0.5


I also changed /etc/nsswitch.conf, but that does no change the behaviour (even after reboot) (old line commented out):



#hosts: files mdns4_minimal resolve [!UNAVAIL=return] dns mdns4
hosts: files mdns4_minimal resolve dns [!UNAVAIL=return] mdns4


Other device in my network can resolv local hostnames correctly.









share|improve this question











share|improve this question




share|improve this question










asked May 10 at 6:26









IanH

131116




131116







  • 1




    host does not use NSS. It directly queries DNS servers specified in /etc/resolv.conf. Please show your /etc/resolv.conf contents.
    – intelfx
    May 11 at 16:03










  • /etc/resolv.conf: nameserver 127.0.0.53 However, the problem is not only the host command - I can't resolve cubietruck at all, e.g ping cubietruck doesn't work, too.
    – IanH
    May 13 at 18:15











  • does it work with systemd-resolve cubietruck?
    – intelfx
    May 13 at 18:38










  • Nope: ian@martok:~$ systemd-resolve cubietruck : cubietruck: resolve call failed: No appropriate name servers or networks for name found
    – IanH
    May 13 at 19:08













  • 1




    host does not use NSS. It directly queries DNS servers specified in /etc/resolv.conf. Please show your /etc/resolv.conf contents.
    – intelfx
    May 11 at 16:03










  • /etc/resolv.conf: nameserver 127.0.0.53 However, the problem is not only the host command - I can't resolve cubietruck at all, e.g ping cubietruck doesn't work, too.
    – IanH
    May 13 at 18:15











  • does it work with systemd-resolve cubietruck?
    – intelfx
    May 13 at 18:38










  • Nope: ian@martok:~$ systemd-resolve cubietruck : cubietruck: resolve call failed: No appropriate name servers or networks for name found
    – IanH
    May 13 at 19:08








1




1




host does not use NSS. It directly queries DNS servers specified in /etc/resolv.conf. Please show your /etc/resolv.conf contents.
– intelfx
May 11 at 16:03




host does not use NSS. It directly queries DNS servers specified in /etc/resolv.conf. Please show your /etc/resolv.conf contents.
– intelfx
May 11 at 16:03












/etc/resolv.conf: nameserver 127.0.0.53 However, the problem is not only the host command - I can't resolve cubietruck at all, e.g ping cubietruck doesn't work, too.
– IanH
May 13 at 18:15





/etc/resolv.conf: nameserver 127.0.0.53 However, the problem is not only the host command - I can't resolve cubietruck at all, e.g ping cubietruck doesn't work, too.
– IanH
May 13 at 18:15













does it work with systemd-resolve cubietruck?
– intelfx
May 13 at 18:38




does it work with systemd-resolve cubietruck?
– intelfx
May 13 at 18:38












Nope: ian@martok:~$ systemd-resolve cubietruck : cubietruck: resolve call failed: No appropriate name servers or networks for name found
– IanH
May 13 at 19:08





Nope: ian@martok:~$ systemd-resolve cubietruck : cubietruck: resolve call failed: No appropriate name servers or networks for name found
– IanH
May 13 at 19:08
















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',
convertImagesToLinks: true,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);








 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1034353%2fcant-resolve-hostname-in-local-network-whats-wrong-with-my-resolver-configura%23new-answer', 'question_page');

);

Post as a guest



































active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes










 

draft saved


draft discarded


























 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1034353%2fcant-resolve-hostname-in-local-network-whats-wrong-with-my-resolver-configura%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

Which professions warranted travel in Medieval times?

How do so many people here on Academia.SE, and in general, afford lavish higher education programs?

Trouble downloading packages list due to a “Hash sum mismatch” error