From: lcargill99@comcast.com   
      
   Char Jackson wrote:   
   > On Wed, 23 Mar 2016 12:32:02 -0500, Les Cargill    
   > wrote:   
   >   
   >>  (directions to a better asking-place always appreciated )   
      
   ^^^^^^^^^^   
   Also this, Char.   
      
   >>   
   >> 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 believe you'd call it a class assignment.   
   >   
      
   Heh. It's actually not. I'm just relatively clueless on the subject.   
      
   I work in the embedded space, and frequently, you'll have nodes   
   identified by nothing more than a static IP address. Hilarity ensues.   
      
   I'd like to find a lightweight, bolt-on solution for that. There's   
   often one workstation that is always on, and it is invariably a Windows   
   machine. If not, I can add a cheap ARM board to do this.   
      
   These networks will almost certainly not be on the larger Internet.   
   Totally airgapped. And "almost" really means "never" but ... things happen.   
      
   The sort of DHCP I am talking about is the sort you get included in   
   things like wireless routers. I understand enough to understand   
   that this may mean I have to use whatever is also in the DHCP server,   
   but I cannot say that categorically yet.   
      
   I see things like this:   
   https://sourceforge.net/projects/dhcp-dns-server/   
      
   >> 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.   
   >   
   > It sounds like the instructor intentionally left out key pieces of   
   > information in an attempt to get you to connect the dots, but he/she also   
   > included some random info to see if you would properly exclude it from your   
   > proposed solution.   
   >   
      
   Nope. The randomness is purely incidental or an artifact of pure ignorance.   
      
   --   
   Les Cargill   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)