The Windows automatic DNS resolution is handled by an integration between DNS and ActiveDirectory, when the machine logs into it's ActiveDirectory Machine account, it gives AD it's IP address, and AD maps that to the DNS record assigned to the machine account. The Windows DNS provider then uses that information to answer DNS queries.
There are mechanisms to do dynamic DNS in Linux/Unix/Solaris too, and they work similarly. The machine logs into it's "account" in NIS or LDAP and the DNS provider uses that information to answer DNS queries.
Note, the Linux Samba client allows Linux to participate in a Windows network, but Windows has nothing that will allow it to participate in a Linux network. That's why getting the two systems to interface requires adding Linux to the Windows AD via Samba, and not the other way around.
==Joseph++
Alan Dayley wrote:
> Ah, the easy way! ;^)
>
> Part of this was a learning exercise for me. Windows computers on the
> network are reachable by name automatically, even as DHCP clients. So I
> wanted to learn a little about what it takes to have "automatic" name
> resolution for Linux computers on a Windows network.
>
> The answer appears to be that Linux computers must have a Samba client
> going for it to work that way. In this case, I did not care to go that
> path and complete my learning process. But, it did teach me something.
>
> Alan
>
> Shane Lofgren wrote:
>> Alan,
>> If this is to be a server then why not set a static IP address for the
>> machine? This would solve your problems and would seem to be a better
>> way to handle your issues. You could then add a new host file in your
>> windows DNS so that clients could resolve the host name.
>>
>> -Shane
>
>
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change you mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
(text/plain)