Now when we've added another domain control and DNS server to our demand list DNS server is automatically
replicated zones from the first domain controller the first DNS server.
You can check it in DNS manager and see that all the zones we've had on the Lapidus the one now are
replicated to lab DC 2 and 2.
For now let's reach on level do see one and do some experiments.
Remember for export zone to file which name was like this.
So now we will call Piers's file and try to restore the zone from this file will copy and paste it in
some location on DC to then we will delete this Ozon to imagine that it was accidentally deleted and
we want to restore it so we can do that with the foreign command to add DNS server.
Second the rezone then we have to specify the files name zone file and we have to load it from existing
file and the master server from this search for this secondary's zone will be our master DNS server
which reaches Gleb DC 1 and of course pass through perimeter to see the results.
So let's perform this operation and this you can see the zone is created.
The second Arizonians created from this file which was copped earlier as was the primary zone.
You can change the certains of a second rezone secondary DNS zones have fewer certains because they
are Read-Only zones dependent on their master server.
When you create your secondary DNS zone all of the certains for the zone can be searched as part of
the at the DNS server.
Second the rezone common.
However if you later need to change those values to change the master server for example you can use
the cert the DNS server seconder alone Gaumont left to modify those loans certains to modify the same
zone which we have now restored.
We can do the following command.
Set the DNS servers under a zone name.
In our case it's a name like this.
And then the master server's parameter and specify Mostel servers.
Let's say that we have changed master server but in this case it's only an experiment.
So I'll specify the master server which is now in place for this zone and pass through parameter to
check if it is performed or key.
Also remember that when you set the properties of a reverse lookup zone you can use either the name
parameter or the network ID parameter.
Some votes about configuring zone trend for certains as long as secondary zone can only transfer the
zone from a primary zone that allows that transfer prevention an authorized loan transfers to certain
of the zone transfer permissions is done at the primary zone not at the secondary zone to set the zone
transfer permissions use a set.
There's DNS server primary zone and let the secure secondary's perimeter controls the servers to reach
transfers are allowed the secure secondary's perimeter accepts the following.
Well there is no transfer transfer any server transfer to zone name server and transfer to a secure
server.
So no transfer parameter allows no transferred for the zones from this server transfer any server any
server can request a zone transfer including service that you know nothing about and don't manage or
control the next parameter transfer to a zone name server on the servers and the and health records
for this zone are allowed to request transfers and S-turns for name servers and the last parameter transfer
to secure servers only servers specified with the secondary service parameter are allowed to request
a loan transfer to set the lab dot com zone zone to only allows zone transfers from name servers use
the following command set this DNS server primary zone then the parameter name.
In my case its leaped out gone securest secondary's transfer to zone name server and pass through parameter.