samba - Feb 2019 - Active Directory one Client with multiple IP addresses

Is is possible to assign one name to a client, but have multiple ip
addresses (3 or more) say for a laptop that can be connected by wireless,
hardline on laptop, or hard-line on docking station where DHCP server
issues multiple ip addresses for each connection which could be used
simultaneously or individually?

and have nslookup yield the one of the working/connected ip address or say
first working if only 1 is connected?

On Thu, 21 Feb 2019 16:59:21 -0600
Brian Davis via samba <samba at lists.samba.org> wrote:
> Is is possible to assign one name to a client, but have multiple ip
> addresses (3 or more) say for a laptop that can be connected by
> wireless, hardline on laptop, or hard-line on docking station where
> DHCP server issues multiple ip addresses for each connection which
> could be used simultaneously or individually?
> 
> and have nslookup yield the one of the working/connected ip address
> or say first working if only 1 is connected?
What you are asking for is the reverse of CNAME's and I don't think you
can. This isn't an Active Directory restriction, it is a DNS
restriction.

Rowland

> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens 
> Brian Davis via samba
> Verzonden: donderdag 21 februari 2019 23:59
> Aan: samba at lists.samba.org
> Onderwerp: [Samba] Active Directory one Client with multiple 
> IP addresses
> 
> Is is possible to assign one name to a client, but have multiple ip
> addresses (3 or more) say for a laptop that can be connected by wireless,
> hardline on laptop, or hard-line on docking station 
> where DHCP server issues multiple ip addresses for each connection which
could be used simultaneously or individually?
Thats not how windows work. 
You have someing as priorities on the connections.
Above should be. 

Docking station > prio 1
NIC laptop > prio 2 
Wireless > prio 3

In win10 is bit more hidden, but here is how its done 
https://www.ghacks.net/2016/12/02/change-network-adapter-priorities-in-windows-10/

This is how it showed in win7
https://support.microsoft.com/en-ca/help/2526067 
> 
> and have nslookup yield the one of the working/connected ip 
> address or say first working if only 1 is connected?
> -- 
If the pc is domain join it "should" update is own dns record of done
by the DHCP server.
So normaly your not simultaneously connected. 

Greetz, 

Louis

>
> and have nslookup yield the one of the working/connected ip
> address or say first working if only 1 is connected?
> --
>> If the pc is domain join it "should" update is own dns record
of done by
the DHCP server.
So normaly your not simultaneously connected.

Do you mean DHCP server integration with SAMBA BIND9? I have read and
configured this on roll my own SAMBA servers that I can control with all
levers at my disposal with the security keys... commercial products with
SAMBA integration do not expose all levers.  This in fact should be part of
the GPL IMO.  Give users not only access to the source, but provide them
with unfettered access to control the software.

It is not clear to me how DHCP and AD integrate.  Currently I have clients
issued assigned fixed IPs by DHCP to get around this.