0
In essence, a DNS server is simply a database that links meaningful names (known as host names), such as http://www.microsoft.com, to a specific IP address, such as 192.168.124.1. So pretty much DNS or the Domain Name System are the guys who know everyone by their real name, so when you type in a 'nickname' (host name) eg: Yahoo.com in your address bar, they say 'oh you mean 209.191.122.70' and your computer now knows who you need to message. Also, on Windows you have something called a Windows Host File - your own little database similar to this so you don't always have to go through the DNS.
The DNS has a little more function than this but this is its main use. Also it sometimes is not as simple as contacting one DNS server and getting IP right off. You may type in mail.yahoo.com and the first DNS server contacted says 'oh well I only know yahoo.com' so he sends you to another DNS server, perhaps yahoos DNS server, this is where you find out IP for mail.yahoo.com. This is why sometimes you will go to a page and it may take a second, this is because it may have to go through multiple DNS servers before someone knows who you're talking about.
As for DHCP, according to TCP/IP every client (your computer, your phone, etc, anything on a network) has to have a unique IP address and subnet mask. At one point in time, people had to do this manually - and considering you cannot have duplicates, it would be very strenuous and a pain to do. That's where DHCP comes in. DHCP does all this automatically. Each client gets a unique IP address, subnet mask, and other IP information such as default gateways and the IP addresses of WINS (Windows internet Name Service) and DNS (Domain Name System) servers. DHCP makes certain that no clients have duplicate addresses, and this entire process is invisible to network administrators and network users.
Wiki User
∙ 12y ago
Add your answer:
Earn +20 pts
If you have not modified the default settings for dns on the dhcp client or server what client record or records will the dhcp server update in dns?
A. The PTR resource record.
What services are DHCP and DNS known as?
Infrastructure Services
What is the purpose of dnsmasq?
A dnsmaq is a lightweight and easy to configure the DNS forwarder and also the DHCP server. It is aimed to design and provide a DNS and also a DHCP to a small network.
What is the name of the control panel applet that is used to set dns and dhcp settings?
DNS and DHCP Management are both Administrative Tools. DNS Management is run from the DNS MMC snap in. This can be accessed by using the Run commend, and inputting: dnsmgmt.msc DHCP Management is run from the DHCP MMC snap in. This can be accessed by using the Run commend, and inputting: dhcpmgmt.msc These snap-ins must be installed on the system, or you will be unable to access them.
Describe the integration between DHCP and DNS.?
Traditionally, DNS and DHCP servers have been configured and managed one at a time. Similarly, changing authorization rights for a particular user on a group of devices has meant visiting each one and making configuration changes. DHCP integration with DNS allows the aggregation of these tasks across devices, enabling a company's network services to scale in step with the growth of network users, devices, and policies, while reducing administrative operations and costs.This integration provides practical operational efficiencies that lower total cost of ownership. Creating a DHCP network automatically creates an associated DNS zone, for example, reducing the number of tasks required of network administrators. And integration of DNS and DHCP in the same database instance provides unmatched consistency between service and management views of IP address-centric network services data.Windows Server 2003 DNS supports DHCP by means of the dynamic update of DNS zones. By integrating DHCP and DNS in a DNS deployment, you can provide your network resources with dynamic addressing information stored in DNS. To enable this integration, you can use the Windows Server 2003 DHCP service.The dynamic update standard, specified in RFC 2136: Dynamic Updates in the Domain Name System (DNS UPDATE), automatically updates DNS records. Both Windows Server 2003 and Windows 2000 support dynamic update, and both clients and DHCP servers can send dynamic updates when their IP addresses change.Dynamic update enables a DHCP server to register address (A) and pointer (PTR) resource records on behalf of a DHCP client by using DHCP Client FQDN option 81. Option 81 enables the DHCP client to provide its FQDN to the DHCP server. The DHCP client also provides instructions to the DHCP server describing how to process DNS dynamic updates on behalf of the DHCP client.The DHCP server can dynamically update DNS A and PTR records on behalf of DHCP clients that are not capable of sending option 81 to the DHCP server. You can also configure the DHCP server to discard client A and PTR records when the DHCP client lease is deleted. This reduces the time needed to manage these records manually and provides support for DHCP clients that cannot perform dynamic updates. In addition, dynamic update simplifies the setup of Active Directory by enabling domain controllers to dynamically register SRV resource records.If the DHCP server is configured to perform DNS dynamic updates, it performs one of the following actions:The DHCP server updates resource records at the request of the client. The client requests the DHCP server to update the DNS PTR record on behalf of the client, and the client registers A.The DHCP server updates DNS A and PTR records regardless of whether the client requests this action or not.By itself, dynamic update is not secure because any client can modify DNS records. To secure dynamic updates, you can use the secure dynamic update feature provided in Windows Server 2003. To delete outdated records, you can use the DNS server aging and scavenging feature.
Is a dhcp database a distributed database similar to a dns database?
no
Integration between DHCP and DNS?
Traditionally, DNS and DHCP servers have been configured and managed one at a time. Similarly, changing authorization rights for a particular user on a group of devices has meant visiting each one and making configuration changes. DHCP integration with DNS allows the aggregation of these tasks across devices, enabling a company's network services to scale in step with the growth of network users, devices, and policies, while reducing administrative operations and costs.This integration provides practical operational efficiencies that lower total cost of ownership. Creating a DHCP network automatically creates an associated DNS zone, for example, reducing the number of tasks required of network administrators. And integration of DNS and DHCP in the same database instance provides unmatched consistency between service and management views of IP address-centric network services data.Windows Server 2003 DNS supports DHCP by means of the dynamic update of DNS zones. By integrating DHCP and DNS in a DNS deployment, you can provide your network resources with dynamic addressing information stored in DNS. To enable this integration, you can use the Windows Server 2003 DHCP service.The dynamic update standard, specified in RFC 2136: Dynamic Updates in the Domain Name System (DNS UPDATE), automatically updates DNS records. Both Windows Server 2003 and Windows 2000 support dynamic update, and both clients and DHCP servers can send dynamic updates when their IP addresses change.Dynamic update enables a DHCP server to register address (A) and pointer (PTR) resource records on behalf of a DHCP client by using DHCP Client FQDN option 81. Option 81 enables the DHCP client to provide its FQDN to the DHCP server. The DHCP client also provides instructions to the DHCP server describing how to process DNS dynamic updates on behalf of the DHCP client.The DHCP server can dynamically update DNS A and PTR records on behalf of DHCP clients that are not capable of sending option 81 to the DHCP server. You can also configure the DHCP server to discard client A and PTR records when the DHCP client lease is deleted. This reduces the time needed to manage these records manually and provides support for DHCP clients that cannot perform dynamic updates. In addition, dynamic update simplifies the setup of Active Directory by enabling domain controllers to dynamically register SRV resource records.If the DHCP server is configured to perform DNS dynamic updates, it performs one of the following actions:The DHCP server updates resource records at the request of the client. The client requests the DHCP server to update the DNS PTR record on behalf of the client, and the client registers A.The DHCP server updates DNS A and PTR records regardless of whether the client requests this action or not.By itself, dynamic update is not secure because any client can modify DNS records. To secure dynamic updates, you can use the secure dynamic update feature provided in Windows Server 2003. To delete outdated records, you can use the DNS server aging and scavenging feature.
What is network aware?
They are network services that are always on listening on the network for requests. Example: DNS, DHCP ..... DNS resolves Domain Names to IP addresses. DHCP assigns dynamic IP addresses.
What roles do DHCP and DNS play?
DHCP is a host configuration protocol and is dynamic . DHCP is short for Dynamic host configuration protocol and is backward compatible with earlier protocols like BOOTp . DNS is domain name system that maps name to an IP address.
What is the best operating system for a DNS or DHCP server?
FreeBSD of course
When configuring DHCP to use the local DNS why would you also include an ISP assigned DNS?
It is useful only in small environments. When you have only one DNS in organization and users mainly use internet (external DNS names) then you can configure in DHCP that users will obtain also external DNS server address as secon one. It will be used only when first DNS service won't be accessible. P.S.
What do active directory clients rely on in DNS to locateresources in active directory?
DHCP
