- [Instructor] There are two roles that
are commonly associated with the management
of TCP/IP within a network.
DHCP configures IP information on the various hosts
as they start up, and DNS maintains a directory
of where to find everything.
Now when I say everything, I do mean everything.
DNS helps you find servers, printers, and websites yes.
But it also tracks every object in active directory
that's everything from group policies,
to the email address of a user.
All of that information is tracked down
through the lookup service provided by DNS.
If you've added the DNS role,
while installing Active Directory Domain Services
it will configure itself while the server
is being promoted to a domain controller
and because the users might need to be able to look up
resources on the internet generally.
It has something called root hints,
where your server is able to look
to the outside world to get information
about other websites, so that you can provide
that name resolution to users
and applications inside your domain.
But just because there's an automatic configuration
doesn't mean that it's the right thing for everyone.
For example, this test lab environment that I'm using
for these demonstrations has a firewall.
That blocks DNS lookups to any server other than
two specific DNS servers in the data center here.
This is a way to protect our users
and applications from being sent
to some erroneous DNS server
that is doing something malicious.
In that case, we can configure forwarders.
This is a server that has been installed
to be a domain controller,
and the DNS role has been installed as well
if I go to the tools menu,
I can go ahead and open up the DNS tool
and from here we can look at the properties of our server.
Inside ForwardLookupZones we can find the domains
that we are able to research and locate information.
For example, landonhotel.com
and another active directory integrated zone.
But if I wanted to change how the server works
as a whole, I can right click on the server
and view its properties, and here you can see
the root hints that were mentioned before.
Where to find servers on the internet,
to help look up generally, and we can find forwarders.
Here I can add the IP addresses of servers
that will look up things on the internet.
This is also useful if this domain is buried
down in the organization and you need to look
to the top of the organization for your lookup information.
In edition to using DNS, having a DHCP server
that's also integrated with active directory
will allow you to hand out configuration information
to requesting hosts, and report back to the DNS server
so that the host can be registered in this list.
This helps maintain the most complete
and the most current list of hosts
and their addresses throughout the network.
There's one other feature that I want to point out to you
that's not new to Windows Server 2019.
But it is severely underutilized.
Once you have an active directory environment
with DNS and DHCP, you now have the task
of keeping track of how these roles are being used.
Some people use spreadsheets to maintain lists
of IP address ranges, DHCP exceptions
and statically assigned or reserved IP addresses
and these spreadsheets may seem to work
in a small environment, but they get outdated very quickly.
As soon as somebody has to change out a printer,
let's say the business center printer
has died and so we've retired that machine
and add a new printer, but we're in a hurry
to get things up and going so we just add it
to the DHCP server and we don't update the spreadsheet.
Later on somebody comes in to do inventory,
and there's different information in different locations.
This can get out of hand really quickly,
and you begin to question whether any of the other
information in the spreadsheet is accurate as well.
There is a feature named IP Address Management Server
or IPAM Server, this feature gives you a dashboard
that you can use to track everything
from an inventory of IP addresses in a scope
to the details of a DNS zone.
You may have noticed that the wallpaper
is a different shade here, I moved from blue to green.
This is a DHCP server that's in the same
active directory domain,
and this is where I'm going to install the feature.
It can be added to any Windows 2016 or 2019 server
so long as the machine is not a domain controller
and this feature is added in pretty much the same process
as a role, I'm going to start by Add roles and features.
This is a server that I haven't yet checked the box
to skip this welcome page.
I want to install a role or feature,
I want to install it on this machine
and this time what we're looking for is not a role.
It's not in the first list so I need to move on,
to the second list where you'll find
IP Address Management IPAM Server, when you check the box,
you'll see that not only do you get administration tools
but there are several prerequisites
that are being added as well.
The .NET Framework and ASP.NET versions 4.7 components
are required in addition to access to the DNS server tools.
As a general rule I accept all of the prerequisites
and tools that are offered to me when I install
a role or a feature, but I do take time
to scroll through them and see what they are.
This helps give me some insight into what this feature
is going to need from this server.
So I'm going to go ahead and add that.
Move on to the next screen,
which will confirm what I've asked it to do,
and then install the role.
The dashboard that IPAM offers us is similar
to that involved in many different
software defined network packages.
Including Windows System Center, and third party products.
If you're using one of those products already, great.
If not, know that Windows Server 2019,
and 2016 have you covered with features
that are already included in the server product
that you bought and are deploying in your network.