Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

When a name server receives a request for a domain name that does not exist in a zone, the name server sends an authenticated negative response in the form of an NSEC or NSEC3 RR. NSEC and NSEC3 records contain the next secure domain name in a zone and list the RR types present at the NSEC or NSEC3 RR's owner name. The difference between an NSEC and NSEC3 RRs is that the owner name in an NSEC3 RR is a cryptographic hash of the original owner name prepended to the name of the zone. NSEC3 RRs protect against zone enumeration.
Following is an example of an NSEC record:

Drawio
width
bordertrue
viewerToolbartrue
fitWindowfalse
diagramNameArrow3
simpleViewerfalse
1
baseUrlhttps://infoblox-docs.atlassian.net/wiki
diagramNameArrow3
zoom1
pageId22252203
custContentId7345809
lbox1
contentVer1
revision1


The first four fields specify the owner name, TT, class and RR type. The succeeding fields are:

...

Following is an example of an NSEC3 RR:

Drawio
bordertrue
viewerToolbartrue
fitWindowfalse
diagramNameArrows4
simpleViewerfalse
width1
baseUrlhttps://infoblox-docs.atlassian.net/wiki
diagramNameArrows4
zoom1
pageId22252203
custContentId7345803
lbox1
contentVer1
revision1


The first field contains the hashed owner name. It is followed by the TTL ,class and RR type. The fields after the RR type are:

...