[Bug 1751797] Re: dns resolution only works for domains in 'search'.
Scott Moser
ssmoser2+ubuntu at gmail.com
Thu Mar 15 13:58:39 UTC 2018
connection.id: System Ethernet
connection.uuid: 72c7fac3-c017-4b76-9954-b4fb08262376
connection.stable-id: --
connection.type: 802-3-ethernet
connection.interface-name: --
connection.autoconnect: yes
connection.autoconnect-priority: 0
connection.autoconnect-retries: -1 (default)
connection.auth-retries: -1
connection.timestamp: 1521122033
connection.read-only: no
connection.permissions: --
connection.zone: --
connection.master: --
connection.slave-type: --
connection.autoconnect-slaves: -1 (default)
connection.secondaries: --
connection.gateway-ping-timeout: 0
connection.metered: unknown
connection.lldp: default
802-3-ethernet.port: --
802-3-ethernet.speed: 0
802-3-ethernet.duplex: --
802-3-ethernet.auto-negotiate: no
802-3-ethernet.mac-address: --
802-3-ethernet.cloned-mac-address: --
802-3-ethernet.generate-mac-address-mask:--
802-3-ethernet.mac-address-blacklist: --
802-3-ethernet.mtu: auto
802-3-ethernet.s390-subchannels: --
802-3-ethernet.s390-nettype: --
802-3-ethernet.s390-options: --
802-3-ethernet.wake-on-lan: default
802-3-ethernet.wake-on-lan-password: --
ipv4.method: auto
ipv4.dns: --
ipv4.dns-search: --
ipv4.dns-options: ""
ipv4.dns-priority: 0
ipv4.addresses: --
ipv4.gateway: --
ipv4.routes: --
ipv4.route-metric: -1
ipv4.route-table: 0 (unspec)
ipv4.ignore-auto-routes: no
ipv4.ignore-auto-dns: no
ipv4.dhcp-client-id: --
ipv4.dhcp-timeout: 0 (default)
ipv4.dhcp-send-hostname: yes
ipv4.dhcp-hostname: --
ipv4.dhcp-fqdn: --
ipv4.never-default: no
ipv4.may-fail: yes
ipv4.dad-timeout: -1 (default)
ipv6.method: auto
ipv6.dns: --
ipv6.dns-search: --
ipv6.dns-options: ""
ipv6.dns-priority: 0
ipv6.addresses: --
ipv6.gateway: --
ipv6.routes: --
ipv6.route-metric: -1
ipv6.route-table: 0 (unspec)
ipv6.ignore-auto-routes: no
ipv6.ignore-auto-dns: no
ipv6.never-default: no
ipv6.may-fail: yes
ipv6.ip6-privacy: -1 (unknown)
ipv6.addr-gen-mode: stable-privacy
ipv6.dhcp-send-hostname: yes
ipv6.dhcp-hostname: --
ipv6.token: --
proxy.method: none
proxy.browser-only: no
proxy.pac-url: --
proxy.pac-script: --
GENERAL.NAME: System Ethernet
GENERAL.UUID: 72c7fac3-c017-4b76-9954-b4fb08262376
GENERAL.DEVICES: enp0s25
GENERAL.STATE: activated
GENERAL.DEFAULT: yes
GENERAL.DEFAULT6: no
GENERAL.SPEC-OBJECT: --
GENERAL.VPN: no
GENERAL.DBUS-PATH: /org/freedesktop/NetworkManager/ActiveConnection/1
GENERAL.CON-PATH: /org/freedesktop/NetworkManager/Settings/1
GENERAL.ZONE: --
GENERAL.MASTER-PATH: --
IP4.ADDRESS[1]: 10.7.2.103/16
IP4.GATEWAY: 10.7.0.1
IP4.ROUTE[1]: dst = 0.0.0.0/0, nh = 10.7.0.1, mt = 100
IP4.ROUTE[2]: dst = 10.7.0.0/16, nh = 0.0.0.0, mt = 100
IP4.ROUTE[3]: dst = 169.254.0.0/16, nh = 0.0.0.0, mt = 1000
IP4.DNS[1]: 10.7.0.1
IP4.DOMAIN[1]: mydomain.com
DHCP4.OPTION[1]: requested_subnet_mask = 1
DHCP4.OPTION[2]: requested_rfc3442_classless_static_routes = 1
DHCP4.OPTION[3]: subnet_mask = 255.255.0.0
DHCP4.OPTION[4]: domain_name_servers = 10.7.0.1
DHCP4.OPTION[5]: ip_address = 10.7.2.103
DHCP4.OPTION[6]: filename = pxelinux.0
DHCP4.OPTION[7]: requested_static_routes = 1
DHCP4.OPTION[8]: dhcp_server_identifier = 10.7.0.1
DHCP4.OPTION[9]: requested_time_offset = 1
DHCP4.OPTION[10]: broadcast_address = 10.7.255.255
DHCP4.OPTION[11]: requested_interface_mtu = 1
DHCP4.OPTION[12]: dhcp_rebinding_time = 37800
DHCP4.OPTION[13]: requested_domain_name_servers = 1
DHCP4.OPTION[14]: dhcp_message_type = 5
DHCP4.OPTION[15]: requested_broadcast_address = 1
DHCP4.OPTION[16]: routers = 10.7.0.1
DHCP4.OPTION[17]: dhcp_renewal_time = 21600
DHCP4.OPTION[18]: requested_domain_name = 1
DHCP4.OPTION[19]: domain_name = mydomain.com
DHCP4.OPTION[20]: requested_routers = 1
DHCP4.OPTION[21]: expiry = 1521163136
DHCP4.OPTION[22]: requested_wpad = 1
DHCP4.OPTION[23]: requested_netbios_scope = 1
DHCP4.OPTION[24]: host_name = milhouse-eth0
DHCP4.OPTION[25]: requested_ms_classless_static_routes = 1
DHCP4.OPTION[26]: requested_netbios_name_servers = 1
DHCP4.OPTION[27]: network_number = 10.7.0.0
DHCP4.OPTION[28]: requested_domain_search = 1
DHCP4.OPTION[29]: next_server = 10.7.10.1
DHCP4.OPTION[30]: requested_ntp_servers = 1
DHCP4.OPTION[31]: requested_host_name = 1
DHCP4.OPTION[32]: dhcp_lease_time = 43200
IP6.ADDRESS[1]: fdfd:dddd:dddd::9fa/128
IP6.ADDRESS[2]: fdfd:dddd:dddd:0:20f8:fe9c:5b0b:14d5/64
IP6.ADDRESS[3]: fdfd:dddd:dddd:0:4aeb:70e7:3e74:10c5/64
IP6.ADDRESS[4]: fe80::64f4:6bde:246e:6d80/64
IP6.GATEWAY: --
IP6.ROUTE[1]: dst = fdfd:dddd:dddd::/48, nh = fe80::c24a:ff:fedd:541e, mt = 100
IP6.ROUTE[2]: dst = fdfd:dddd:dddd::/64, nh = ::, mt = 100
IP6.ROUTE[3]: dst = ff00::/8, nh = ::, mt = 256, table=255
IP6.ROUTE[4]: dst = fe80::/64, nh = ::, mt = 256
IP6.ROUTE[5]: dst = fe80::/64, nh = ::, mt = 100
IP6.ROUTE[6]: dst = fdfd:dddd:dddd::9fa/128, nh = ::, mt = 100
IP6.DNS[1]: fdfd:dddd:dddd::1
DHCP6.OPTION[1]: dhcp6_client_id = 0:4:b6:a3:4e:94:10:5a:74:69:20:d6:3e:4:14:31:a7:63
DHCP6.OPTION[2]: dhcp6_unknown_11 = 3:1:0:5a:aa:72:c4:0:0:0:82:1:bc:31:b9:64:a2:c2:f1:d3:a9:5d:fe:ae:97:e5:60:c9
DHCP6.OPTION[3]: requested_dhcp6_name_servers = 1
DHCP6.OPTION[4]: dhcp6_name_servers = fdfd:dddd:dddd::1
DHCP6.OPTION[5]: rebind = 34560
DHCP6.OPTION[6]: max_life = 4294967295
DHCP6.OPTION[7]: preferred_life = 4294967295
DHCP6.OPTION[8]: requested_dhcp6_domain_search = 1
DHCP6.OPTION[9]: requested_dhcp6_client_id = 1
DHCP6.OPTION[10]: life_starts = 1521119940
DHCP6.OPTION[11]: ip6_address = fdfd:dddd:dddd::9fa
DHCP6.OPTION[12]: ip6_prefixlen = 64
DHCP6.OPTION[13]: dhcp6_domain_search = mydomain.com.
DHCP6.OPTION[14]: dhcp6_solmax_rt = 60
DHCP6.OPTION[15]: renew = 21600
DHCP6.OPTION[16]: dhcp6_server_id = 0:3:0:1:c0:4a:0:dd:54:1e
DHCP6.OPTION[17]: iaid = ed:75:5f:9a
DHCP6.OPTION[18]: starts = 1521119940
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1751797
Title:
dns resolution only works for domains in 'search'.
Status in network-manager package in Ubuntu:
New
Status in systemd package in Ubuntu:
Confirmed
Bug description:
After reboot, dns was broken.
This is a very simple Network Manager managed interface that has dhcp.
$ nmcli device show enp0s25 | pastebinit
http://paste.ubuntu.com/p/sMVTdrMBxJ/
I've attached systemd-resolve --status output.
In order to file the bug I just modified /etc/resolv.conf to put the
dns server in directly.
Other information, it seems like it just will only look for dns under
my search domains from the dhcp server:
$ systemd-resolve home.mosers.us
home.mosers.us: 23.28.108.176
-- Information acquired via protocol DNS in 1.5ms.
-- Data is authenticated: no
$ systemd-resolve google.com
google.com: resolve call failed: No appropriate name servers or networks for name found
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Feb 26 09:35:32 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-07-23 (949 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=1
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.vendor: Intel Corporation
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1751797/+subscriptions
More information about the foundations-bugs
mailing list