looking to implement host name pools

[ggnfs000]

i am looking to deploy a large number of possible server but also consists of consumer grade OS like WIN10, WIN7-s.
Now I am contemplating to join them to Active Directory for easier management.
For controlling the host use RDP.
Now IP is real ping in the a** as DHCP lease expires and host get different IP. I also have at home about 20 different devices all get IP, it is much easier to communcaite with them using NETBEUI.
Now for this project, I might be deploying few hundred possible and assign host name to each of them is pain. So I thought, is there a host name pool implemented somewhere? it wil consist of prefix (static) + suffix (some sort of incrementing number) and each time server joins it will randomly get from the pool.

cisco ucs does similar thing in terms of mac-addr pool, ip pool and wwn pool etc. but not hostname pool. Even if it does so, I wont get it it is too costly for home project.

[deanwebb]

You should be able to reserve an address for each device, even if it is in the DHCP pool. Check on that.

[dlots]

If your DHCP server is a Microsoft box over at dhimes.com I have a spreadsheet, you give it the IP you want it to have, and the device's mac address and it spits out the windows command put put in the reservations.

Saved me a lot of time when I was doing MS DHCP work.

[wintermute000]

It always p1ssed me off how you have to work out the client identifier. I remember in some scenarios it was easier to run a debug watch the request come in then you know the ID lol.
That's the only real obstacle, you can then merrily reserve addys on any not-retarded DHCP server, even the built in IOS one on a router.

[deanwebb]

It always p1ssed me off how you have to work out the client identifier. I remember in some scenarios it was easier to run a debug watch the request come in then you know the ID lol.
That's the only real obstacle, you can then merrily reserve addys on any not-retarded DHCP server, even the built in IOS one on a router.

True... MSFT DHCP makes me go



MSFT DHCP is the Jerry of the DHCP world. But at least it can be used in production. Cisco even warns to not use Cisco DHCP in production, unless you like

[ggnfs000]

going by IP is marginally OK, if you can remember the IP for each host (assuming got a decent memory) but real problem begins after the host is down for a while and gets different IP. Perhaps immediate near-term solution might be just infinitely extend the lease time and hoping that it will not exhaust the subnet space.

Looks like the matter of choosing between:
- struggling to identify new IP for specific host
- or identify from the pre-assigned dhcp ip pool which IP is no longer necessary and manually erase from pool.

However with large enough pool may be second one is better.

[deanwebb]

My big question is why do you need the devices to have a static IP address? Or to have the same IP address over time?

If you're running Windows DHCP along with Windows DNS, you'll be able to reach devices by FQDN no matter what the IP addresses are.

And if you have a stable environment, the devices should renew the address they have, even if it's not a reserved address.

[dlots]

A lot of the devices we used in my 1st networking job required that kinda thing.
Printers
Cash registers
HVAC
Machines that needed ACL holes poked in for them
VIPs who demanded high priority internet access (who then said we didn't need upgraded internet access, after all internet worked just fine for them)
Fire alarms
etc

[ggnfs000]

My big question is why do you need the devices to have a static IP address? Or to have the same IP address over time?

If you're running Windows DHCP along with Windows DNS, you'll be able to reach devices by FQDN no matter what the IP addresses are.

And if you have a stable environment, the devices should renew the address they have, even if it's not a reserved address.

static IP adds extra job, gotta keep track of which IP is being used by which system. IMHO, it is too much, I think it is far better to let the DHCP to the job and keep the lease to indefinite rather than static. But it is personal preference I think.

At least in my home system, the critical device that  I need access at any time quick and fast, I assigned static IP to make sure it is not released. Also dhcp I left the default at 8 days of lease time. I am considering it to indefinite or may be several of month lease time and eliminate static IP addresses.

[deanwebb]

I really don't think you need to do anything else. The minor devices will not need to worry at all about what IP they have.

Also moving to proper part of the forum.

[dlots]

static IP adds extra job, gotta keep track of which IP is being used by which system. IMHO, it is too much, I think it is far better to let the DHCP to the job and keep the lease to indefinite rather than static. But it is personal preference I think.

At least in my home system, the critical device that  I need access at any time quick and fast, I assigned static IP to make sure it is not released. Also dhcp I left the default at 8 days of lease time. I am considering it to indefinite or may be several of month lease time and eliminate static IP addresses.

Yep
Do DHCP reservations, not static IPs.

[ggnfs000]

static IP adds extra job, gotta keep track of which IP is being used by which system. IMHO, it is too much, I think it is far better to let the DHCP to the job and keep the lease to indefinite rather than static. But it is personal preference I think.

At least in my home system, the critical device that  I need access at any time quick and fast, I assigned static IP to make sure it is not released. Also dhcp I left the default at 8 days of lease time. I am considering it to indefinite or may be several of month lease time and eliminate static IP addresses.

Yep
Do DHCP reservations, not static IPs.

dhcp reservation has to deal with mac-addr, wanna be hands-free or almost.
I set the dhcp lease-time to 3 month on home router that is hosting dhcp server, I think i can live in peace with that configuration.