Web Site

Domain-name-system.org


» Domain Name System » Topics begins with L » LV resource record


Page modified: Friday, June 23, 2006 20:29:01

LV resource record (LV = name server) can realize two different functions:

  • A NS-RR defines, which autoritativen name servers for this zone officially admit are
  • A NS-RR concatenates zones to a zone tree (delegation)

Note to function 1: A zone can possess still further autoritative name servers, for which no LV-RRs exists. Such servers are called stealth servers.

Structure

Domain for which the entry istTTL indicates, like for a long time this RR in a Cache valid its being allowed minutes IN (Internet) service LV (name service) - list server name of the name server autoritativen for this domain

Listing of autoritativer name servers

In each zone file at least a NS-RR must be present, which indicates, which name server for this zone is autoritativ. The appropriate LV-RRs is usually at the beginning of a zone file directly behind the SOA-RR.

Example

In the zone file example.com exist the following LV-RRs:

example.com. 1800 IN LV names1.example.com. example.com. 1800 IN LV names2.example.net. 

From the LV-RRs alone it is not to be read off who Primary and who Secondary name server is. The Primary name server is specified in the SOA resource record. All other LV entries refer name servers to Secondary.

Zone delegation

Over LV-RRs can be defined references to The appropriate is paged out to a certain extent from the zone file. A such NS-RR serves thereby as pointer which refers to another name server (or to another zone file of the same server). One speaks in this connection also of delegation. Resolver inquiries are delegated to another name server. The appropriate LV-RRs is usually registered over the zone file scattered.

Example

In the zone file example.com exists the following line:

zone.example.com. 1800 IN LV names1.example.com. zone.example.com. 1800 IN LV names1.zone.example.com. 

Thus now the zone zone.example.com is delegated within example.com to the two name servers, which are autoritativ responsible thereby. To consider is still that names1.zone.example.com lies within the zone, for which it is responsible. A dissolution of this name to the IP address is not now possible, since only the server can make the dissolution. For this reason Glue so mentioned record is inserted, that is A resource record, which makes evenly this allocation possible. In our example would be thus still another names1.zone.example.com. 1800 IN A 192.168.7.200 necessarily.


Articles in category "LV resource record"

We found here 2 articles.

L

» LOC resource record
» LV resource record

Related Websites

We found here 6 related websites.

Page cached: Wednesday, July 5, 2006 14:16:02
Valid XHTML 1.0!  Valid CSS!

Page copy protected against web site content infringement by Copyscape