DNS Concepts: Difference between revisions
| (29 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
=External= | |||
* https://www.digitalocean.com/community/tutorials/an-introduction-to-dns-terminology-components-and-concepts | |||
=Internal= | =Internal= | ||
* [[bind#Subjects|bind]] | * [[bind#Subjects|bind]] | ||
* [[Amazon Route53 Concepts]] | |||
=Zone File= | =DNS Name= | ||
==DNS Host== | |||
==DNS Domain== | |||
==<span id='FQDN'></span>Fully Qualified Domain Name (FQDN)== | |||
=Zone= | |||
A '''zone''', also referred to as '''hosted zone''', is a container for [[#Zone_Records|zone records]], which include information about how you want to route traffic for a domain and all of its subdomains. A hosted zone has the same name as the corresponding domain. | |||
==Zone File== | |||
A zone file organizes the [[#Zone_Records|zone records]] for domain names and sub-domains in a DNS server. Every domain name and sub-domain has its own zone file, and each zone file contains [[#Zone_Records|zone records]]. | A zone file organizes the [[#Zone_Records|zone records]] for domain names and sub-domains in a DNS server. Every domain name and sub-domain has its own zone file, and each zone file contains [[#Zone_Records|zone records]]. | ||
| Line 9: | Line 22: | ||
=Domains and Sub-Domains= | =Domains and Sub-Domains= | ||
Sub-domains are extensions of a domain name. For example, for the "novaordis.com" domain name, "internal.novaordis.com" is a sub-domain. Although domain names might have sub-domains, the [[#Zone_File|zone files]] for sub-domains are not considered sub-zones. All zone files are separate entities and do not have a hierarchical structure. | Sub-domains are extensions of a domain name. For example, for the "novaordis.com" domain name, "internal.novaordis.com" is a sub-domain. Although domain names might have sub-domains, the [[#Zone_File|zone files]] for sub-domains are not considered sub-zones. All zone files are separate entities and do not have a hierarchical structure. With godaddy.com you one can add up to 90 sub-domains per domain name. Multiple levels of sub-domains can also be added. Each sub-domain can be up to 25 characters long. Sub-domains that point to IP addresses can be simply added as A records. | ||
With godaddy.com you one can add up to 90 sub-domains per domain name. Multiple levels of sub-domains can also be added. Each sub-domain can be up to 25 characters long. | |||
Sub-domains that point to IP addresses can be simply added as A records. | |||
==Wildcard Sub-Domain== | ==Wildcard Sub-Domain== | ||
| Line 19: | Line 28: | ||
A wildcard DNS record is a record in a DNS zone that will match requests for non-existent domain names. A wildcard DNS record is specified by using a "*" as the leftmost label (part) of a domain name, e.g. *.example.com. | A wildcard DNS record is a record in a DNS zone that will match requests for non-existent domain names. A wildcard DNS record is specified by using a "*" as the leftmost label (part) of a domain name, e.g. *.example.com. | ||
Wildcard sub-domain procedures: | |||
* [[Bind_Operations_-_Set_Up_DNS_Server#Declare_a_Wildcard_DNS_Domain|Declare a Wildcard Subdomain in bind]] | |||
* [[godaddy.com#Setting_Up_a_Wildcard_DNS|Setting Up a Wildcard DNS at godaddy.com]] | |||
* [[Add_a_Zone_File_to_Kubernetes_CoreDNS#Wildcard_Domain|Setting up a Wildcard Domain with CoreDNS in Kubernetes]] | |||
=Zone Records= | =Zone Records= | ||
| Line 39: | Line 51: | ||
==CNAME (Alias)== | ==CNAME (Alias)== | ||
A CNAME is an alias for a host. Using CNAMEs, you can have more than one DNS name for a host. CNAME records point back to the A record, which is referred to as the "canonical name" of the CNAME. When you change the IP address in your A record, all CNAME records for that domain name automatically follow the new IP address. | A CNAME is an alias for a host. Using CNAMEs, you can have more than one DNS name for a host. CNAME records point back to the [[#A_.28Host.29|A record]], which is referred to as the "canonical name" of the CNAME. When you change the IP address in your [[#A_.28Host.29|A record]], all CNAME records for that domain name automatically follow the new IP address. | ||
==MX (Mail Exchanger)== | ==MX (Mail Exchanger)== | ||
| Line 73: | Line 85: | ||
{{Internal|Linux_Hostname#Host_Name_and_the_Domain_Name|Linux_Hostname#Host_Name_and_the_Domain_Name}} | {{Internal|Linux_Hostname#Host_Name_and_the_Domain_Name|Linux_Hostname#Host_Name_and_the_Domain_Name}} | ||
</font> | </font> | ||
=DNS Servers= | |||
* <span id='bind'></span>[[bind]] | |||
* <span id='Dnsmasq'></span>[[Dnsmasq|Dnsmasq]] | |||
* <span id='CoreDNS'></span>[[CoreDNS]] | |||
=DNS Naming Standards= | |||
==DNS Subdomain Name== | |||
{{External|https://tools.ietf.org/html/rfc1123}} | |||
The name: | |||
* contains no more than 253 characters | |||
* contains only lowercase alphanumeric characters, '-' or '.' | |||
* starts with an alphanumeric character | |||
* ends with an alphanumeric character | |||
==DNS Label Name== | |||
{{External|https://tools.ietf.org/html/rfc1123}} | |||
The name: | |||
* contains at most 63 characters | |||
* contains only lowercase alphanumeric characters or '-' | |||
* starts with an alphanumeric character | |||
* ends with an alphanumeric character | |||
Latest revision as of 03:52, 6 February 2021
External
Internal
DNS Name
DNS Host
DNS Domain
Fully Qualified Domain Name (FQDN)
Zone
A zone, also referred to as hosted zone, is a container for zone records, which include information about how you want to route traffic for a domain and all of its subdomains. A hosted zone has the same name as the corresponding domain.
Zone File
A zone file organizes the zone records for domain names and sub-domains in a DNS server. Every domain name and sub-domain has its own zone file, and each zone file contains zone records.
Domains and Sub-Domains
Sub-domains are extensions of a domain name. For example, for the "novaordis.com" domain name, "internal.novaordis.com" is a sub-domain. Although domain names might have sub-domains, the zone files for sub-domains are not considered sub-zones. All zone files are separate entities and do not have a hierarchical structure. With godaddy.com you one can add up to 90 sub-domains per domain name. Multiple levels of sub-domains can also be added. Each sub-domain can be up to 25 characters long. Sub-domains that point to IP addresses can be simply added as A records.
Wildcard Sub-Domain
A wildcard DNS record is a record in a DNS zone that will match requests for non-existent domain names. A wildcard DNS record is specified by using a "*" as the leftmost label (part) of a domain name, e.g. *.example.com.
Wildcard sub-domain procedures:
- Declare a Wildcard Subdomain in bind
- Setting Up a Wildcard DNS at godaddy.com
- Setting up a Wildcard Domain with CoreDNS in Kubernetes
Zone Records
The most common records contained in a zone file are start of authority (SOA), nameserver, mail exchanger, host, and CNAME. These are described below.
Start of Authority (SOA)
Required for every zone file, the SOA record contains caching information, the zone administrator’s email address, and the master name server for the zone. The SOA also contains a number incremented with each update. As this number updates, it triggers the DNS to reload the zone data.
A (Host)
A records (also known as host records) simply point a domain name or sub domain to an IP address. Uses the A record to map an IP address to a host name. This is the most common type of record on the Internet.
"@" represents the entire domain. "@" for "novaordis.com" represents ... "novaordis.com". Entering "@" for the host name is the same as entering your domain name.
To create a wildcard A record, enter an asterisk ("*") for the host name. The wildcard makes the server respond with the IP address specified instead of an error, if the sub-domain queried does not exist within your zone file.
CNAME (Alias)
A CNAME is an alias for a host. Using CNAMEs, you can have more than one DNS name for a host. CNAME records point back to the A record, which is referred to as the "canonical name" of the CNAME. When you change the IP address in your A record, all CNAME records for that domain name automatically follow the new IP address.
MX (Mail Exchanger)
The MX record provides the mail server information for that zone to deliver email to the correct location.
TXT (Text)
This is an informational record. Use it for additional information about a host or for technical information to servers.
SRV (Service)
SRV records are resource records used to identify computers hosting specific services.
AAAA (IPv6 Host)
AAAA records store a 128-bit Internet Protocol version 6 (IPv6) address that does not fit the standard A record format. For example, 2007:0db6:85a3:0000:0000:6a2e:0371:7234 is a valid 128-bit/IPv6 address.
NS (Nameserver)
The NS record contains the name server information for the zone.
Reverse DNS
Reverse DNS (rDNS) is name resolution that looks up an IP addresses to obtain a domain name, performing the opposite function of the DNS server, which turns domain names into IP addresses.
Host Name and the Domain Name
Research the proper way of naming a machine (relative to domain name) when it has one IP address internally and another IP address externally. Now I am using a short name "not500". Also see
DNS Servers
DNS Naming Standards
DNS Subdomain Name
The name:
- contains no more than 253 characters
- contains only lowercase alphanumeric characters, '-' or '.'
- starts with an alphanumeric character
- ends with an alphanumeric character
DNS Label Name
The name:
- contains at most 63 characters
- contains only lowercase alphanumeric characters or '-'
- starts with an alphanumeric character
- ends with an alphanumeric character