References; Assigning Name Servers; Figure 24: Dns Hierarchy Example - Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - SYSTEM BASICS CONFIGURATION GUIDE 2010-10-04 Configuration Manual

JunosE 11.3.x System Basics Configuration Guide

References

Assigning Name Servers

306
A name server may provide the translation from its cache or may poll servers lower in
the DNS hierarchy to obtain a translation. Typically, name servers at the top of the
hierarchy recognize top level domain names and know which servers to contact for
information about more detailed domain names. See Figure 24 on page 306.

Figure 24: DNS Hierarchy Example

DNS messages from a name resolver to a name server must include the domain name
for the resolver's clients. Consequently, you must specify a default domain name for the
clients. The default domain name is appended to unqualified hostnames (those without
domain names).
The name resolver must be able to access at least one name server. Accordingly, you
must configure a static route to a gateway that provides access to the name server and
assign the name server to the name resolver. For more information, see "Assigning Name
Servers" on page 306.
Each virtual router can have its own name resolver and domain name. However, if two
virtual routers use the same name servers and belong to the same local domain, you do
not need to configure name resolvers on both virtual routers. For more information, see
"Using One Name Resolver for Multiple Virtual Routers" on page 308.
For more information about the DNS, consult the following resources:
RFC 1035—Domain Names – Implementation and Specification (November 1987)
RFC 2308—Negative Caching of DNS Queries (DNS NCACHE) (March 1998)
To assign name servers to the system:
Access the virtual router context.
1.
Define static routes to the gateways that provide access to the name servers.
2.
Enable the virtual router to query name servers.
3.
Specify a default domain name for the hosts.
4.
Specify the name servers.
5.
Copyright © 2010, Juniper Networks, Inc.