7 replies
by ---tk--- Accepted solution
by stealthwifi Accepted solution
From my understanding (and their may be exceptions to this) but in order to have a static IP you have to have a pool of address's to pull from.
If you have a router usually that router can handle DHCP for you, if not just throw it on the DNS server.
DNS is for your Domain Name
AD is for accounts and logging
WAN is for, well WAN
you can have all the statics you want but someone has to hold the key as to who goes with what, yah the address can be registered in DNS but not too sure how that would function without playing with it and no time today to fiddle.
Cheers,
by ---tk--- Accepted solution
by stealthwifi Accepted solution
by Member 25348569 Accepted solution
If everything has its own static address with everything assigned manually, DHCP won't ever be used.
Less simple answer - you ought to use DHCP, though. It's a much better way of assigning workstation addresses as you can then change gateway addresses and anything else at one central point.
by ---tk--- Accepted solution
by cg it Accepted solution
if you use static addresses, you don't need DHCP. A best practice would be if you have a small # of workstations and don't mind documenting IP addresses for each workstation [as well as their MAC addresses] that by all means use static addressing.
If you have a large # of workstations and don't want the hassle of tracking addresses used and need to run a DHCP relay agent for remote workstations, use DHCP. It's less administrative work.
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending