Can't resolve hostname in local network - whats wrong with my resolver configuration?
Clash 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.
networking dns systemd
asked May 10 at 6:26
IanH
131116
add a comment |Â
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.
networking dns systemd
asked May 10 at 6:26
IanH
131116
1
hostdoes not use NSS. It directly queries DNS servers specified in/etc/resolv.conf. Please show your/etc/resolv.confcontents.
– intelfx
May 11 at 16:03
/etc/resolv.conf:nameserver 127.0.0.53However, the problem is not only thehostcommand - I can't resolvecubietruckat all, e.gping cubietruckdoesn't work, too.
– IanH
May 13 at 18:15
does it work withsystemd-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
add a comment |Â
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.
networking dns systemd
asked May 10 at 6:26
IanH
131116
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.
networking dns systemd
asked May 10 at 6:26
IanH
131116
asked May 10 at 6:26
IanH
131116
asked May 10 at 6:26
IanH
131116
asked May 10 at 6:26
IanH
131116
131116
1
hostdoes not use NSS. It directly queries DNS servers specified in/etc/resolv.conf. Please show your/etc/resolv.confcontents.
– intelfx
May 11 at 16:03
/etc/resolv.conf:nameserver 127.0.0.53However, the problem is not only thehostcommand - I can't resolvecubietruckat all, e.gping cubietruckdoesn't work, too.
– IanH
May 13 at 18:15
does it work withsystemd-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
add a comment |Â
1
hostdoes not use NSS. It directly queries DNS servers specified in/etc/resolv.conf. Please show your/etc/resolv.confcontents.
– intelfx
May 11 at 16:03
/etc/resolv.conf:nameserver 127.0.0.53However, the problem is not only thehostcommand - I can't resolvecubietruckat all, e.gping cubietruckdoesn't work, too.
– IanH
May 13 at 18:15
does it work withsystemd-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
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Â
draft saved
draft discarded
Â
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
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
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
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
1
hostdoes not use NSS. It directly queries DNS servers specified in/etc/resolv.conf. Please show your/etc/resolv.confcontents.– intelfx
May 11 at 16:03
/etc/resolv.conf:
nameserver 127.0.0.53However, the problem is not only thehostcommand - I can't resolvecubietruckat all, e.gping cubietruckdoesn'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