Hi,
in case of classless IN-ADDR.ARPA
delegations(http://www.ietf.org/rfc/rfc2317.txt) I have usually seen
at least one NS record pointing to name server other than the
end-customer ones. Example from rfc2317.txt where there are two NS
records and the second one is not the end-customer name
If a zone is being made available to the public (which these are)
then steps should be taken to ensure it is resolvable all the time.
This means having multiple servers that are not subject to common
failures. This is basic DNS.
In message
On 04/02/2013 12:47 AM, Martin T wrote:
Is NS record pointing to some other name server needed in case of
classless IN-ADDR.ARPA delegations? What happens if one does not
specify this?
It's very common for the parent name server(s) to slave the 2317 zone so
that it can answer directly. It's
3 matches
Mail list logo
