1 - 2 - 8 - A - B - C - D - E - F - G - H - I - K - L - M - N - O - P - Q - R - S - T - U - V - W - Z
network
Click on the red underlined text to get to the source
... RRs should not
have a date signed significantly in the future. To prevent
misordering of network requests to update a zone dynamically,
monotonically increasing "time signed" dates may be necessary.
...
... RRs is to sort
them in ascending order by name, considering labels as a left
justified unsigned octet sequence in network (transmission) order
where a missing octet sorts before a zero octet. (See also ordering
discussion ...
... AXFR SIG. They may
originate in the network and might not, in general, be migrated to
the recommended off line zone signing procedure (see Section 7.2).
...
... DNS name compression
when being transmitted over the network. The size of the bit map can
be inferred from the RDLENGTH and the length of the next domain name ...
... A variety of time synchronization protocols exist including the
Network Time Protocol (NTP, RFC1305draft). If such protocols are used,
...
... private keys and the zone file master
copy be kept and used in off-line non-network connected physically
secure machines only. Periodically an application can be run to add
authentication ...
...
The idea is to have a one way information flow to the network to
avoid the possibility of tampering from the network. Keeping the
...
... flow to the network to
avoid the possibility of tampering from the network. Keeping the
zone master file on-line on the network ...
... network. Keeping the
zone master file on-line on the network and simply cycling it through
an off-line signer ...
... maximum security, the master copy of the zone file should be off net
and should not be updated based on an unsecured network mediated
communication.
...
... - Network Security: PRIVATE Communications in a PUBLIC World, Charlie Kaufman, Radia Perlman, & Mike Speciner, Prentice Hall Series in Computer
Networking and Distributed Communications 1995. ...
... - Mills, D., "Network Time Protocol (v3)", RFC 1305draft, March 1992. ...