Opened 10 years ago

Closed 9 years ago

#63 closed defect (invalid)

auth returns apex NSEC+RRSIG with NXDOMAIN

Reported by: jinmei Owned by: jinmei
Priority: medium Milestone: 03. 1st Incremental Release
Component: Unclassified Version:
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity:
Sub-Project: Feature Depending on Ticket:
Estimated Difficulty: Add Hours to Ticket:
Total Hours: Internal?:

Description

In the authority section, the first RRs are unnecessary.

% dig @127.0.0.1 -p 5300 foobar.jinmei.org a +dnssec

;; AUTHORITY SECTION:
jinmei.org. 1200 IN NSEC cvs.jinmei.org. NS SOA MX RRSIG NSEC DNSKEY
jinmei.org. 1200 IN RRSIG NSEC 5 2 1200 20100402185826 20100303185826 48576 jinmei.org. gEsUI0c2CZciN0NOaytpHDsm8qJd1C6i+LxNlH24LMg3pCB5RYDb4gER 6R54MDhsjVlri/ayu1dfY5hqbMLiPiEO2R0N3icjDiBa0yH/qncYMQX1 KGaHJLg/tFEbsQ9AoX5Nr6EOPmgPchUUujqXZqZcyGVk693RnsFvy0aL wXI=
jinmei.org. 86400 IN SOA ns.jinmei.org. jinmei.kame.net. 2010030300 7200 3600 2592000 1200
jinmei.org. 86400 IN RRSIG SOA 5 2 86400 20100402185826 20100303185826 48576 jinmei.org. DeXE1Ps2wLKybzDFPaodyMYpqVxNtyY098CYLYFN54dbzLBQjgTMHCIe T+BBpkvbnsbzl9gaFuPBI6sq1Bs3IBzxCsm3rQs6fykm0NO8neJ9C5OY wwZuJwU39hmSN/D4rUArcWvCsXXYIyIiUUndl1F5LBT02vI3sKzkGSZy F8E=
foo.jinmei.org. 1200 IN NSEC gate.jinmei.org. NS RRSIG NSEC
foo.jinmei.org. 1200 IN RRSIG NSEC 5 3 1200 20100402185826 20100303185826 48576 jinmei.org. vv7KyeT04BzS6Formy++EZwrnw9MPUumK7eKGMLbZiThbQNQXgZ54X+c 7utT6YK2l1xZIiY3GdGrHymhLnixrL55lgIcKOz/UUKwPalOEp4cCQaH K1jtGWkxxDJyByGrZTs1O3lcgh1fxiL8jJ8DehbE90GG45s4QZZm036Z 2X8=

Subtickets

Change History (2)

comment:1 follow-up: Changed 10 years ago by shane

  • Owner set to jinmei
  • Status changed from new to assigned

Can you check again?

comment:2 in reply to: ↑ 1 Changed 9 years ago by jinmei

  • Resolution set to invalid
  • Status changed from assigned to closed

Replying to shane:

Can you check again?

I realized I was confused. The auth server worked correctly in this case (there was nothing to be fixed). Closing.

Note: See TracTickets for help on using tickets.