Dhcp not updating dns records
Mockapetris instead created the Domain Name System.
In 1984, four UC Berkeley students, Douglas Terry, Mark Painter, David Riggle, and Songnian Zhou, wrote the first Unix name server implementation for the Berkeley Internet Name Domain, commonly referred to as BIND.
Using a simpler, more memorable name in place of a host's numerical address dates back to the ARPANET era.
The Stanford Research Institute (now SRI International) maintained a text file named HOSTS.
This process of using the DNS to assign proximal servers to users is key to providing faster and more reliable responses on the Internet and is widely used by most major Internet services.
Each subdomain is a zone of administrative autonomy delegated to a manager.
A DNS name server is a server that stores the DNS records for a domain; a DNS name server responds with answers to queries against its database.
The most common types of records stored in the DNS database are for Start of Authority (SOA), IP addresses (A and AAAA), SMTP mail exchangers (MX), name servers (NS), pointers for reverse DNS lookups (PTR), and domain name aliases (CNAME).
Postel directed the task of forging a compromise between five competing proposals of solutions to Paul Mockapetris.
For zones operated by a registry, administrative information is often complemented by the registry's RDAP and WHOIS services.
That data can be used to gain insight on, and track responsibility for, a given host on the Internet.
Although not intended to be a general purpose database, DNS can store records for other types of data for either automatic lookups, such as DNSSEC records, or for human queries such as responsible person (RP) records.
As a general purpose database, the DNS has also been used in combating unsolicited email (spam) by storing a real-time blackhole list.