[Autogenerated] Now Jaden needs to go
ahead and add some records to the primary
server. He'll confirm the record movement
from the primary to the secondary via wire
shark. Where US Primary. We'll go ahead
and start a new capture. Our goal is to
add a few more records, so we'll go into
the DNA snap in and add a new host record.
Our server is named sales, and it's IP
address is 10 12.3 dot eight. We'll go
ahead and create the Associated Pointer
record at the same time. Now we actually
have to IP addresses for sales so that we
can do load balancing. So we'll also add
in 10 12 3D at 18. In case someone types
in the three W's for our domain name.
We'll go ahead and add a C name record or
canonical name for that. Alias will want
it to point to the sales server. Now we
can go ahead and just type in the fully
qualified domain name or we can. Browse
and look for it. I'll choose the first in
the list because what matters is the name,
not the IP address. Remember, will
redirect that Alias alias to the true or
canonical name. We're going to need an SRV
record as well, so I'll go in to other
records and scroll down to service
location. That's an SRV record or service
record. We'll go ahead and add a Kerberos
services. If we were using
Active Directory, these held app protocol
would be used to find a resource. The curb
rows protocol is used. Check your
permissions for the resource. Often this
is all done on the same server, and it's
an internal process. But the larger the
environment, the more likely the services
offloaded to its own. Server Clients have
no way of knowing who the Kerberos and L'd
apps servers are, so they use DNA Jest to
look for the service I'll put in the
servers IP address of 10 12 3D at seven.
Notice the layout of the record is a bit
different. It will be underscore protocal
name, underscore TCP and then underscore
the domain name. Let's see how all this
looks in wire shark. I'll filter for
Dean's first. I'm interested in the zone
Record exchange. There they are. I X f our
records. Incremental transfers. Remember
the A X F R record was used when it was a
new zone and we had to transfer the entire
database. Now we simply added a few
records, so we only need to send the
changes. That's the definition of
incremental. I'll filter for the
incremental transfer query Type 2 51. The
requests are being sent by the secondary
because when the zone was updated, the
primary sent out to the secondary a zone
change notification record. Here's our
edition of the sea name record of the
Pointer Records and the are records. When
we look at the incremental transfer, we'll
see what records actually got sent. First
is these SSH record notice that the serial
number is up to seven. Now there's our new
SRV record and see how the name of the
record is different with the underscores
and protocol names. The type is SRV, and
it lists priority and wait. If I had
multiple curb rows servers or any of the
same type of SRV record, it would give me
a chance to put in which one had the
highest priority. If you have multiples,
you'll have to list each one with a
different priority. That way, when the
dean's responses go to the clients the
clients can do use the priority number to
determine which of the addresses for that
service type they should attempt to go to
first. You'll also see this in M X records
for email servers because that's actually
where it started. These AMX record for the
email servers was the only service type in
the original RC for DNA Jest as time went
on and services were added. Instead of
adding a different record type for each
different type of service, they added the
SRV record to take care of any new service
and the priority and wait fields just
followed along. We also have a listing for
the port, and 88 is the standard port for
Kerberos. There's a different incremental
transfer record request for each of the
different records, we added. That's
because every change we committed to N S
primary sent off that notification that
there was a change in the zone. Since this
is a filter we may do again and again,
let's save it as a display filter button
on the filter bar. We're going to edit and
preferences and filter _______. We can
change the name of the button label to
take advantage of filter button grouping
I'll put in Q type / / and that will add
it to the Q type group. We don't even have
to rearrange them to have them all
together, because wires shark does that
for us. See how now they're at the end of
our list. Nice, quick way to go ahead and
filter for any of the query types. JSON
wants to practice adding records and bind.
But Ennis Bind is already a secondary in
the gt dot g m dot com domain. He knows he
can only add records to the primary. Since
their copy of the database is read right.
Jaden's using web hman so he doesn't have
to do everything at the command line.
He'll just go ahead and make a new primary
domain. Global ticket gm dot com All of
the options look familiar. It's just the
layout that's different. He'll add the
name server record for Ennis Bind. We'll
go back and there are the zone tiles. If
we go into the new global ticket's own
we can, add a host record for the band
server. The great thing about web hman is
Jaden can do. Check his CONFIG files right
within the web interface in the name Deed
Config file. He has an access control list
for the 10 network. Suhani is a security
analyst for Globomantics. She's coming in
a bit later to help jade and hard in the
servers. She'll want him to tighten up
that list to just the networks for
Globomantics and their divisions. There's
the list of name servers, then in the name
D V8 DOM Options File is That s Primary is
who the bind server forwards to in the
name D could fig dot local file is the
zone that Jaden created. The name D config
dot default. Dat's own name, D config dot
default dot zones lists all of the zones
that are default in bind. We'll go back
and there are the zone tiles will go into
the global ticket zone and then go into
the all records tile. And there's our two
entries. Notice we could edit each t t l in