From: lcargill99@comcast.com   
      
   Robert Wessel wrote:   
   > On Wed, 23 Mar 2016 12:32:02 -0500, Les Cargill   
   >  wrote:   
   >   
   >> (directions to a better asking-place always appreciated )   
   >>   
   >> Suppose I had a pseudo random network of IP nodes. Say,   
   >> 50 out of a possible 2000 were on a given network at any given time.   
   >>   
   >> I want to have a DNS-like solution that uses the static hostname of   
   >> each node to populate the DNS tables.   
   >>   
   >> DHCP may or may not be run on the same server. Dunno yet.   
   >>   
   >> There may be DHCP for more than one Class C subnet. Dunno that yet,   
   >> either. I don't have a clear picture of how coupled DHCP and DNS   
   >> really are.   
   >>   
   >> Human beings would be personally responsible for setting the hostname   
   >> per node.   
   >>   
   >> Sadly, it's better if this runs on Windows, and not necessarily a   
   >> Windows server offering. It can simply be something that starts up on a   
   >> workstation.   
   >>   
   >> I would not be adverse to a small-footprint Linux VM on said Windows   
   >> machine to do this. Also maybe some small ARM Linux solution perhaps.   
   >>   
   >> What is this sort of thing called? I don't think the classic DNS BIND   
   >> service works for this, but I'd be eternally grateful to be proven   
   >> wrong - that's a "one book" solution.   
   >   
   >   
   > I'm not sure I fully understand the problem you're trying to solve.   
      
   You are excellent company. I'm not sure I do either.   
      
   In one sentence: I observe people using static IP addresses on a   
   semi-random network (think an engineering development/test network   
   without official IT sanction) and I wonder if there's some way to   
   organize this with a combination of DHCP and DNS in a lightweight and   
   inexpensive fashion.   
      
   I'd like there to be persistent state (hostname) on the nodes   
   that is used to influence the choice of DNS name, so that   
   pinging "TestTarget42" always gets the same node, but the IP address   
   can then be different.   
      
   > DHCP and DNS are usually fairly independent (there are some   
   > implementations where the two are integrated), but many DHCP servers   
   > can update a DNS server as they hand out IP address assignments.  The   
   > mechanism is usually called "Dynamic DNS" (although there can be other   
   > sources of dynamic DNS updates, not just DHCP).   
   >   
   > MS's DHCP server can update MS's DNS server (both on Windows Server)   
   > fairly painlessly (although that's optional).  See:   
   >   
      
   There can be no provision for an install of Windows Server. It may   
   be that a Windows workstation can have a VM of a Linux server if   
   that is the only way.   
      
   > https://technet.microsoft.com/en-us/library/cc771732.aspx   
   >   
   > You can also have Windows (DNS) client machines themselves issue the   
   > DNS update, for example, when IP address assignments or the computer   
   > name in the network configuration changes.  MS calls that "dynamic   
   > update", and the DNS server has to be configured to allow them:   
   >   
   > https://technet.microsoft.com/en-us/library/cc771255.aspx   
   >   
   > RFC2136 defines the standard Dynamic DNS protocol, but I'm not sure if   
   > that's what MS DNS supports (although I suspect that it does, at least   
   > in additional to the AD protocols it uses).   
   >   
      
   --   
   Les Cargill   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)