This is more of a subjective questions, but...

I want comment out some the DHCP leases the router is giving out. Most of the time this is done in conjunction with assigning a specific IP address outside of the pool/scope. I am not as concerned with what the IP address is - simply who/what the host is.

Do you typically move these outside your pool/scope or leave them in it? I don't think it really matters as the router will not hand out that in-scope address for that host if it sees a reservation ... right?

Thanks in advance.

Any ideas?

Its not clear what you want.

I convert all DHCP for my small net to static IP, then add DNS names for them. This way all units get the same IP all time and with a understandable name.

My SOP is to move static leases out of pool range, which then effectively acts as address pool for (yet) unknown devices. Additional benefit is that I can tell if device is known to me from its IP address.

On most sites I run internal DNS (on separate small server) ... so when I set static DHCP lease, I also add (by hand) that device to DNS system.

Thanks guys - that was what I was looking for.

On most sites I run internal DNS (on separate small server) ... so when I set static DHCP lease, I also add (by hand) that device to DNS system.

This you can do on the MT Router itself. No need for an external server.

On most sites I run internal DNS (on separate small server) ... so when I set static DHCP lease, I also add (by hand) that device to DNS system.

This you can do on the MT Router itself. No need for an external server.

I know ... and that's not the point.

I'm the same as all the rest here. All known DHCP clients are given a DHCP reservation outside of the IP Pool. Most of the pools are only 10 IPs (and in reality, I could normally get away with one or two).