[Samba] A records of computers in domain take long to update

Mikel Pérez io at mikelpr.com
Sun Aug 18 19:08:19 UTC 2024


Windows clients
Sometimes it's not long and happens eventually but sometimes it's been
hours since the computer was booted and the DNS records still point to
their previous IP address and I have to go look for their current IP
address on the router's status page to connect via RDP to them
Hmph. So I'm at Microsoft's mercy here? Is there not a way to run a DHCP
server on the samba DC and have that instantly update DNS records instead
of waiting for the client computers to do it when they want?

On Sat, 17 Aug 2024, 01:06 Rowland Penny via samba, <samba at lists.samba.org>
wrote:

> On Fri, 16 Aug 2024 15:57:32 -0600
> Mikel Pérez via samba <samba at lists.samba.org> wrote:
>
> > hey there :) don't know why but it takes a while before I can reach
> > computers in my AD network by their hostnames. I often have to end up
> > looking for them at the router's status page (OpenWrt)
> > is it because I'm letting the router be the DHCP server instead of my
> > samba AD DC? if that's the case, how should I go on about setting the
> > DC to be the DHCP server and how do I link it to samba? if it isn't,
> > then what should I do so that the computers hostnames point to their
> > IP addresses as soon as they're assigned to them by the router?
> >
> > thanks!!
>
> Are we talking Windows or Linux clients here ?
> If Linux, then I am surprised that their DNS records are getting
> updated in AD at all, as far as I am aware, there isn't any mechanism
> to do this.
> Windows clients are different, they can and do update their own AD DNS
> records, whilst this might not be instantaneous, it isn't really long
> either.
>
> Rowland
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
>


More information about the samba mailing list