Hallo, thanks but this doesn t work here allthough most tips and hints are using this parameter. Any idea how to debug ?

Thanks Ralf

Von meinem iPad gesendet

Am 29.01.2019 um 18:08 schrieb Liam O'Toole liam.p.otoole@gmail.com:

...

On 2019-01-29, Ralf Prengel ralf.prengel@rprengel.de wrote: Hallo,

I try to configure my dhcp-client to send the hostname to a microsoft dns/dhcp server. It doesn t work. Nothing happens. A debian system works fine so it seems that the microsoft-side isn t the problem this time. I found some hints but nothing works.

Thansk for hints.

Ralf

I have used the following approach successfully in the past:

https://possiblelossofprecision.net/?p=1377

More recently, on systems running Network Manager, I find that it's no longer necessary.

--

Liam

---

CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos

Zitat von Liam O'Toole liam.p.otoole@gmail.com:

On 2019-01-29, Ralf Prengel ralf.prengel@rprengel.de wrote:

...

Hallo, thanks but this doesn t work here allthough most tips and hints are using this parameter. Any idea how to debug ?

Thanks Ralf

Von meinem iPad gesendet

Please don't top-post.

Sorry, my fault.

Try running 'dhclient -H <hostname> <interface>' from the commanad line. Make sure that the network interface is down first.

Here the logfile. Thanks for your help

Ralf

Jan 30 06:03:17 000c2967082a NetworkManager[8956]: <info> [1548824597.4087] device (ens33): state change: activated -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed') Jan 30 06:03:17 000c2967082a NetworkManager[8956]: <info> [1548824597.4097] dhcp4 (ens33): canceled DHCP transaction, DHCP client pid 9102 Jan 30 06:03:17 000c2967082a NetworkManager[8956]: <info> [1548824597.4097] dhcp4 (ens33): state changed bound -> done Jan 30 06:03:17 000c2967082a dnsmasq[13518]: no servers found in /etc/resolv.conf, will retry Jan 30 06:03:17 000c2967082a NetworkManager[8956]: <info> [1548824597.4152] manager: NetworkManager state is now CONNECTED_LOCAL Jan 30 06:03:17 000c2967082a dbus[8916]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' Jan 30 06:03:17 000c2967082a systemd: Starting Network Manager Script Dispatcher Service... Jan 30 06:03:17 000c2967082a dbus[8916]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Jan 30 06:03:17 000c2967082a nm-dispatcher: req:1 'down' [ens33]: new request (4 scripts) Jan 30 06:03:17 000c2967082a systemd: Started Network Manager Script Dispatcher Service. Jan 30 06:03:17 000c2967082a nm-dispatcher: req:1 'down' [ens33]: start running ordered scripts... Jan 30 06:03:17 000c2967082a nm-dispatcher: req:2 'connectivity-change': new request (4 scripts) Jan 30 06:03:17 000c2967082a chronyd[8955]: Can't synchronise: no selectable sources Jan 30 06:03:17 000c2967082a nm-dispatcher: req:2 'connectivity-change': start running ordered scripts... Jan 30 06:03:18 000c2967082a journal: INFO: Starting agent for DB55B6D85FD79FFBB7B4 Jan 30 06:03:23 000c2967082a journal: INFO: Starting agent for DB55B6D85FD79FFBB7B4 Jan 30 06:03:28 000c2967082a journal: INFO: Starting agent for DB55B6D85FD79FFBB7B4 Jan 30 06:03:34 000c2967082a journal: INFO: Starting agent for DB55B6D85FD79FFBB7B4 Jan 30 06:03:39 000c2967082a journal: INFO: Starting agent for DB55B6D85FD79FFBB7B4 Jan 30 06:03:41 000c2967082a kernel: IPv6: ADDRCONF(NETDEV_UP): ens33: link is not ready Jan 30 06:03:41 000c2967082a kernel: e1000: ens33 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None Jan 30 06:03:41 000c2967082a kernel: IPv6: ADDRCONF(NETDEV_CHANGE): ens33: link becomes ready Jan 30 06:03:41 000c2967082a NetworkManager[8956]: <info> [1548824621.3565] device (ens33): carrier: link connected Jan 30 06:03:41 000c2967082a NetworkManager[8956]: <info> [1548824621.3566] device (ens33): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed') Jan 30 06:03:41 000c2967082a NetworkManager[8956]: <info> [1548824621.3602] policy: auto-activating connection 'ens33' (c83605ea-2baf-4013-a40c-9a067208e8fa) Jan 30 06:03:41 000c2967082a NetworkManager[8956]: <info> [1548824621.3605] device (ens33): Activation: starting connection 'ens33' (c83605ea-2baf-4013-a40c-9a067208e8fa) Jan 30 06:03:41 000c2967082a NetworkManager[8956]: <info> [1548824621.3606] device (ens33): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Jan 30 06:03:41 000c2967082a NetworkManager[8956]: <info> [1548824621.3609] manager: NetworkManager state is now CONNECTING Jan 30 06:03:41 000c2967082a NetworkManager[8956]: <info> [1548824621.3610] device (ens33): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Jan 30 06:03:41 000c2967082a NetworkManager[8956]: <info> [1548824621.3639] device (ens33): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') Jan 30 06:03:41 000c2967082a NetworkManager[8956]: <info> [1548824621.3641] dhcp4 (ens33): activation: beginning transaction (timeout in 45 seconds) Jan 30 06:03:41 000c2967082a dhclient[57707]: DHCPDISCOVER on ens33 to 255.255.255.255 port 67 interval 4 (xid=0x13cb0bcd) Jan 30 06:03:41 000c2967082a NetworkManager[8956]: <info> [1548824621.3700] dhcp4 (ens33): dhclient started with pid 57726 Jan 30 06:03:41 000c2967082a dhclient[57707]: DHCPREQUEST on ens33 to 255.255.255.255 port 67 (xid=0x13cb0bcd) Jan 30 06:03:41 000c2967082a dhclient[57707]: DHCPOFFER from 192.168.xxx.40 Jan 30 06:03:41 000c2967082a dhclient[57707]: DHCPACK from 192.168.xxx.40 (xid=0x13cb0bcd) Jan 30 06:03:41 000c2967082a dhclient[57726]: DHCPREQUEST on ens33 to 255.255.255.255 port 67 (xid=0x1bc5be42) Jan 30 06:03:41 000c2967082a dhclient[57726]: DHCPACK from 192.168.xxx.40 (xid=0x1bc5be42) Jan 30 06:03:41 000c2967082a NetworkManager[8956]: <info> [1548824621.4041] dhcp4 (ens33): address 192.168.xxx.145 Jan 30 06:03:41 000c2967082a NetworkManager[8956]: <info> [1548824621.4041] dhcp4 (ens33): plen 21 (255.255.248.0) Jan 30 06:03:41 000c2967082a NetworkManager[8956]: <info> [1548824621.4041] dhcp4 (ens33): gateway 192.168.xxx.232 Jan 30 06:03:41 000c2967082a NetworkManager[8956]: <info> [1548824621.4041] dhcp4 (ens33): lease time 172800 Jan 30 06:03:41 000c2967082a NetworkManager[8956]: <info> [1548824621.4041] dhcp4 (ens33): nameserver '192.168.xxx.7' Jan 30 06:03:41 000c2967082a NetworkManager[8956]: <info> [1548824621.4041] dhcp4 (ens33): nameserver '192.168.xxx.30' Jan 30 06:03:41 000c2967082a NetworkManager[8956]: <info> [1548824621.4041] dhcp4 (ens33): nameserver '192.168.xxx.40' Jan 30 06:03:41 000c2967082a NetworkManager[8956]: <info> [1548824621.4041] dhcp4 (ens33): nameserver '192.168.xxx.79' Jan 30 06:03:41 000c2967082a NetworkManager[8956]: <info> [1548824621.4041] dhcp4 (ens33): domain name 'firma.de' Jan 30 06:03:41 000c2967082a NetworkManager[8956]: <info> [1548824621.4041] dhcp4 (ens33): state changed unknown -> bound Jan 30 06:03:41 000c2967082a avahi-daemon[8935]: Joining mDNS multicast group on interface ens33.IPv4 with address 192.168.xxx.145. Jan 30 06:03:41 000c2967082a avahi-daemon[8935]: New relevant interface ens33.IPv4 for mDNS. Jan 30 06:03:41 000c2967082a avahi-daemon[8935]: Registering new address record for 192.168.xxx.145 on ens33.IPv4. Jan 30 06:03:41 000c2967082a NetworkManager[8956]: <info> [1548824621.4123] device (ens33): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Jan 30 06:03:41 000c2967082a NetworkManager[8956]: <info> [1548824621.4127] device (ens33): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Jan 30 06:03:41 000c2967082a NetworkManager[8956]: <info> [1548824621.4129] device (ens33): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Jan 30 06:03:41 000c2967082a NetworkManager[8956]: <info> [1548824621.4131] manager: NetworkManager state is now CONNECTED_LOCAL Jan 30 06:03:41 000c2967082a NetworkManager[8956]: <info> [1548824621.4171] manager: NetworkManager state is now CONNECTED_SITE Jan 30 06:03:41 000c2967082a NetworkManager[8956]: <info> [1548824621.4172] policy: set 'ens33' (ens33) as default for IPv4 routing and DNS Jan 30 06:03:41 000c2967082a dhclient[57726]: bound to 192.168.xxx.145 -- renewal in 75828 seconds. Jan 30 06:03:41 000c2967082a NetworkManager[8956]: <info> [1548824621.4215] device (ens33): Activation: successful, device activated. Jan 30 06:03:41 000c2967082a NetworkManager[8956]: <info> [1548824621.4219] manager: NetworkManager state is now CONNECTED_GLOBAL Jan 30 06:03:41 000c2967082a dnsmasq[13518]: reading /etc/resolv.conf Jan 30 06:03:41 000c2967082a dnsmasq[13518]: using nameserver 192.168.xxx.7#53 Jan 30 06:03:41 000c2967082a dnsmasq[13518]: using nameserver 192.168.xxx.30#53 Jan 30 06:03:41 000c2967082a dnsmasq[13518]: using nameserver 192.168.xxx.40#53 Jan 30 06:03:41 000c2967082a dnsmasq[13518]: using nameserver 192.168.xxx.79#53

Zitat von Steven Tardy sjt5atra@gmail.com:

Try to check the “dynamic update” checkbox in the AD DHCP confit like the 5th image on this blog:

https://blog.royso.me/integrate-linux-desktop-to-microsoft-active-directory-...

The dns-admin show me tha these options are configured.

Ralf

Am 30.01.2019 um 13:03 schrieb Liam O'Toole liam.p.otoole@gmail.com:

I see you're using network-manager. Does the file /var/lib/NetworkManager/dhclient-<interface>.conf contain a line beginning with 'send host-name'?

Hallo, problem is solved now. Thanks for your help.

Ralf