DNS Zones and Records Explained
Key Points
- DNS translates human‑readable domain names (e.g., dubdub.ibm.com) into IP addresses so browsers can locate web resources.
- A DNS **zone** is an administratively controlled segment of the DNS namespace that contains a collection of records.
- **Records** (resource records) are the individual entries within a zone, such as A records that map a hostname to an IP address.
- Multiple records with the same name but different values form a **resource record set (RRset)**, allowing a single hostname to resolve to several IPs.
- **NS (name server) records** delegate sub‑zones to other teams or servers, enabling separate groups to manage their own DNS entries (e.g., api.subzone.ibm.com).
Sections
- Understanding DNS Zones & Records - The speaker reviews DNS fundamentals before explaining that a DNS zone is an administratively controlled segment of the name space containing various record types (like A records) that map domain names to IP addresses.
- DNS Zones, Subzones, and Records - The speaker explains how DNS zones delegate authority via NS redirection to subzones and outlines the fields and common types of DNS records, such as A records.
- DNS Record Types Overview - The speaker explains how priority name servers, CNAME redirections, TXT records, and NS delegation work together to provide redundancy and routing in DNS management.
Full Transcript
# DNS Zones and Records Explained **Source:** [https://www.youtube.com/watch?v=U-i_UDDYLxY](https://www.youtube.com/watch?v=U-i_UDDYLxY) **Duration:** 00:08:27 ## Summary - DNS translates human‑readable domain names (e.g., dubdub.ibm.com) into IP addresses so browsers can locate web resources. - A DNS **zone** is an administratively controlled segment of the DNS namespace that contains a collection of records. - **Records** (resource records) are the individual entries within a zone, such as A records that map a hostname to an IP address. - Multiple records with the same name but different values form a **resource record set (RRset)**, allowing a single hostname to resolve to several IPs. - **NS (name server) records** delegate sub‑zones to other teams or servers, enabling separate groups to manage their own DNS entries (e.g., api.subzone.ibm.com). ## Sections - [00:00:00](https://www.youtube.com/watch?v=U-i_UDDYLxY&t=0s) **Understanding DNS Zones & Records** - The speaker reviews DNS fundamentals before explaining that a DNS zone is an administratively controlled segment of the name space containing various record types (like A records) that map domain names to IP addresses. - [00:03:07](https://www.youtube.com/watch?v=U-i_UDDYLxY&t=187s) **DNS Zones, Subzones, and Records** - The speaker explains how DNS zones delegate authority via NS redirection to subzones and outlines the fields and common types of DNS records, such as A records. - [00:06:21](https://www.youtube.com/watch?v=U-i_UDDYLxY&t=381s) **DNS Record Types Overview** - The speaker explains how priority name servers, CNAME redirections, TXT records, and NS delegation work together to provide redundancy and routing in DNS management. ## Full Transcript
today we're here to learn about
DNS
zones and
Records first let's start with a quick
review of the DNS as you may remember
DNS is the protocol that's used to
convert the name that someone types in
their
browser into a name into a number that
the computer can understand so for
example the user types dub du.
ibm.com their PC talks to the local
resolver which then goes out to the DNS
uh to an authoritative DNS name server
who looks up that name dubdub du.
ibm.com and Returns the IP address for
dubdub du. ibm.com and then the user is
able to get to the web page for IBM and
go view all of our products
now this all works great but you may be
uh now responsible for DNS and need to
set it up for your particular
application so you're wondering you know
what what are these things that I'm
hearing about zones records RR sets all
this different terminology what is what
does it all mean and how do I use it so
let's start at the beginning with what
is a zone so a DNS zone is an area of
administrative control of a portion of
the DNS name space so for example we
might have a Zone for
ibm.com and inside the Zone we're going
to have a number of
Records just right and records are
things like
um dub
dubdub uh would be the record the type
is I in I'll go over all this in more
detail in a minute it's an a record type
and the IP address is 9991 now I might
have another record also dub dub dub
actually we'll do four dubs I in a and
it's
9992 what this means is that there's two
records with the same label with the
same name and that's called a resource
record set you'll often hear that uh in
the DNS terminology all it means is that
there's multiple records with the same
name but different values different
answers want to also mention here a
special record type
called a name server record and that's
used to do what we call delegate the
zone to another group The use case for
this is for example uh maybe the central
CIO team is managing ibm.com but there's
another group for which you want to give
access to a portion of the DNS and you
want to give them their own Zone on
their own server so in that case you'll
set up a special record type called
subzone uh this this is the name It'll
point to an n a name server record and n
s and we'll just uh say it's going to
subzone Nam server.
ibm.com now what that does is it creates
this redirection to another
Zone called uh
subzone uh sub zone.
ibm.com and in here we can also set up
records so say maybe that team wants to
set up an API so they create a record
API also an a record and it points to
99110 so this would uh when someone does
a lookup over there for api. sz. ibm.com
it will first go to uh this Zone which
will then redirect it via this NS record
to a subzone where it will find the
answer api. Sub zone. ibm.com in return
99910 do10 that's an overview of zones
which are an area of administrative
control of a portion of the DNS
namespace and Records which are the
entries or the rows in the database that
actually provide the
data so now let's talk a little bit
about the different types of records
that are
available so if I um go over here and
let's talk about the format of Records
so records have uh a number of fields
first they have the owner field which is
like the dubdub dub they then have a
class so let's fill this in as I go so
this is dub dub dub the class would be
in in there are a number of classes
defined but the only one you'll ever see
used is in in which stands for internet
uh the other ones are mainly
experimental are used for odd use cases
which you almost never see uh then we
then have a
type uh the most common example you'll
see is the a record and then you'll have
a
value and the value is um the the number
here 1.11.1 for example
um let's go through a few different
types just to give you a feel for what
are the types out there I'm not going to
cover them all um but before I get
started I want to refer you to a website
a.org
that's the official body that maintains
the list of all the different record
types and you can go there and see the
full list of what's available but I'll
cover uh the main ones uh that people
tend to use so the next one we have is
called the quad a record uh which is
written as foras and it's for an IPv6
address so something like 2001 colon
colon um one 27
would be an IPv6 address another common
type we have is the mail server
address uh which is an MX record that
has two portions to the value it's got a
priority and the mail server name so
something like
mail.
ibm.com it allows you to set up multiple
name servers so maybe I have another one
that's priority to that's maybe mail to.
ibm.com what that means is that um the
sender will first try the priority one
entry if that doesn't work then it'll
try the priority 2 entry so there's kind
of built-in redundancy enabled through
the DNS another common type is called
the C name so if I have one uh just take
a label Fu I in C
name and this one is stands for
canonical name it's essentially a
redirection so in this case if someone
types in fu. m.com I'll redirect them to
dubdub
dub.
ns.com and that's just a straight text
replacement fu. ibm.com gets replaced
with dubdub dub. ibm.com you'll often
see this used uh when you're deploying
your website into a CDN where the CDN
will provide you the value to use with
for your canonical name or your cname
record Another common one is a text
record and so if we have a record like
this text and we can just say hello
world if someone types in um types in
hello. ibm.com they'll get back the text
hello world and the last one which I
showed over here is just the NS record
uh just for completeness We'll add it in
um and we'll have subzone ns.
ibm.com and again that's for delegate
your Zone to a different entity so that
they can also work on the Zone again
these are just a few examples check out
the site.org for the full list and
hopefully now you have a good idea of
the terminology of DNS and you're on
your way to becoming a DNS administrator
thank you if you like this video and
want to see more like it please like And
subscribe if you have any questions or
want to share your thoughts about this
topic please leave a comment below