What Is Dns

What are DNS and DHCP, why is it needed and what overhead can it create for an IT Administer. These are the questions I set out looking for to help provide a better understanding of these roles in a Server. By understanding them better it can help to create a knowledge base to be successful in IT. First we will looking in DNS this is short for Domain Name System, in a nutshell it provides a meaningful host name with network address (Windows server 2008, 2008). As we have learned all computers use TCP/ IP to communicate and that each computer is given a unique IP address (Microsoft Windows server 2008 r2, 2010). In this way every computer has a different IP address so there needed to be away for use to remember them it would be heard for everyone to remember each IP address so with DNS we can create names for them to help out like www.Microsoft.com. This is done by using fully qualified domain names or FQDN; this is a way to map a host name to an IP address (Windows server 2008, 2008). The DHCP is short for Dynamic Host Configuration Protocol, this for the conveniently assigning network addresses and other network configuration parameters to a system upon request, usually when it is first bootstrapped or attached to the network (Windows server 2008, 2008). In other words when you start up a computer you need an IP address this will assign you one that is not used on the network that is different from the other so that you and use the network. It will also assign you a default gateway, DNS and ever a subnet mask if you are in need of one. For an IT administer these thing can help you save time. For one thing if you are working with over 10 computers it’s a good idea to use DHCP because if you are using Static IP Addresses you needed to go to each computer if there is a change in IP addresses also you need to keep track of what IP address you have used. This can take up you time but in using DHCP it keeps track of it for you and can make changes