Consider the subject of DNS servers.

• Why would a host contact a DNS server?
• If a local DNS server does not know the IP address for a host name, what will it do?
• What kind of organization must maintain one or more DNS servers? Why?
• How does your organization protect itself from DNS cache poisoning? Do you think this is sufficient? Why or why not?

 

Why would a host contact a DNS server? If a local DNS server does not know the IP address for a host name, what will it do?

Because DNS permits numerous hostnames to correlate to a single IP address, a host would query a DNS server. This may be utilized for virtual hosting, where multiple websites are provided from a single host. A single appellation can also resolve to numerous IP addresses, allowing load to be distributed over multiple servers. If the domain name and IP address are not found in its database, it queries alternative DNS server on the network. It may have to repeat this process several times. If it has to contact another DNS server, it caches the inquiry findings for a short period so that subsequent queries to the same domain name can be resolved promptly.

What kind of organization must maintain one or more DNS servers? Why?

Organizations that must maintain one or more DNS servers, such as the Google Company. This is mostly due to the importance of a local DNS for enterprise-level and bigger businesses. A DNS server protects IP addresses within a business network. They are accessible to the rest of the globe. It also contributes to faster connection speeds (Hock & Kortis, 2016). DNS's key job is to convert names into Ip Addresses that processer can comprehend. It also offers a list of mail servers for each domain name that accept emails. Each website address in DNS will appoint a group of name servers to be the trustworthy servers for its DNS records.

How does your organization protect itself from DNS cache poisoning? Do you think this is sufficient? Why or why not?

To assist my organization in preventing the muggings, cache poisoning tools are obtainable. DNSSEC is the most regularly cast-off cache intoxication protection technique. The internet engineering work force formed it, and it offers safe DNS data verification (Hock & Kortis, 2016). Yes, I believe it is sufficient since cache poisoning tools detect and handle any cache assault so that it does not reach and harm the organization's sites. This will keep the data safe and prevent data panic since you will be confident that it is protected.