Product Collateral

eBook - DNS Fundamentals From a Technical Perspective

Learn all you need to know about email best practices, deliverability, and tools with email whitepapers and ebooks.

Issue link: https://hub.dyn.com/i/875330

Contents of this Issue

Navigation

Page 2 of 12

@dyn dyn.com page 3 Global DNS Let's begin by defining the actors on the stage. The DNS can really be broken down from a request perspective: There are authoritative servers, and there are things that talk to those authoritative servers. Often, the things that talk to the authoritative servers are doing it on behalf of someone else, which are "stubs." As we'll discuss later, there are a number of things you can be authoritative for. This can't possibly be repeated enough: users are our eyeballs on the edge of the internet accessing internet resources. Whenever we hit a URL like http://www.dyn.com/blog, our devices parse it out into multiple parts. Your browser first uses DNS to look up the target hostname's IP address (or the URL may have an IP-literal hostname that directly specifies an IP address, skipping DNS altogether). The URL has some distinct parts. The beginning is the scheme. In general terms, it says which protocol is in use (in this case, http). After the two slashes comes some network location information, which is almost always an Internet host expressed as a domain name that can be looked up in the DNS. In our example, this is www.dyn.com. There are other kinds of information that can be here, too, but a domain name is most common. After another slash comes the path (in this case, blog) which says where the desired resource is found on the host. To get to the blog, you must know how to find the host on the internet. This is where the DNS comes in, using a process called name resolution. Ebook | DNS Fundamentals

Articles in this issue

Links on this page

view archives of Product Collateral - eBook - DNS Fundamentals From a Technical Perspective