To solve this problem the concept of Name Servers was created in the mid 70's to enable certain attributes (properties) of a named resource to be maintained in a known location - the Name Server.
With a Name Server present in the network any host only needs to know the physical address of a Name Server and the name of the resource it wishes to access.
Using this data it can find the address (or any other stored attribute or property) of the resource by interrogating (querying) the Name Server.
Resources can be added, moved, changed or deleted at a single location - the Name Server.
We now have a new problem with our newly created Name Server concept.Please refer to the errata for this document, which may include normative corrections.This document is also available in these non-normative formats: diff-marked HTML .If our Name Server is not working our host cannot access any resource on the network. So we had better have more than one Name Server in case of failure.allow-notify applies to slave zones only and defines a match list, for example, IP address(es) that are allowed to NOTIFY this server and implicitly update the zone in addition to those hosts defined in the masters option for the zone.I am trying to implement lazy-loading of data (infinite scrolling).