Hi John,

On 11.01.19 10:53, john doe wrote:
On 1/11/2019 9:49 AM, MIchael Schleicher (smicha) wrote:

thanks for your reply.

On 10.01.19 22:25, wkitt...@gmail.com wrote:
On 1/10/19 3:26 PM, Michael Schleicher wrote:
As I said, for Linux VM's, I can set a uniq Client-ID that helps, but on
Windows you can not set define a Client-ID (as far as I know).

isn't this the machine name? when i was supporting winwhatever, the
install generated a machine name... that is the name i saw used in
DHCP requests... it is the name that was added to the DNS so queries
on it would return its current IP...

I have just checked on my environment what's in the dnsmasq.leases file:

1547246444 00:50:56:85:23:ea win-vm 01:00:50:56:85:23:ea
1547276503 00:50:56:85:f1:86 linux-vm 01:00:50:56:85:f1:86

As you see the Client-ID (5th field) is the MAC + "01:" as prefix.

You previously said that the hostname is always the same, as ilustrated
by the above they are not (win-vm vs linux-vm)?

That are 2 different systems. (1 Windows and 1 Linux VM). It's just a example


Dnsmasq-discuss mailing list

Reply via email to