DHCP is Dynamic Host Configuration Protocal. It assings IP addresses to the needed computers in a network dynamically.
DNS is Domain Naming System(Service) It is system for naming computers and network services that is organized into a hierarchy of domains. DNS naming is used in TCP/IP networks, such as internet, to locate computers and services through user friendly names.
What is the difference between a preferred DNS server and an altenate DNS server?Read more: http://wiki.answers.com/What_is_the_difference_between_a_preferred_DNS_server_and_an_altenate_DNS_server#ixzz2LRd3ICed
A. The PTR resource record.
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.
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.
FreeBSD of course
It's up to you. People usually have different ip addresses for gateways and DNS/DHCP servers. It's because a separate server is used for gateway.
RARP help the PC to find its MAC address in the same network from the RARP Server.RARP Serveronly providethe IP adress to the PC by remembering its MAC.DHCP works on the same way but DHCP Server provide the PC its IP address, Subnetmask, Default Gateway and DNS Server etc...So the big difference is DHCP provide more information than your RARP Server.
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.
Without Active Directory the DHCP server cannot be authorized, and could therefore be considered a "rogue". What A.D do for a DHCP Server that it authorised to DHCP server to give an Ip add. to clients and authorised for update the DNS PTR records. and when we won't authorised DHCP with Active Directory it won't be update the the PTR records and won't be update the IP add. in DNS records.
yes it is and recommended also
Secondary DNS gets its records from the Primary DNS Server. The secondary DNS is essentially there in case the primary DNS doesn't respond.
Check your network connections. That is usually a main problem of not communicating with either DNS or DHCP on a LAN.