问题原文
原帖链接 · Stewart · CC BY-SA 4.0
How do I register DHCP linux client's hostnames in a windows server DNS?
I have a small-business mixed network with:
- DCHP Windows workstations (Example hostname:
win1)- About 10 machines
- Machines are on the domain, no special config.
- DHCP Linux (Debian stretch) workstations (Example hostname:
lin1)- About 20 machines
- Connected to domain with
sssdusingrealm join - Can use AD credentials on any machine
/etc/nsswitch.confcontainshosts: files dnswhich I think means that linux clients can import hostnames from the DNS
- DHCP/DNS server running Windows Server at a static IP
From any machine I can ping win1, but can't ping lin1 which tells us:
- all machines use the DNS fine (can ping
win1) - windows hostnames are automatically registered
- linux hostnames are not automatically registered
Rejected solutions:
hosts: We don't have static IPs so I'm not going to manually maintain a master copy of thehostsfile and distribute it whenever a new DHCP lease is issued.- Adding
Arecords to DNS: Again, I don't want to manually update records when new DHCP leases are issued. avahi: The windows clients can't see the linux ones.
Things I haven't tried:
likewise: I'd rather not abandonsssdand reconfigure all 20 machines from scratch like this. But iflw-register-dnswould solve the problem and wouldn't conflict withsssd, then that could be a solution. Still find it weird that clients would need to create a cron-job to modify the DNS, I optimally want to limit DNS write-access.winbind, also seems to replacesssdcompletely. I tried the linked suggestion, but saw no differences after restarting the client's networking service.nmbd. The workstations already usesmbclient, do they really need to become full-fledged samba servers too?net ads dns register -P. I'll need to get access to the DNS to enable insecure updates.
已采纳解答
原帖链接 · Stewart · CC BY-SA 4.0
So the final answer was not on the linux-client side at all, but on the DHCP configuration.
On "Windows Server 2016 Standard" I had to do the following to get this working.
- Open the "DHCP" desktop app
- Select the DNS tab
- Expand the node representing your domain
- Right click on "IPv4"
- Select "Properties" from the context menu
- Check "Enable DNS dynamic updates according to the settings below:"
- Select "Always dynamically update DNS records"
- Check "Dynamically update DNS records for DHCP clients that do not request updates"
The results were not immediate. Rebooting machines did not force the update. I made the change on Friday, and by Wednessday all Linux clients seemed to be listed in the DNS.
I was able to confirm the additions by viewing the "DNS Manager" on the same server.
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
