Tahi users and developers,
Is anyone also having an ipv6 dns self test with koi-1.1.1.tgz
and DNS_Self_Test_1-1-1.tgz ?
When i do it with FreeBSD6.2 (TN) and rhel5(NUT), i found that
many test cases fail regardless of client mode or server mode.
And when i do it with FreeBSD6.2 (TN) and FreeBSD6.2(NUT),
many test cases still fail.
How about your ipv6 dns test reports?
Look forward to communication with you.
For more information, pls refer to the summary of the report
with FreeBSD6.2 (TN) and FreeBSD6.2(NUT).
IPv6 Conformance Test For DNS
________________________________________________________________________
Tool Version :
REL_1_1_1
Test Program Version :
REL_1_1_1
________________________________________________________________________
Start:
2008/01/16 12:13:34
End :
2008/01/16 14:59:29
________________________________________________________________________
________________________________________________________________________
No.
Title
Result
Log
Script
Dump
Server Test
RFC 1034:
Domain
Concepts and
Facilities
3. DOMAIN
NAME SPACE
AND RESOURCE
RECORDS
3.1. Name
space
specifications and terminology
1
Label length
PASS
X
X
Link0
2
Case-insensitive manner
PASS
X
X
Link0
3
Domain Name
length
PASS
X
X
Link0
3.5.
Preferred
name syntax
4
Rule for
label
PASS
X
X
Link0
3.6.
Resource
Records
NAME
NAME (owner)
is tested at
TYPE test.
TYPE
5
A type
PASS
X
X
Link0
6
CNAME type
PASS
X
X
Link0
7
HINFO type
PASS
X
X
Link0
8
MX type
PASS
X
X
Link0
9
NS type
PASS
X
X
Link0
10
PTR type
FAIL
X
X
Link0
11
SOA type
PASS
X
X
Link0
CLASS
12
IN class
PASS
X
X
Link0
CH class
TTL
RDATA
13
A resource
data (IN
class)
PASS
X
X
Link0
A resource
data (CH
class)
14
CNAME
resource
data
no test
sequence
X
X
Link0
15
HINFO
resource
data
PASS
X
X
Link0
16
MX resource
data
FAIL
X
X
Link0
17
NS resource
data
FAIL
X
X
Link0
18
PTR resource
data
PASS
X
X
Link0
19
SOA resource
data
PASS
X
X
Link0
Caching
20
Zero TTL
prohibits
caching
PASS
X
X
Link0
3.6.2.
Aliases and
canonical
names
21
CNAME RR is
present at a
node, no
other data
should be
present
PASS
X
X
Link0
22
* query
should
return just
the CNAME
PASS
X
X
Link0
3.7. Queries
23
Carried in
TCP
PASS
X
X
Link0
24
Standard
message
format
PASS
X
X
Link0
25
Opcode
(standard
query)
PASS
X
X
Link0
Opcode
(status
query)
3.7.1.
Standard
queries
26
Question
section
format
PASS
X
X
Link0
QTYPE
27
* type for
query
PASS
X
X
Link0
28
* type for
response
PASS
X
X
Link0
QCLASS
29
* class (the
requestor is
seeking data
from more
than one
class)
FAIL
X
X
Link0
3.7.2.
Inverse
queries
(Obsoleted
by RFC3425)
4. NAME
SERVERS
4.1.
Introduction
30
The name
server
returns data
w/
Authoritative Answer (AA) or not.
PASS
X
X
Link0
4.2. How the
database is
divided into
zone
4.3. Name
server
internals
4.3.1.
Queries and
responses
31
No-recursive
queries
FAIL
X
X
Link0
32
Name server
acts in the
role of a
resolver
FAIL
X
X
Link0
Recursive
mode
33
Recursion
Available
(RA) bit is
set or
cleared by a
name server
in all
responses
PASS
X
X
Link0
34
Recursion
desired (RD)
no test
sequence
X
X
Link0
Recursion is
available
case
35
The answer
with CNAME
to the
query.
FAIL
X
X
Link0
36
A name error
indicating
that the
name does
not exist.
no test
sequence
X
X
Link0
37
A temporary
error
indication.
PASS
X
X
Link0
Recursion is
not
available
case
38
An
authoritative name error indicating that the name does not exist.
PASS
X
X
Link0
A temporary
error
indication
(Tested at
4.3.1.
No-recursive
queries)
4.3.2.
Algorithm
A. And the
whole of
QNAME is
matched
39
The data at
the node is
a CNAME, and
QTYPE
doesn't
match CNAME
case.
PASS
X
X
Link0
40
The data at
the node is
except the
above-mentioned.
PASS
X
X
Link0
B. A match
take QNAME
out of the
authoritative data, QNAME has a referral.
41
QNAME is
found in the
cache.
PASS
X
X
Link0
42
QNAME is not
found in the
cache.
PASS
X
X
Link0
C. At some
label, a
match is
impossible.
43
The "*"
label does
not exist,
the name is
original.
PASS
X
X
Link0
The "*"
label does
exist.
(Tested at
4.3.3.
Wildcards)
Recursion
service is
available
and
requested
via the RD
bit in the
query.
(Tested at
5.3.3.
Algorithm.)
4.3.3.
Wildcards
44
Caching
wildcards
queries
FAIL
X
X
Link0
45
Wildcards is
not applied
case
PASS
X
X
Link0
4.3.4.
Negative
response
caching
(Optional)
4.3.5. Zone
maintenance
and
transfers
46
Zone
maintenance
and
transfers
FAIL
X
X
Link0
47
Zone
transfer is
not
completed
case
FAIL
X
X
Link0
48
Distribute
zone
FAIL
X
X
Link0
5. RESOLVERS
5.1
Introduction
5.2.
Client-resolver interface
5.2.1.
Typical
functions
49
Returning of
answer
PASS
X
X
Link0
50
Returning of
name error
PASS
X
X
Link0
51
Returning of
data not
found error
PASS
X
X
Link0
5.2.2.
Aliases
52
Encounters a
CNAME
PASS
X
X
Link0
53
Multiple
levels of
aliases
should be
avoided, but
should not
be signaled
as an error
PASS
X
X
Link0
5.2.3.
Temporary
failures
5.3.
Resolver
internals
5.3.1. Stub
resolvers
5.3.2.
Resources
54
Cache data
vs
authoritative data
PASS
X
X
Link0
5.3.3.
Algorithm
55
Answer in
local
information
PASS
X
X
Link0
56
Sending
query to
server
FAIL
X
X
Link0
57
Analyze the
response
(delegation)
PASS
X
X
Link0
58
Analyze the
response
(caching
delegation)
PASS
X
X
Link0
59
Analyze the
response
(caching
CNAME)
PASS
X
X
Link0
60
Analyze the
response
(answer is
invalid)
PASS
X
X
Link0
61
Analyze the
response
(delegation
is invalid)
PASS
X
X
Link0
RFC 1035:
Domain
Implementation and Specification
2.3.1.
Preferred
name syntax
2.3.2. Data
Transmission
Order
62
Order of
transmission
of octets
and bits
PASS
X
X
Link0
2.3.3.
Character
Case
2.3.4. Size
limits
3. DOMAIN
NAME SPACE
AND RR
DEFINITIONS
3.1. Name
space
definitions
63
Label format
PASS
X
X
Link0
64
Label of
root
PASS
X
X
Link0
3.2. RR
definitions
3.2.1.
Format
3.2.2. TYPE
values
65
WKS type
PASS
X
X
Link0
66
TXT type
PASS
X
X
Link0
3.3.
Standard RRs
(Tested at
3.2.2. TYPE
values)
3.3.14. TXT
RDATA format
67
TXT resource
data
PASS
X
X
Link0
3.4.
Internet
specific RRs
3.4.1. A
RDATA format
3.4.2. WKS
RDATA format
68
WKS resource
data
PASS
X
X
Link0
3.5.
IN-ADDR.ARPA
domain
(Tested at
3.3.12. PTR
RDATA
format)
4. MESSAGES
4.1. Format
4.1.1.
Header
section
format
69
Header
section
format
(query)
PASS
X
X
Link0
70
Header
section
format
(response)
PASS
X
X
Link0
71
Format error
(RCODE=1)
PASS
X
X
Link0
72
Server
failure
(RCODE=2)
PASS
X
X
Link0
73
Not
Implemented
(RCODE=4)
PASS
X
X
Link0
74
Refused
(RCODE=5)
for query
PASS
X
X
Link0
75
Refused
(RCODE=5)
for zone
transfer
PASS
X
X
Link0
4.1.2.
Question
section
format
4.1.3.
Resource
record
format
76
Answer
section
format
PASS
X
X
Link0
77
Authority
section
format
PASS
X
X
Link0
78
Additional
section
format
PASS
X
X
Link0
4.1.4.
Message
compression
79
Message
compression
PASS
X
X
Link0
80
Message
compression
format
PASS
X
X
Link0
4.2.
Transport
4.2.1. UDP
usage
81
Messages
carried by
UDP are
restricted
to 512 bytes
PASS
X
X
Link0
82
Not depend
on response
in order
PASS
X
X
Link0
4.2.2. TCP
usage
83
TCP
connection
management
check
PASS
X
X
Link0
6. NAME
SERVER
IMPLEMENTATION
6.1.
Architecture
6.1.1.
Control
84
Accept UDP
while server
waits TCP
connecting
PASS
X
X
Link0
6.1.2.
Database
6.1.3. Time
6.2.
Standard
query
processing
85
Processing
queries with
QCLASS=*
PASS
X
X
Link0
86
Duplicate
answer is
omitted from
the
additional
section
PASS
X
X
Link0
87
Authority
section
guarantee
uniqueness
of the
answer
SKIP
X
X
Link0
6.3. Zone
refresh and
reload
processing
6.4. Inverse
queries
(Optional)
Obsoleted by
RFC3425
7. RESOLVER
IMPLEMENTATION
7.1.
Transforming
a user
request into
a query
7.2. Sending
the queries
7.3.
Processing
response
88
Invalid
response
(query is
returned)
PASS
X
X
Link0
89
Invalid
response
(RRs are
incorrectly
formatted)
PASS
X
X
Link0
90
Invalid
response
(long TTL)
(optional)
PASS
X
X
Link0
91
Invalid
response (ID
does not
match)
PASS
X
X
Link0
92
Invalid
response
(invalid
question
section)
PASS
X
X
Link0
7.4. Using
the cache
93
Caching
several RRs
of same type
PASS
X
X
Link0
RFC 1123:
Requirements
for Internet
Hosts --
Application
and Support
6. SUPPORT
SERVICES
6.1. DOMAIN
NAME
TRANSACTION
6.1.1.
INTRODUCTION
6.1.2.
PROTOCOL
WALK-THROUGH
6.1.2.1.
Resource
Records with
Zero TTL:
RFC-1035
Section
3.2.1
Resource
Records with
Zero.
6.1.2.2.
QCLASS
Values:
RFC-1035
Section
3.2.5
6.1.2.3.
Unused
Fields:
RFC-1035
Section
4.1.1
94
Unused
fields in a
query
PASS
X
X
Link0
Unused
fields in a
query.
6.1.2.4.
Compression:
RFC-1035
Section
4.1.4
Message
compression.
6.1.2.5.
Misusing
Configuration Info: RFC-1035 Section 6.1.2
6.1.3.
SPECIFC
ISSUES
6.1.3.1
Resolver
Implementation
95
Multiplex
concurrent
requests
PASS
X
X
Link0
(A)
Full-Service
Resolver
96
Time out of
cache
PASS
X
X
Link0
(B) Stub
Resolver
6.1.3.2
Transport
Protocols
97
Not refuse
TCP query
(query)
PASS
X
X
Link0
98
Not refuse
TCP query
(response)
no test
sequence
X
X
Link0
99
Caching
truncated
responses
SKIP
X
X
Link0
100
Processing
UDP query
while zone
transfering
PASS
X
X
Link0
101
Broadcast/Multicast query
FAIL
X
X
Link0
102
Server
ignores
queries via
broadcast or
multicast
address
PASS
X
X
Link0
6.1.3.3
Efficient
Resource
Usage
103
Retransmission control
PASS
X
X
Link0
104
Caching of
temporary
failure
FAIL
X
X
Link0
6.1.3.4
Multihomed
Hosts
6.1.3.5
Extensibility
6.1.3.6
Status of RR
Types
Server loads
zone files
without
obsolete RR
types
6.1.3.7
Robustness
105
Continue to
provide
service
PASS
X
X
Link0
6.1.3.8
Local Host
Table
6.1.4. DNS
USER
INTERFACE
6.1.4.1 DNS
Administration
6.1.4.2 DNS
User
Interface
6.1.4.3
Interface
Abbreviation
Facilities
Caching of
negative
response.
(Tested at
6.1.3.3.
Efficient
Resource
Usage)
RFC 1995:
Incremental
Zone
Transfer in
DNS
2. Brief
Description
of the
Protocol
106
An IXFR
client sends
an IXFR
message
FAIL
X
X
Link0
107
An IXFR
client
receive an
IXFR
response
with the
full zone
transfer
message
FAIL
X
X
Link0
108
An IXFR
client
receive an
IXFR
response
with the
incremental
message
(add)
FAIL
X
X
Link0
109
An IXFR
client
receive an
IXFR
response
with the
incremental
message
(remove)
FAIL
X
X
Link0
110
An IXFR
client
receive an
IXFR
response
with the
incremental
message
(change)
FAIL
X
X
Link0
111
An IXFR
client
receive an
IXFR
response
with the
incremental
message
(remove/add/change)
FAIL
X
X
Link0
112
An IXFR
client tries
an AXFR, if
the query
type is not
recognized
by the
server.
FAIL
X
X
Link0
113
An IXFR
client tries
to use TCP,
if the reply
does not fit
in a single
DNS packet.
FAIL
X
X
Link0
114
An IXFR
server
transmits an
IXFR
response
with the
incremental
message
(add).
FAIL
X
X
Link0
115
An IXFR
server
transmits an
IXFR
response
with the
incremental
message
(remove).
FAIL
X
X
Link0
116
An IXFR
server
transmits an
IXFR
response
with the
incremental
message
(change).
FAIL
X
X
Link0
117
An IXFR
server
received an
IXFR request
with an
older
version
number.
FAIL
X
X
Link0
118
An IXFR
server
received an
IXFR request
with a same
version
number.
FAIL
X
X
Link0
119
An IXFR
server
received an
IXFR request
with a newer
version
number.
FAIL
X
X
Link0
120
An IXFR
server sends
a single SOA
record of
the server's
current
version, if
the UDP
reply does
not fit in a
single DNS
packet.
PASS
X
X
Link0
4. Response
Format
5. Purging
Strategy
6. Optional
Condensation
of Multiple
Versions
121
An IXFR
client
receive an
IXFR
response
with the
condensed
incremental
message
FAIL
X
X
Link0
RFC 1996:
DNS NOTIFY
1. Rationale
and Scope
1.1
1.2 The DNS
NOTIFY
transaction
allows
master
servers to
inform salve
servers when
the zone has
changed
122
An IXFR
client sends
an IXFR
message
through
NOTIFY
mechanism
FAIL
X
X
Link0
3. NOTIFY
Message
3.1
3.2
123
A master
ignores
message if
fields are
not to be
filled with
binary zero
(0).
FAIL
X
X
Link0
124
A slave
ignores
message if
fields are
not to be
filled with
binary zero
(0).
PASS
X
X
Link0
3.3
125
Slave server
sends a
NOTIFY
response
back to the
NOTIFY
request's
source.
PASS
X
X
Link0
3.4
126
Primary
Master sends
a NOTIFY
query
PASS
X
X
Link0
3.5
TCP
127
A master
continue to
offer name
service
during the
NOTIFY
transaction.
FAIL
X
X
Link0
128
A slave
sends a once
a NOTIFY
request
until
timeout
FAIL
X
X
Link0
3.6
UDP
129
A master
periodically
sends a
NOTIFY
request to a
slave until
timeout.
FAIL
X
X
Link0
130
A master
periodically
sends a
NOTIFY
request to a
slave until
ICMP message
indicating.
FAIL
X
X
Link0
131
A master
periodically
sends a
NOTIFY
request to a
slave until
a NOTIFY
response is
received.
FAIL
X
X
Link0
3.7
132
ANCOUNT=0
and the
answer
section
differs from
the slave's
local data
FAIL
X
X
Link0
133
ANCOUNT>0
and the
answer
section
differs from
the slave's
local data
FAIL
X
X
Link0
3.8
3.9
3.10
134
A slave
ignores a
NOTIFY
request from
a unknown
master for
the zone.
FAIL
X
X
Link0
3.11
3.12
135
A master
receives a
NOTIMP
(unimplemented feature error) message.
FAIL
X
X
Link0
RFC 2181:
Clarifications to the DNS Specification
4.1. UDP
Source
Address
Selection
136
UDP Source
Address
Selection
PASS
X
X
Link0
4.2. Port
Number
Selection
137
Port number
selection
PASS
X
X
Link0
5. Resource
Record Sets
5.1 Sending
RRs from an
RRSet
138
Sending RRs
from an
RRSet
PASS
X
X
Link0
5.2. TTLs of
RRs in an
RRSet
139
TTLs of all
RRs in an
RRSet must
be the same
PASS
X
X
Link0
140
Treat
Differing
TTLs from
non-authoritative source as error
FAIL
X
X
Link0
141
Differing
TTLs from
non-authoritative source
FAIL
X
X
Link0
142
Differing
TTLs from
authoritative source
PASS
X
X
Link0
5.3. DNSSEC
Special
Cases
5.4.
Receiving
RRSets
143
Never merge
RRs from
response
with RRs in
cache
FAIL
X
X
Link0
144
Update the
TTL in cache
with the TTL
of the
received
answer
FAIL
X
X
Link0
5.4.1.
Ranking data
145
Server makes
a judgment
by the
reliability
of data
(Data from
the answer
section of
an
authoritative answer v.s. Data from the authority section of an authoritative answer)
PASS
X
X
Link0
146
Server makes
a judgment
by the
reliability
of data
(Data from
the answer
section of
an
authoritative answer v.s. Non-authoritative data from the answer section of an authoritative answer)
PASS
X
X
Link0
147
Server makes
a judgment
by the
reliability
of data
(Data from
the answer
section of
an
authoritative answer v.s. Data from the additional section of an authoritative answer)
FAIL
X
X
Link0
148
Server makes
a judgment
by the
reliability
of data
(Data from
the
authority
section of
an
authoritative answer v.s. Data from the answer section of a non-authoritative answer)
FAIL
X
X
Link0
149
Server makes
a judgment
by the
reliability
of data
(Data from
the
authority
section of
an
authoritative answer v.s. Data from the authority section of a non-authoritative answer)
PASS
X
X
Link0
150
Server makes
a judgment
by the
reliability
of data
(Data from
the answer
section of
an
non-authoritative answer v.s. Data from the additional section of a authoritative answer)
PASS
X
X
Link0
151
Least
reliability
data should
not return
as answer
(Additional
section from
an
authoritative answer)
no test
sequence
X
X
Link0
152
Least
reliability
data should
not return
as answer
(Authority
section from
a
non-authoritative answer)
FAIL
X
X
Link0
153
Least
reliability
data should
not return
as answer
(Additional
section from
a
non-authoritative answer)
PASS
X
X
Link0
5.5. Sending
RRSets
(reprise)
154
A Resource
Record Set
should only
be included
once in any
DNS reply
PASS
X
X
Link0
6. Zone Cuts
6.1. Zone
Authority
155
A server for
a zone
should not
return
authoritative answer for queries related to names in another name
PASS
X
X
Link0
6.2. DNSSEC
issues
7. SOA RRs
7.1.
Placement of
SOA RRs in
authoritative answers
156
SOA records
are to be
placed in
the
authority
section
PASS
X
X
Link0
8. Time to
Live (TTL)
157
Time to live
PASS
X
X
Link0
158
Received
with the
most
significant
bit is set
FAIL
X
X
Link0
9. The TC
(truncated)
header bit
159
Case of the
TC header
bit is not
set
PASS
X
X
Link0
10. Naming
issues
10.1. CNAME
resource
records
10.2. PTR
records
160
RRSet for
PTR record
PASS
X
X
Link0
RFC 2308:
DNS NCACHE
2. Negative
Response
2.1. Name
Error
161
Name error
(RCODE=NXDOMAIN)
PASS
X
X
Link0
2.1.1.
Special
Handling of
Name Error
2.2. No Data
162
No Data
PASS
X
X
Link0
3. Negative
Answers from
Authoritative Servers
(Related to
DNSSEC)
4. SOA
Minimum
Field
5. Caching
Negative
Answers
163
TTL expired
negative
cache MUST
NOT be used
(NXDOMAIN)
PASS
X
X
Link0
164
TTL expired
negative
cache MUST
NOT be used
(NODATA)
PASS
X
X
Link0
165
Caching of
name error
(NXDOMAIN)
PASS
X
X
Link0
166
Caching of
name error
(NXDOMAIN)
for query
tuple
PASS
X
X
Link0
167
Caching of
no data
(NODATA)
PASS
X
X
Link0
168
Caching of
no data
(NODATA) for
query tuple
PASS
X
X
Link0
NXT record
is stored
(Related to
DNSSEC)
NXT record
has the same
owner name
(Related to
DNSSEC)
169
Negative
responses
without SOA
records
FAIL
X
X
Link0
6. Negative
answers from
the cache
NXT record
is added to
the
authority
section
(Related to
DNSSEC)
SIG record
is added to
the
authority
section
(Related to
DNSSEC)
170
Negative
answer
should have
an implicit
referral
built into
the answer
(NXDOMAIN)
FAIL
X
X
Link0
171
Negative
answer
should have
an implicit
referral
built into
the answer
(NODATA)
FAIL
X
X
Link0
7. Other
Negative
Responses
7.1. Server
Failure
(OPTIONAL)
172
Resolver
cache a
server
failure
response
PASS
X
X
Link0
173
Resolver
cache a
server
failure
response for
query tuple
PASS
X
X
Link0
174
Limit of
time (5
minutes) for
caching
(Server
Failure)
PASS
X
X
Link0
7.2. Dead /
Unreachable
Server
(OPTIONAL)
175
Caching of
dead server
indication
PASS
X
X
Link0
176
Caching of
dead server
indication
for query
tuple
PASS
X
X
Link0
177
Limit of
time (5
minutes) for
caching
(Dead/Unreachable Server)
PASS
X
X
Link0
8. Changes
from RFC1034
Resolver
cache a
server
failure
response
(Tested at
7.1. Server
Failure)
178
Caching of
SOA record
PASS
X
X
Link0
Caching of
name error
(NXDOMAIN)
(Tested at
5. Caching
Negative
Answers)
Caching of
no data
(NODATA)
(Tested at
5. Caching
Negative
Answers)
Negative
answers from
the cache
(Tested at
6. Negative
answers from
the cache)
$TTL
directive
define
default TTL
(Tested at
4. SOA
Minimum
Field)
RFC 2671:
Extension
Mechanisms
for DNS
(EDNS0)
4. OPT
pseudo-RR
179
OPT
pseudo-RR
FAIL
X
X
Link0
180
OPT
pseudo-RR
(recursive)
FAIL
X
X
Link0
5. Transport
Consideration
5.1.
181
The presence
of an OPT
pseuduo-RR
FAIL
X
X
Link0
5.2.
182
The lack of
an OPT
pseuduo-RR
FAIL
X
X
Link0
5.3.
183
Responders
don't
understand
OPT RR
FAIL
X
X
Link0
RFC 2782:
DNS SRV RR
184
SRV type
FAIL
X
X
Link0
185
SRV resource
record
FAIL
X
X
Link0
RFC 3401:
DDDS - The
Comprehensive DDDS
RFC 3402:
DDDS - The
Algorithm
RFC 3403:
DDDS DNS
Database
RFC 3404:
DDDS Based
URI
Resolution
RFC 3405:
URI.ARPA
Assignment
Procedures
RFC3401 Part
One: The
Comprehensive DDDS
RFC3402 Part
Two: The
Algorithm
RFC3403 Part
Three: The
Domain Name
System (DNS)
Database
4. NAPTR RR
Format
4.1 Packet
Format
186
NAPTR type
FAIL
X
X
Link0
187
Caching
NAPTR
resource
record
FAIL
X
X
Link0
188
NAPTR
resource
record
FAIL
X
X
Link0
189
Multiple
NAPTR
resource
records with
several
ORDER and
PREFERENCE
FAIL
X
X
Link0
190
Invalid
NAPTR
resource
record
format
FAIL
X
X
Link0
RFC3404 Part
Four: The
Uniform
Resource
Identifiers
(URI)
Resolution
Application
4. The URI
and URN
Resolution
Application
Specifications
4.3 Flags
191
Flag in
NAPTR
resource
record
(empty)
FAIL
X
X
Link0
192
Flag in
NAPTR
resource
record (P
flag)
FAIL
X
X
Link0
193
Flag in
NAPTR
resource
record (A
flag)
FAIL
X
X
Link0
194
Flag in
NAPTR
resource
record (S
flag)
FAIL
X
X
Link0
195
Multiple
Flags in
NAPTR
resource
record (X,Y
flag)
FAIL
X
X
Link0
4.5 Valid
Databases
196
Additional
Section
Processing
for NAPTR
resource
record (A
flag)
FAIL
X
X
Link0
197
Additional
Section
Processing
for NAPTR
resource
record (S
flag)
FAIL
X
X
Link0
RFC3405 Part
Five:
URI.ARPA
Assignment
Procedures
RFC 3425:
Obsoleting
IQUERY
3 - Effect
on RFC 1035
198
Returning
Not
Implemented
error
FAIL
X
X
Link0
RFC 3596:
DNS
Extensions
to Support
IPv6
2. New
resource
record
definition
and domain
2.1. AAAA
record type
2.2. AAAA
data format
2.3. AAAA
query
199
AAAA type
FAIL
X
X
Link0
200
AAAA
resource
record
FAIL
X
X
Link0
2.4. Textual
format of
AAAA records
2.5.
IP6.ARPA
Domain
201
PTR type
FAIL
X
X
Link0
202
PTR resource
data
FAIL
X
X
Link0
Regards,
Zhiyong Wu