2 - 3 - 8 - A - B - C - D - E - F - G - H - I - K - L - M - N - O - P - Q - R - S - T - U - V - W - X
DNS
Click on the red underlined text to get to the source
... Even when effective summarization is possible to hide the details of
routing, DNS, filters, and other services may be affected by any
...
... and other infrastructural servers. Examples of these servers are
given in the "Network Management" section below. DNS itself,
however, may be an important exception.
...
... however, may be an important exception.
Wherever possible, servers should be referenced by DNS name rather
than by IP address. If a specific router ...
... hosts. If traceroute displays
DNS names rather than IP addresses, certain debugging options can be
transparent through the address ...
... address/name correspondences that will not be affected by a change in
the DNS server.
Different DNS ...
... DNS server.
Different DNS databases are affected by renumbering. For example,
the enterprise usually controls its own "forward" data base ...
... routing system. Coexistence over a significant period of time is
especially likely for DNS references to addresses that are known in
the global Internet ...
... address.
DNS RR statements can end with a semicolon, indicating the rest of
the line is a comment. This can be used as the basis of tools ...
... the line is a comment. This can be used as the basis of tools to
renumber DNS names for router addresses, by putting a comment (e.g.,
...
... SNMP to find the specific local-to-global mappings in effect.
There are also issues for DNS, DHCP, and other address management ...
... mechanisms that assign or resolve addresses (e.g., DHCP, DNS),
mechanisms that use IP addresses for identification (e.g., SNMP ...
... Another area of dynamic behavior that can be affected is caching.
Application servers, directory functions such as DNS, etc., may cache
IP addresses ...
...
It is worthwhile to distinguish that a router's use of a DNS name
does not necessarily mean that name is defined in a name server.
...
... address to name mappings local to the
router, so both the DNS zone files and the router configurations will
need to be checked.
...
... configuration file, RR in our zone's DNS, RR in a zone file outside
ours), the definition statement (or equivalent if the routers ...
... hosts may not have been maintained as systematically as
are RR records in a DNS server. It is entirely possible that
different host mapping entries for the same name point to different
...
... router renumbering.
Caches in DNS servers both inside and outside the organization may
have sufficient persistence that a "flag day" cutover is not
practical if worldwide connectivity is to be kept. DNS ...
... DNS servers both inside and outside the organization may
have sufficient persistence that a "flag day" cutover is not
practical if worldwide connectivity is to be kept. DNS can help,
however, make a period of old and new address coexistence work.
...
... address.
DNS RR statements can end with a semicolon, indicating the rest of
the line is a comment. This can be used as the basis of tools ...
... the line is a comment. This can be used as the basis of tools to
renumber DNS names for router addresses, by putting a comment (e.g.,
...
... routing, there may be static name
definitions. Such definitions are probably harder to keep maintained
than entries in the DNS, simply because they are more widely
distributed.
...
... perl script called h2n converts host tables into zone data files that
can be added to the DNS server. It is available as
ftp://ftp.uu.net/published/oreilly/nutshell/dnsbind/dns.tar.Z.
...
... ftp://ftp.cus.cam.ac.uk/pub/software/programs/DNS/makezones ...
... ftp://ftp.cus.cam.ac.uk/pub/software/programs/DNS/makezones
See the DNS Resources Directory at http://www.dns.net/dnsrd.
...
... Routers may have other unique identifiers, such as DNS names used for
the set of addresses on the "box," or SNMP ...
... Changes to this pseudo-address may have implications for DNS. Even
if this is not a real address, A and PTR resource records ...
... addresses.
Another potential DNS implication is that a CNAME may have been
established for the entire set of interface ...
... Internet unless explicitly used for exterior
routing. External traceroutes will also fail reverse DNS lookup.
...
... LAN segment is populated only by clients that communicate with key
servers (e.g., DNS or DHCP) by sending limited broadcasts. Router
interfaces ...
... filtering events, typically denial
of access. If logging is implemented, logging servers to which log
events are sent preferably should be identified by DNS name. If the
logging server is referenced by IP address, its address ...
...
Another component of a firewall system is the "split DNS" server,
which provides address mapping in relation to the globally visible
...
... address space for router IDs, as long as these can be looked up in a
DNS server within the domain.
...
... services. In
general, try to convert script references to IP addresses to DNS
names.
A critical ...
...
During renumbering, it will probably be useful to assign DNS names to
interfaces, virtual interfaces ...
...
If dynamic addressing is used, dynamic DNS should be considered.
Since this is under development, it may be appropriate to consider
proprietary means to learn what addresses ...
... Also remember that some name resolution may be done by static tables
that are part of router configurations. Changing the DNS entries,
and even restarting the routers ...
...
Hard-coded references to NTP servers should be changed to DNS when
possible, and renumbered otherwise.
...
... security, such as pointers to authentication,
logging, and DNS servers.
During a renumbering operation, it may be appropriate to introduce
...
... Remember static name definitions in routers may not be affected
by DNS changes.
Coordinate changes with affected external organizations (e.g.,
ISPs ...
... router
configuration files, DNS zone files, and other information that
documents your present environment.
...