Þ•×"h-Ti-—¾-sV.oÊ.&:/Ša/€ì/^m0ZÌ0*'1,R1-101mÞ1?L2Œ2<™23Ö2& 3+13O]3X3O4XV45¯4Jå4J056{56²5@é5/*6+Z68†6A¿6B7$D7Hi7b²7‡8‡8Y%990œ9wÍ9 E:8f:dŸ:\;da;#Æ;/ê;#<&><†e<†ì<ks=Nß=7.>~f>~å>cd?xÈ?xA@/º@Jê@‰5AŠ¿AŽJB›ÙB°uC3&D%ZD.€DZ¯D‹ E‹–Ep"Fƒ“FƒGh›G}H}‚HIHŽIK×IH#JlJ/îJxK„—K*L>GLN†LKÕLJ!MlM‹ME¡M-çMN;2NnN(îN1OIOfO†wOþO±P²ÏP@‚Q*ÃQ1îQ7 R6XRR¨R#ÄR(èR(SD:S/S@¯SðS@TXET=žTCÜTD U:eU7 UMØU3&V7ZVM’V3àV8WMWYûW_UXaµXWYPoYRÀYSZ^gZpÆZ;7[Ls[À[-Ñ[,ÿ[5,\b\"u\4˜\0Í\þ\[]l]`‹]aì]WN^X¦^.ÿ^9._!h_RŠ_SÝ_1`^D`_£`=aIAa4‹aVÀa;bCSb—b.²báb)þbJ(cVsc=Êc=d,Fd€sd&ôd:e'VeU~eGÔe/fDLf]‘fGïfZ7gS’g æg:hPBhP“hQähQ6iOˆi8Øi8j9Jj9„j9¾j9øj>2k#qk=•kÓk"òkDlRZlPl3þlY2mYŒm[æm[BnvžnvowŒowp\|pTÙpT.qUƒqUÙqL/rA|r4¾r+ór'sDGs6Œs]Ãs9!t8[t}”t%u68u,ou,œu(Éu4òu'v?v$Vv9{v/µv0åv-w7Dw.|w*«wEÖw9xnVxlÅxZ2y`ycîyRzHmzM¶zG{EL{g’{Aú{J<|Ó‡|)[};…}<Á}-þ}?,~‡l~”ô~„‰‘€L €qí€p_zÐ{K‚jÇ‚62ƒ<iƒS¦ƒIúƒHD„8„3Æ„*ú„4%…Z…’u…S†P\††eÉ†W/‡T‡‡EÜ‡I"ˆlˆhˆˆOñˆVA‰N˜‰ç‰ Šb$ŠP‡ŠØŠ%X‹9~‹¸‹hÎ‹G7ŒIŒNÉŒ>aW?¹`ùaZŽ:¼Ž{÷Žs‰¤ÂÙïCGGŠ‘G1‘Hy‘HÂ‘ž’>ª’é’ú’“)0“&Z“)“«“!Ë“í“ ”X”Vx” Ï”ð”>•N•ˆm•¡ö•˜–_(—™ˆ—º"˜…Ý˜ƒc™ƒç™„kš™ðš‹Š›[œ•rœ¶¿”Až”ÖžakŸuÍŸšC Þ }^¡‰Ü¡¡f¢ £œ©£‘F¤|Ø¤«U¥¡¦’£¦¨6§„ß§‡d¨ì¨n|©pë©’\ª†ïª”v«¢¬‡®¬n6x¥;®Z®-ø®e&¯vŒ¯o°ts°wè°p`±uÑ±8G²\€²TÝ²g2³žš³y9´¨³´ž\µjûµ.f¶>•¶*Ô¶>ÿ¶$>·5c·q™·|¸]ˆ¸]æ¸QD¹Q–¹–è¹xºhøºa»‡ï»ew¼»Ý¼²™½ŸL¾xì¾ªe¿^À‘oÀcÁVeÁQ¼ÁKÂMZÂ4¨ÂrÝÂjPÃZ»ÃcÄ}zÄrøÄ`kÅÌÅf]ÆjÄÆ¥/Ç‡ÕÇ{]ÈžÙÈŒxÉAÊ GÊChÊ;¬ÊHèÊh1ËfšËkÌlmÌlÚÌUGÍVÍôÍgÎAzÎB¼Î3ÿÎ03Ï?dÏ•¤Ï|:Ð·Ð‡HÑÐÑèÑvüÑ“sÒ†Ó‡ŽÓnÔ]…ÔCãÔ]'Õy…ÕDÿÕLDÖR‘Ö9äÖE×d×du×jÚ×REØ(˜ØUÁØJÙ,bÙ(Ù3¸Ù1ìÙÚ5ÚFÚ)SÚ#}Ú¡Úh¹Úa"ÛM„ÛÒÛfRÜi¹Üa#Ýp…ÝqöÝ#hÞßŒÞJlßŸ·ß|WàxÔà0Mám~ájìáaWâ]¹â<ã)Tã)~ã/¨ãwØã8Pä‰ä<–äDÓä4å;MåN‰å`ØåN9æ`ˆæ:éæ;$ç;`çPœç9íçU'è*}è&¨èJÏèWéXré!ËéIíéÍ7ê’ë’˜ëY+ì…ìR¥ìuøì%níB”í\×íR4î\‡îJäîP/ï6€ï.·ï“æï¥zðœ ñk½ñ`)òŽŠòŽó}¨ó‚&ô‚©ô5,õXbõÐ»õ×ŒöÜd÷ÍAøÎùIÞù8(ú=aú^Ÿú¦þú¦¥ûLüêüzý… þƒþƒÿ•˜ÿQ.S€jÔ}?;½wù}q!ï;qM ¿~`#ßAM\!ª_Ì“,(ÀFé#0Ti!úØÓõCÉ + 29 6l :£ #Þ #'&=N&Œd³/FHD£bèBK \Ž _ë FKC’@Ö;CS@—;Ø.úCV>V•UìKBSŽOâP2RƒÖDXW6õG,Ot7Ä(ü2%/X.ˆ·`Ó4McÏP3Q„6Ö* 8aWb¹ h=a¦<?E/…[µ3>E&„/«Û2ø^+`Š6ë6"-Y|‡(?-0m‡žM& 8t X –![!~ù!^x"#×"Bû"H>#H‡#IÐ#I$`d$8Å$8þ$97%9q%@«%@ì%=-&/k&c›&,ÿ&/,'J\'Q§'\ù'6V(c(cñ(eU)e»)!*€¯*Ž0+¿+`A,d¢,d-el-eÒ-M8.B†.8É.;/)>/Yh/;Â/eþ/Gd09¬0gæ0(N1<w1*´1*ß1% 2,02]2v2'•2>½2<ü2>935x37®36æ374IU4?Ÿ4Oß4”/5~Ä5gC6j«6!7L87Q…7D×7R8Uo8PÅ8I9ù`91Z:fŒ:Nó:/B;Ir;¥¼;°b<¢=¶=Sd>Š¸>C?™Ñ?˜k@ŒAO‘ALáAm.BSœBNðB:?C:zC8µC0îCD¯?DVïD[FE-¢EuÐEZFFY¡F(ûF)$G NGzoG_êG[JHV¦HýH Iv9IU°IzJ*J6¬JãJŠýJPˆKJÙK^$LEƒLoÉLJ9Mn„MóMDsN‰¸NBO*\O‡O(¢OËOäO]ûOTYP—®P#FQMjQN¸QORjWRCÂRSS7S3SS1‡S8¹S!òS'T c¦Øcªd¦*e¢Ñertf´çfªœgšGhºâh“i‰1j•»j•Qk‘çk®yl´(mÆÝmÄ¤nÅioÁ/pØñp3Êq¢þq2¡r`Ôrˆ5sn¾sx-tv¦tpuyŽu8v^AvK vdìv£Qwoõw±ex§yf¿y-&zETz4šz8Ïz"{;+{~g{~æ{Le|L²|Nÿ|NN}}j;~e¦~‡•”X*€¯ƒ€¦3¢Úd}‚±â‚Y”ƒ}îƒMl„Aº„@ü„H=…U†…/Ü…W†Xd†`½†k‡‡Š‡yˆ`Œˆ‘íˆg‰iç‰¡QŠ„óŠ|x‹¤õ‹šŒ>+!j>Œ9ËNŽ~TŽ…ÓŽ‚YÜt\oÑ[A‘‘e¸‘?’@^’3Ÿ’;Ó’K“«[“|”“„”Š•£•Ã•mÞ•–L–œã–Œ€—g ˜lu˜8â˜n™ŒŠ™hšR€šYÓš<-›Kj›¶›`Í›j.œh™œ1_4P”Xå2>ž0qž5¢ž&ØžÿžŸ<+Ÿ:hŸ£Ÿq¾Ÿl0 _ šý g˜¡‚¢gƒ¢pë¢q\£Î£éè·DòèC‘+;$Á5ù¯ú¸?ì¦ðz ˜6òÜwWÛÔL<¢ûÂÙ`'åËkÿ>Hyq£0X^×™¤,º½÷3øJ]œN¡~?QG¿-jm)ÁÏ²µöÃŒÔiýí4wêŠ“e@|î¢vU–ˆâƒì°%Rc’½»ÇÑØ®id97oA"¾FRÍtã«—9}ÎzÞ/("°ñm‰±ÖV>b¹.2j<æNhsÑÀ¤Àg‡IçS»œK„´uÞÚŽ¥T]qƒ€¨©ÛM™ÏórOî_sBA€.ú!ö&¨tY‡1yvf‹0Be§fZ§Ck«!³Eõß;6Ì-Ø ¿ïŽªVáþ”Ã‚æ“D[Ç}¬¦åxÅÊ®\Ý„†õ_Ó8) Î¥áQ¶š·,Ð4óŠë ÷ÆM'gÜ GF‚Ä†ž È/ Õl%Â³Ÿ\…Éž3: Y{ß›•@Ed¼àˆl$ë{ZËüÖýêOÌªPÚ ÒñŒSÝnÐJ¯^¼£#ÆXÓŸÄW~ÒôUÅ&ÿüTé…Íu:‰K2¶aÕ` p˜ð±ç ôà[(µÊ´”•É‹¹|ä7brLí²Ù¬×›* H¾©8¸cûpx#5n1+‘þïã–Pâ Èaä¡’=—*øhoùIš=º"{domain_child}" does not exist as a DNS zone. Try to test "{domain_super}" instead."{domain_child}" is not a zone. It is an alias for "{domain_target}". Run a test for "{domain_target}" instead. Returned from name servers "{ns_list}".A CDNSKEY RRset exists, but no DNSKEY record exists. Fetched from the nameservers with IP addresses "{ns_ip_list}".A CDS RRset exists, but no DNSKEY record exists. Fetched from the nameservers with IP addresses "{ns_ip_list}".A name server should not be a recursorA non-null SPF policy was found on {domain}, although this type of domain (root, TLD or under .ARPA) is not expected to be used for email.A null SPF policy was found on {domain}, which is a type of domain (root, TLD or under .ARPA) not expected to be used for email.A single "delete" CDNSKEY record is found on the nameservers with IP addresses "{ns_ip_list}".A single "delete" CDS record is found on the nameservers with IP addresses "{ns_ip_list}".A single NS set was found ({nsname_list}).A single SOA mname value was seen ({mname}).A single SOA rname value was found ({rname}).A single SOA serial number was found ({serial}).A single SOA time parameter set was seen (REFRESH={refresh},RETRY={retry},EXPIRE={expire},MINIMUM={minimum}).A unique SOA record is returned by all nameservers of the zone.AS DiversityAS database returned no informations for IP address {ns_ip}.ASN Database error. No data to analyze for {ns_ip}.AXFR not available on nameserver {ns}.All DNSKEY algorithms used to sign the zoneAll authoritative nameservers have their IPv4 addresses in the same AS ({asn}).All authoritative nameservers have their IPv4 addresses in the same AS set ({asn_list}).All authoritative nameservers have their IPv6 addresses in the same AS ({asn}).All authoritative nameservers have their IPv6 addresses in the same AS set ({asn_list}).All keys from the DNSKEY RRset have the correct size.All name server(s) IPv4 address(es) are announced in the same IPv4 prefix.All name server(s) IPv6 address(es) are announced in the same IPv6 prefix.All nameservers reply with same IP used to query them.All nameservers succeeded to resolve to an IP address.All of the nameserver names are listed both at parent and child.All servers do not have the same CDNSKEY RRset.All servers do not have the same CDS RRset.All the IP addresses used by the nameservers are unique.All the IP addresses used by the nameservers in child are unique.All the IP addresses used by the nameservers in parent are unique.All the nameservers have SOA record.All these nameservers are confirmed to be authoritative : {nsname_list}.Ambiguous downcasing of character "{unicode_name}" in the domain name. Use all lower case instead.At least two IPv4 addresses of the authoritative nameservers are announced by different AS sets. A merged list of all AS: ({asn_list}).At least two IPv6 addresses of the authoritative nameservers are announced by different AS sets. A merged list of all AS: ({asn_list}).Authoritative answer on SOA query for "{domain}" is returned by name servers "{ns_list}".Behaviour against AAAA queryBig packet size ({size}) (try with "{command}").Both CDS and CDNSKEY RRsets are found on nameservers that resolve to IP addresses ({ns_ip_list}) but they do not match.Both IPv4 and IPv6 are disabled.Broken response from name server "{ns}" on an SOA query.CDNSKEY RRset is found on nameservers that resolve to IP addresses ({ns_ip_list}), but no CDS RRset.CDNSKEY and CDS RRsets are found on nameservers that resolve to IP addresses ({ns_ip_list}).CDS RRset is found on nameservers that resolve to IP addresses ({ns_ip_list}), but no CDNSKEY RRset.Check for invalid DNSKEY algorithmsCheck for too short or too long RRSIG lifetimesCheck for valid RSA DNSKEY key sizeChecking for revealed software versionChild does not list enough ({count}) nameservers that resolve to IPv4 addresses. Lower limit set to {minimum}. Name servers: {ns_list}Child does not list enough ({count}) nameservers that resolve to IPv6 addresses. Lower limit set to {minimum}. Name servers: {ns_list}Child does not list enough ({count}) nameservers. Lower limit set to {minimum}. Name servers: {nsname_list}Child has extra nameserver IP address(es) not listed at parent ({ns_ip_list}).Child has nameserver(s) not listed at parent ({extra}).Child lists enough ({count}) nameservers that resolve to IPv4 addresses. Lower limit set to {minimum}. Name servers: {ns_list}Child lists enough ({count}) nameservers that resolve to IPv6 addresses. Lower limit set to {minimum}. Name servers: {ns_list}Child lists enough ({count}) nameservers. Lower limit set to {minimum}. Name servers: {nsname_list}Child lists no nameserver that resolves to an IPv4 address. If any were present, the minimum allowed would be {minimum}.Child lists no nameserver that resolves to an IPv6 address. If any were present, the minimum allowed would be {minimum}.Consistency between glue and authoritative dataDNS query to {ns} for {domain}/{type}/{class} failed with error: {message}DNSKEY with tag {keytag} and using algorithm {algo_num} ({algo_descr}) has a size ({keysize}) larger than the maximum one ({keysizemax}).DNSKEY with tag {keytag} and using algorithm {algo_num} ({algo_descr}) has a size ({keysize}) smaller than the minimum one ({keysizemin}).DNSKEY with tag {keytag} and using algorithm {algo_num} ({algo_descr}) has a size ({keysize}) smaller than the recommended one ({keysizerec}).DNSKEY with tag {keytag} uses unsupported algorithm {algo_num} ({algo_mnemo}) by this installation of Zonemaster. Fetched from name servers "{ns_ip_list}".DNSKEY with tag {keytag} uses unsupported algorithm {algo_num} ({algo_mnemo}) by this installation of Zonemaster. Fetched from the nameservers with IP addresses "{ns_ip_list}".DNSSEC signed zone and DS in parent for signed zoneDS in delegation requires signed zoneDS must match a valid DNSKEY in the child zoneDS record for the child zone found on parent nameservers with IP addresses "{ns_ip_list}".Delegation does not list enough ({count}) nameservers that resolve to IPv4 addresses. Lower limit set to {minimum}. Name servers: {ns_list}Delegation does not list enough ({count}) nameservers that resolve to IPv6 addresses. Lower limit set to {minimum}. Name servers: {ns_list}Delegation does not list enough ({count}) nameservers. Lower limit set to {minimum}. Name servers: {nsname_list}Delegation lists enough ({count}) nameservers that resolve to IPv4 addresses. Lower limit set to {minimum}. Name servers: {ns_list}Delegation lists enough ({count}) nameservers that resolve to IPv6 addresses. Lower limit set to {minimum}. Name servers: {ns_list}Delegation lists enough ({count}) nameservers. Lower limit set to {minimum}. Name servers: {nsname_list}Delegation lists no nameserver that resolves to an IPv4 address. If any were present, the minimum allowed would be {minimum}.Delegation lists no nameserver that resolves to an IPv6 address. If any were present, the minimum allowed would be {minimum}.Difference between the smaller serial ({serial_min}) and the bigger one ({serial_max}) is greater than the maximum allowed ({max_variation}).Domain name ({domain}) has a label ({label}) ending with a hyphen ('-').Domain name ({domain}) has a label ({label}) starting with an hyphen ('-').Domain name ({domain}) has a label ({label}) too long ({dlength}/{max}).Domain name ({domain}) has a label ({label}) with a double hyphen ('--') in position 3 and 4 (with a prefix which is not 'xn--').Domain name ({domain}) has a zero-length label.Domain name ({domain}) has no label with a double hyphen ('--') in position 3 and 4 (with a prefix which is not 'xn--').Domain name MX ({domain}) has a label ({label}) with a double hyphen ('--') in position 3 and 4 (with a prefix which is not 'xn--').Domain name MX ({domain}) syntax is valid.Domain name MX ({domain}) within a 'numeric only' TLD ({tld}).Domain name has a label that is too long (more than 63 characters), "{label}".Domain name has a non-ASCII label ("{label}") which is not a valid U-label.Domain name has an ASCII label ("{label}") with a character not permitted.Domain name has repeated dots.Domain name is empty.Domain name is too long (more than 253 characters with no final dot).Domain name is too long ({fqdnlength}/{max}).Domain name starts with dot.Empty NOERROR response to SOA query was received from {ns}.Erroneous RCODE ("{rcode}") in response to an EDNS version 1 query. Fetched from the nameservers with IP addresses {ns_ip_list}Erroneous response from nameserver {ns}.Every reverse DNS entry matches name server name.Existence of CDS and CDNSKEYExistence of SOAExpected RCODE but received erroneous response to an EDNS version 1 query. Fetched from the nameservers with IP addresses {ns_ip_list}Fatal error in {module}: {msg}Flags field of DNSKEY record with tag {keytag} has not SEP bit set although DS with same tag is present in parent. Fetched from the nameservers with IP addresses "{ns_ip_list}".Flags field of DNSKEY record with tag {keytag} has not ZONE bit set although DS with same tag is present in parent. Fetched from the nameservers with IP addresses "{ns_ip_list}".Found SOA rname {rname} on following nameserver set : {ns_list}.Found illegal characters in MX ({domain}).Found illegal characters in SOA MNAME ({domain}).Found illegal characters in the domain name ({domain}).Found illegal characters in the nameserver ({domain}).Found {count} NS set(s).Found {count} SOA rname(s).Found {count} SOA serial number(s).Found {count} SOA time parameter set(s).Fully qualified master nameserver in SOAFunctional nameserver found. "A" query for www.{zname} test skipped.Globally reachable IP address(es): "{ns_list}".Glue records are consistent between glue and authoritative data.IP Prefix DiversityIP address(es) intended for documentation purposes: "{ns_list}".IP address(es) intended for local use on network or service provider level: "{ns_list}".IP address(es) not listed as globally reachable: "{ns_list}".IP {ns_ip} in child refers to multiple nameservers ({nsname_list}).IP {ns_ip} in parent refers to multiple nameservers ({nsname_list}).IP {ns_ip} refers to multiple nameservers ({nsname_list}).IPv4 is disabled, not sending "{rrtype}" query to {ns}.IPv4 is disabled. No DNS queries are sent to these name servers: "{ns_list}".IPv4 is enabled, can send "{rrtype}" query to {ns}.IPv6 is disabled, not sending "{rrtype}" query to {ns}.IPv6 is disabled. No DNS queries are sent to these name servers: "{ns_list}".IPv6 is enabled, can send "{rrtype}" query to {ns}.Illegal character(s) found in SOA RNAME field ({rname}).In-bailiwick name server listed at parent has a mismatch between glue data at parent ({parent_addresses}) and any equivalent address record in child zone ({zone_addresses}).Inconsistent NSEC3 flag list in responses for the child zone from different name servers.Inconsistent NSEC3 iteration value in responses for the child zone from different name servers.Inconsistent hash algorithm in NSEC3 in responses for the child zone from different name servers.Inconsistent responses from name servers. Some include signed responses, others do not.Inconsistent responses from parent name servers. Some include DS, others do not.Inconsistent responses from zone with NSEC. Fetched from name servers "{ns_list}".Inconsistent responses from zone with NSEC3. Fetched from name servers "{ns_list}".Inconsistent salt length in NSEC3 in responses for the child zone from different name servers.Incorrect version of EDNS (expected 0) in response from {ns} on query with EDNS (version 0) asking for {domain}.It cannot be determined if the child zone is signed or not.It cannot be determined if the parent zone has DS for the child zone or not.Lame delegation.Legal values for the DS hash digest algorithmLogger callback died with error: {exception}MX RRset was returned by name servers "{ns_ip_list}".MX is not an aliasMX name must have a valid hostnameMX record for the domain is not pointing to a CNAME.MX record for the domain is pointing to a CNAME.MX record presentMail targets in the MX RRset "{mailtarget_list}" returned from name servers "{ns_ip_list}".Minimum number of name serversMissing RRSIG (signature) for the NSEC record or records. Fetched from name servers "{ns_list}".Missing RRSIG (signature) for the NSEC3 record or records. Fetched from name servers "{ns_list}".Missing SOA record in NODATA response with NSEC. Fetched from name servers "{ns_list}".Missing SOA record in NODATA response with NSEC3. Fetched from name servers "{ns_list}".Misuse of '@' character in the SOA RNAME fieldMisused '@' character found in SOA RNAME field ({rname}).Module {module} finished running.Multiple NSEC records when one is expected. Fetched from name servers "{ns_list}".Multiple NSEC3 records when one is expected. Fetched from name servers "{ns_list}".NS can be resolvedNSEC record for the zone apex with incorrect type list. Fetched from name servers "{ns_list}".NSEC3 record for the zone apex with incorrect type list. Fetched from name servers "{ns_list}".Name server "{nsname}" cannot be resolved into an IP address.Name server "{ns}" does not give an authoritative answer on an SOA query.Name server "{ns}" does not respond to an SOA query.Name server "{ns}" responds with an unexpected RCODE name ("{rcode}") on an SOA query.Name server IP address "{ns_ip}" is announced by ASN {asn}.Name server IP address "{ns_ip}" is announced in prefix "{prefix}".Name server NS consistencyName server address must be globally reachableName server is authoritativeName server must not point at CNAME aliasName server {ns} not adding fake delegation for domain {domain} to itself.Name servers for the child zone are inconsistent on whether the zone is signed or not.Name servers have IPv4 addresses in the following ASs: {asn}.Name servers have IPv6 addresses in the following ASs: {asn}.Name servers must have distinct IP addressesNameserver ({domain}) has a label ({label}) with a double hyphen ('--') in position 3 and 4 (with a prefix which is not 'xn--').Nameserver ({domain}) syntax is valid.Nameserver ({domain}) within a 'numeric only' TLD ({tld}).Nameserver {nsname} RR points to CNAME.Nameserver {nsname} has an IP address ({ns_ip}) with mismatched PTR result ({names}).Nameserver {nsname} has an IP address ({ns_ip}) without PTR configured.Nameserver {ns} allow zone transfer using AXFR.Nameserver {ns} answered A query with an unexpected rcode ({rcode}).Nameserver {ns} answered AAAA query with an unexpected RDATA length ({length} instead of 16).Nameserver {ns} answered AAAA query with an unexpected rcode ({rcode}).Nameserver {ns} answered query for name {query_name} and type {rrtype} with RCODE {rcode}.Nameserver {ns} did not respond to a query for name {query_name} and type {rrtype}.Nameserver {ns} did not respond.Nameserver {ns} did not return "A" record(s) for {domain}.Nameserver {ns} does not give an authoritative response on an NS query over TCP.Nameserver {ns} does not give an authoritative response on an NS query over UDP.Nameserver {ns} does not give an authoritative response on an SOA query over TCP.Nameserver {ns} does not give an authoritative response on an SOA query over UDP.Nameserver {ns} does not preserve original case of the queried name ({domain}).Nameserver {ns} does not respond to NS queries over TCP.Nameserver {ns} does not respond to NS queries over UDP.Nameserver {ns} does not respond to SOA queries over TCP.Nameserver {ns} does not respond to SOA queries over UDP.Nameserver {ns} does not respond to any queries over TCP.Nameserver {ns} does not respond to any queries over UDP.Nameserver {ns} does not support EDNS0 (replies with FORMERR).Nameserver {ns} dropped AAAA query.Nameserver {ns} has one or more unknown EDNS Z flag bits set.Nameserver {ns} is a recursor.Nameserver {ns} is not a recursor.Nameserver {ns} preserves original case of queried names ({domain}).Nameserver {ns} replies on a SOA query with a different source address ({source}).Nameserver {ns} replies on an EDNS query with a truncated response without EDNS.Nameserver {ns} responded with no DNSKEY record(s).Nameserver {ns} responds to a NS query with no NS records in the answer section over TCP.Nameserver {ns} responds to a NS query with no NS records in the answer section over UDP.Nameserver {ns} responds to a SOA query with no SOA records in the answer section over TCP.Nameserver {ns} responds to a SOA query with no SOA records in the answer section over UDP.Nameserver {ns} responds with a wrong owner name ({domain_found} instead of {domain_expected}) on NS queries over TCP.Nameserver {ns} responds with a wrong owner name ({domain_found} instead of {domain_expected}) on NS queries over UDP.Nameserver {ns} responds with a wrong owner name ({domain_found} instead of {domain_expected}) on SOA queries over TCP.Nameserver {ns} responds with a wrong owner name ({domain_found} instead of {domain_expected}) on SOA queries over UDP.Nameserver {ns} responds with a wrong owner name ({owner} instead of {name}) on SOA queries.Nameserver {ns} responds with an unexpected RCODE ({rcode}) on an NS query over TCP.Nameserver {ns} responds with an unexpected RCODE ({rcode}) on an NS query over UDP.Nameserver {ns} responds with an unexpected RCODE ({rcode}) on an SOA query over TCP.Nameserver {ns} responds with an unexpected RCODE ({rcode}) on an SOA query over UDP.Nameserver {ns} responds with multiple ({count}) SOA records on SOA queries.Nameserver {ns} response is not authoritative on {proto} port 53.Nameserver {ns} returned "A" record(s) for {domain}.Nameserver {ns} returns an upward referral.Nameservers did not respond to A query.Neither end of any label in the domain name ({domain}) has a hyphen.No CDS or CDNSKEY RRsets are found on any name server.No DS record for the child zone found on parent nameservers with IP addresses "{ns_ip_list}".No IP address found for SOA 'mname' nameserver ({mname}).No MX RRset was returned by name servers "{ns_ip_list}".No SPF policy was found for {domain}, which is a type of domain (root, TLD or under .ARPA) not expected to be used for email.No SPF policy was found for {domain}.No hyphen ('-') at the start or end of the domain nameNo illegal characters in the SOA MNAME fieldNo illegal characters in the SOA RNAME fieldNo illegal characters in the domain nameNo illegal characters in the domain name ({domain}).No multiple SOA recordsNo name servers found.No nameserver points to CNAME alias.No nameserver was successfully resolved to an IP address.No response from nameserver {ns} on NS queries.No response from nameserver {ns} on SOA queries.No response from nameserver(s) on MX queries.No response from nameserver(s) on PTR query ({domain}).No response from nameserver(s) on SOA queries.No response from {ns} asking for {domain}.No response from {ns} when EDNS is used in query asking for {domain}.No response on MX query from name servers "{ns_ip_list}".No response or error in response from all name servers on the DNSKEY query. Failing name servers: "{ns_list}".No response or error in response from all parent name servers on the DS query. Name servers are "{ns_list}".No response or error in response on query for NSEC. Fetched from name servers "{ns_list}".No response or error in response on query for NSEC3PARAM. Fetched from name servers "{ns_list}".No response to an EDNS version 1 query. Fetched from the nameservers with IP addresses {ns_ip_list}No truncation of referralsNon-authoritative response on MX query from name servers "{ns_ip_list}".None of the following nameservers returns an upward referral : {nsname_list}.None of the name servers IP addresses are listed as globally reachable.None of the nameservers listed at the parent are listed at the child.None of the zoneâ€™s name servers responded with an authoritative response to queries for SPF policies.Not enough data about {domain} was found to be able to run tests.One or more name servers do not publish the same SPF policy as the others.Out-of-bailiwick name server listed at parent with glue record has a mismatch between the glue at the parent ({parent_addresses}) and any equivalent address record found in authoritative zone ({zone_addresses}).Parent glue name records present in childParent has nameserver(s) not listed at the child ({extra}).Parent name servers are inconsistent on the existence of DS.Prefix database error for IP address {ns_ip}.Prefix database returned no information for IP address {ns_ip}.RRSIG with keytag {keytag} and covering type DNSKEY has already expired. Fetched from the nameservers with IP addresses "{ns_ip_list}".RRSIG with keytag {keytag} and covering type DNSKEY has inception date in the future. Fetched from the nameservers with IP addresses "{ns_ip_list}".RRSIG with keytag {keytag} and covering type SOA has already expired. Fetched from the nameservers with IP addresses "{ns_ip_list}".RRSIG with keytag {keytag} and covering type SOA has inception date in the future. Fetched from the nameservers with IP addresses "{ns_ip_list}".RRSIG with keytag {keytag} and covering type(s) {types} expires at : {date}.RRSIG with keytag {keytag} and covering type(s) {types} has a duration of {duration} seconds, which is just fine.RRSIG with keytag {keytag} and covering type(s) {types} has a duration of {duration} seconds, which is too long.RRSIG with keytag {keytag} and covering type(s) {types} has a remaining validity of {duration} seconds, which is too long.RRSIG with keytag {keytag} and covering type(s) {types} has a remaining validity of {duration} seconds, which is too short.RRSIG with keytag {keytag} and covering type(s) {types} has already expired (expiration is: {expiration}).RRSIG(SOA) must be valid and created by a valid DNSKEYRequest to run unknown method {testcase} in module {module}.Request to run {testcase} in unknown module {module}. Known modules: {module_list}.Response from nameserver {ns} on SOA queries does not contain SOA record.Response without EDNS from {ns} on query with EDNS0 asking for {domain}.Reverse DNS entry exists for each Nameserver IP address.Reverse DNS entry exists for name server IP addressReverse DNS entry matches name server nameRoot zone with an unexpected MX RRset (non-Null MX).SOA 'expire' minimum valueSOA 'expire' value ({expire}) is higher than the minimum recommended value ({required_expire}) and not lower than the 'refresh' value ({refresh}).SOA 'expire' value ({expire}) is less than the recommended one ({required_expire}).SOA 'expire' value ({expire}) is lower than the SOA 'refresh' value ({refresh}).SOA 'minimum' maximum valueSOA 'minimum' value ({minimum}) is between the recommended ones ({lowest_minimum}/{highest_minimum}).SOA 'minimum' value ({minimum}) is higher than the recommended one ({highest_minimum}).SOA 'minimum' value ({minimum}) is less than the recommended one ({lowest_minimum}).SOA 'mname' value ({mname}) refers to a NS which is an alias (CNAME).SOA 'mname' value ({mname}) refers to a NS which is not an alias (CNAME).SOA 'refresh' minimum valueSOA 'refresh' value ({refresh}) is at least equal to the minimum recommended value ({required_refresh}).SOA 'refresh' value ({refresh}) is higher than the SOA 'retry' value ({retry}).SOA 'refresh' value ({refresh}) is less than the recommended one ({required_refresh}).SOA 'refresh' value ({refresh}) is lower than the SOA 'retry' value ({retry}).SOA 'retry' at least 1 hourSOA 'retry' lower than 'refresh'SOA 'retry' value ({retry}) is at least equal to the minimum recommended value ({required_retry}).SOA 'retry' value ({retry}) is less than the recommended one ({required_retry}).SOA MNAME ({domain}) has a label ({label}) with a double hyphen ('--') in position 3 and 4 (with a prefix which is not 'xn--').SOA MNAME ({domain}) syntax is valid.SOA MNAME ({domain}) within a 'numeric only' TLD ({tld}).SOA MNAME consistencySOA MNAME is specified as "." which usually means "no server". Fetched from name servers "{ns_ip_list}".SOA MNAME name server "{nsname}" cannot be resolved into an IP address.SOA MNAME name server "{nsname}" is not listed as NS record for the zone.SOA MNAME name server "{nsname}" resolves to a localhost IP address ({ns_ip}).SOA MNAME name server "{ns}" does not respond to an SOA query.SOA MNAME name server "{ns}" gives unexpected RCODE name ("{rcode}") in response to an SOA query.SOA MNAME name server "{ns}" is not authoritative for the zone.SOA MNAME name server "{ns}" responds to an SOA query with no SOA records in the answer section.SOA MNAME name server is "localhost", which is invalid. Fetched from name servers "{ns_ip_list}".SOA MNAME name server(s) "{ns_list}" appears to be master.SOA MNAME name server(s) "{ns_list}" do not have the highest SOA SERIAL (expected "{soaserial}" but got "{soaserial_list}")SOA RNAME consistencySOA master is not an aliasSOA serial number consistencySOA timers consistencySPF policy validationSame source addressSaw NS set ({nsname_list}) on following nameserver set : {servers}.Saw SOA serial number {serial} on following nameserver set : {ns_list}.Saw SOA time parameter set (REFRESH={refresh}, RETRY={retry}, EXPIRE={expire}, MINIMUM={minimum}) on following nameserver set : {ns_list}.Saw {count} SOA mname.Server at {server} sent {keys} DNSKEY records and {sigs} RRSIG records.Server at {server} sent {keys} DNSKEY records, and {sigs} RRSIG records.Signed child zone found on nameservers with IP addresses "{ns_ip_list}".Some name servers do not support DNSSEC or have not been properly configured. DNSKEY cannot be tested on those servers. Fetched from name servers "{ns_list}".Some name servers return an MX RRset while others return none.TCP connectivityTEST_CASE_END {testcase}.TEST_CASE_START {testcase}.Test availability of zone transfer (AXFR)Test for DNSSEC Algorithm CompletenessTest for truncated response on EDNS queryTest for undefined EDNS versionTest for unknown EDNS OPTION-CODETest for unknown EDNS flagsTest of EDNS0 supportTested zone is the root zone, but no undelegated DS has been provided. DS is not tested.Tested zone is undelegated, but no undelegated DS has been provided. DS is not tested.Testing QNAME case insensitivityTesting QNAME case sensitivityThe ASN data for name server IP address "{ns_ip}" is "{data}".The Broken but functional testThe CDNSKEY RRset is a mixture between "delete" record and other records. Fetched from the nameservers with IP addresses "{ns_ip_list}".The CDNSKEY RRset is not signed by the DNSKEY that the CDNSKEY record with tag {keytag} points to. Fetched from the nameservers with IP addresses "{ns_ip_list}".The CDNSKEY RRset is not signed with a DNSKEY record that a DS record points to. Fetched from the nameservers with IP addresses "{ns_ip_list}".The CDNSKEY RRset is not signed. Fetched from the nameservers with IP addresses "{ns_ip_list}".The CDNSKEY RRset is signed by RRSIG with tag {keytag} but that is not in the DNSKEY RRset. Fetched from the nameservers with P addresses "{ns_ip_list}".The CDNSKEY RRset is signed with an RRSIG with tag {keytag}, but the RRSIG does not match the DNSKEY with the same key tag. Fetched from the nameservers with IP addresses "{ns_ip_list}".The CDNSKEY record with tag {keytag} does not match any DNSKEY record. Fetched from the nameservers with IP addresses "{ns_ip_list}".The CDNSKEY record with tag {keytag} has the SEP bit (bit 15) unset. Fetched from the nameservers with IP addresses "{ns_ip_list}".The CDNSKEY record with tag {keytag} has the zone bit (bit 7) unset. Fetched from the nameservers with IP addresses "{ns_ip_list}".The CDS RRset is a mixture between "delete" record and other records. Fetched from the nameservers with IP addresses "{ns_ip_list}".The CDS RRset is not signed by the DNSKEY that the CDS record with tag {keytag} points to. Fetched from the nameservers with IP addresses "{ns_ip_list}".The CDS RRset is not signed with a DNSKEY record that a DS record points to. Fetched from the nameservers with IP addresses "{ns_ip_list}".The CDS RRset is not signed. Fetched from the nameservers with IP addresses "{ns_ip_list}".The CDS RRset is signed by RRSIG with tag {keytag} but that is not in the DNSKEY RRset. Fetched from the nameservers with P addresses "{ns_ip_list}".The CDS RRset is signed with an RRSIG with tag {keytag}, but the RRSIG does not match the DNSKEY with the same key tag. Fetched from the nameservers with IP addresses "{ns_ip_list}".The CDS record with tag {keytag} does not match any DNSKEY record. Fetched from the nameservers with IP addresses "{ns_ip_list}".The CDS record with tag {keytag} matches a DNSKEY record with SEP bit (bit 15) unset. Fetched from the nameservers with IP addresses "{ns_ip_list}".The CDS record with tag {keytag} matches a DNSKEY record with zone bit (bit 7) unset. Fetched from the nameservers with IP addresses "{ns_ip_list}".The DNS response contains an unknown EDNS option-code. Returned from name servers "{ns_ip_list}".The DNS response, on query with unknown EDNS option-code, does not contain any EDNS from name servers "{ns_ip_list}".The DNS response, on query with unknown EDNS option-code, does not contain the expected SOA record in the answer section from name servers "{ns_ip_list}".The DNS response, on query with unknown EDNS option-code, has unexpected RCODE name "{rcode}" from name servers "{ns_ip_list}".The DNS response, on query with unknown EDNS option-code, is unexpectedly not authoritative from name servers "{ns_ip_list}".The DNSKEY RRset has not been signed by any DNSKEY matched by a DS record. Fetched from the nameservers with IP addresses "{ns_ip_list}".The DNSKEY RRset is not signed by algorithm {algo_num} ({algo_mnemo}) present in the DNSKEY RRset. Fetched from the nameservers with IP addresses "{ns_ip_list}".The DNSKEY RRset is not signed by the DNSKEY that the CDNSKEY record with tag {keytag} points to. Fetched from the nameservers with IP addresses "{ns_ip_list}".The DNSKEY RRset is not signed by the DNSKEY that the CDS record with tag {keytag} points to. Fetched from the nameservers with IP addresses "{ns_ip_list}".The DNSKEY RRset is not signed by the DNSKEY with tag {keytag} that the DS record refers to. Fetched from the nameservers with IP "{ns_ip_list}".The DNSKEY RRset is not signed, which is against expectation. Fetched from the nameservers with IP addresses "{ns_ip_list}".The DNSKEY RRset is signed with an RRSIG with tag {keytag} which cannot be validated by the matching DNSKEY. Fetched from the nameservers with IP addresses "{ns_ip_list}".The DNSKEY RRset is signed with an RRSIG with tag {keytag} which does not match any DNSKEY record. Fetched from the nameservers with IP addresses "{ns_ip_list}".The DNSKEY record with tag {keytag} that the DS refers to does not exist in the DNSKEY RRset. Fetched from the nameservers with IP "{ns_ip_list}".The DNSKEY with tag {keytag} uses algorithm number {algo_num} ("{algo_descr}", {algo_mnemo}) which is not meant for zone signing. Fetched from name servers "{ns_list}".The DNSKEY with tag {keytag} uses algorithm number {algo_num} ("{algo_descr}", {algo_mnemo}). Fetched from name servers "{ns_list}".The DNSKEY with tag {keytag} uses algorithm number {algo_num} which is reserved for private use. Fetched from name servers "{ns_list}".The DNSKEY with tag {keytag} uses deprecated algorithm number {algo_num} ("{algo_descr}", {algo_mnemo}). Fetched from name servers "{ns_list}".The DNSKEY with tag {keytag} uses reserved algorithm number {algo_num}. Fetched from name servers "{ns_list}".The DNSKEY with tag {keytag} uses unassigned algorithm number {algo_num}. Fetched from name servers "{ns_list}".The DNSKEY with tag {keytag} uses unrecommended algorithm number {algo_num} ("{algo_descr}", {algo_mnemo}). Fetched from name servers "{ns_list}".The DS record does not match the DNSKEY with tag {keytag} by algorithm or digest. Fetched from the nameservers with IP "{ns_ip_list}".The DS record with keytag {keytag} uses a deprecated digest algorithm {ds_algo_num} ({ds_algo_descr}). Fetched from parent name servers "{ns_list}".The DS record with keytag {keytag} uses a digest algorithm {ds_algo_num} ({ds_algo_descr}) not meant for DS records. Fetched from parent name servers "{ns_list}".The DS record with keytag {keytag} uses a digest algorithm {ds_algo_num} for private use. Fetched from parent name servers "{ns_list}".The DS record with keytag {keytag} uses a reserved digest algorithm {ds_algo_num} on name servers "{ns_list}".The DS record with keytag {keytag} uses an unassigned digest algorithm {ds_algo_num} on parent name servers "{ns_list}".The MX RRset data is inconsistent between the name servers.The NS RRset is not signed by algorithm {algo_num} ({algo_mnemo}) present in the DNSKEY RRset. Fetched from the nameservers with IP addresses "{ns_ip_list}".The NS name must have a valid domain/hostnameThe RRSIG (signature) for the NSEC3 record cannot be verified. Fetched from name servers "{ns_list}".The RRSIG (signature) with tag {keytag} for the NSEC record cannot be verified. Fetched from name servers "{ns_list}".The RRSIG (signature) with tag {keytag} for the NSEC record has expired. Fetched from name servers "{ns_list}".The RRSIG (signature) with tag {keytag} for the NSEC record it not yet valid. Fetched from name servers "{ns_list}".The RRSIG (signature) with tag {keytag} for the NSEC3 record cannot be verified. Fetched from name servers "{ns_list}".The RRSIG (signature) with tag {keytag} for the NSEC3 record has expired. Fetched from name servers "{ns_list}".The RRSIG (signature) with tag {keytag} for the NSEC3 record it not yet valid. Fetched from name servers "{ns_list}".The SOA RNAME field ({rname}) is compliant with RFC2822.The SOA RNAME mail domain ({domain}) cannot be resolved to a mail server with an IP address.The SOA RNAME mail domain ({domain}) refers to an address which is an alias (CNAME).The SOA RNAME mail domain ({domain}) resolved to a mail server with localhost ({localhost}) IP address.The SOA RRset is not signed by algorithm {algo_num} ({algo_mnemo}) present in the DNSKEY RRset. Fetched from the nameservers with IP addresses "{ns_ip_list}".The SOA RRset is not signed, which is against expectation. Fetched from the nameservers with IP addresses "{ns_ip_list}".The SOA RRset is signed with an RRSIG with tag {keytag} which cannot be validated by the matching DNSKEY. Fetched from the nameservers with IP addresses "{ns_ip_list}".The SOA RRset is signed with an RRSIG with tag {keytag} which does not match any DNSKEY record. Fetched from the nameservers with IP addresses "{ns_ip_list}".The SPF policy of {domain} has a syntax error. Policy retrieved from the following nameservers: {ns_list}.The SPF policy of {domain} has correct syntax.The alias for "{domain}" is inconsistent between name servers.The child zone has no mail target (no MX).The child zone is unsigned, but the parent zone has DS record.The domain must have a parent domainThe domain must have at least one working name serverThe fake delegation of domain {domain} includes a name server {nsname} that cannot be resolved to any IP address.The fake delegation of domain {domain} includes an in-zone name server {nsname} without mandatory glue (without IP address).The following name server(s) are announced in the same IPv4 prefix ({ip_prefix}): "{ns_list}"The following name server(s) are announced in the same IPv6 prefix ({ip_prefix}): "{ns_list}"The following name server(s) are announced in unique IPv4 prefix(es): "{ns_list}"The following name server(s) are announced in unique IPv6 prefix(es): "{ns_list}"The following name server(s) do not respond or respond with SERVFAIL to software version query "{query_name}". Returned from name servers: "{ns_list}"The following name server(s) do not return CH class record(s) on CH class query. Returned from name servers: "{ns_list}"The following name server(s) do not reveal the software version. Returned from name servers: "{ns_list}"The following name server(s) respond to software version query "{query_name}" with string "{string}". Returned from name servers: "{ns_list}"The following name servers do not provide DS record or have not been properly configured. Fetched from parent name servers "{ns_list}".The following name servers do not respond on DNSKEY query with DO bit set. Name servers: "{ns_list}".The following name servers do not support DNSSEC or have not been properly configured. Testing for NSEC and NSEC3 has been skipped on these servers. Fetched from name servers "{ns_list}".The following name servers do not support DNSSEC or have not been properly configured. Testing for NSEC3 has been skipped on those servers. Fetched from name servers "{ns_list}".The following name servers do not use NSEC3, but others do. Testing for NSEC3 has been skipped on the following servers. Fetched from name servers "{ns_list}".The following name servers give a non authoritative response on DNSKEY query with DO bit set. Name servers: "{ns_list}".The following name servers give a non-standard response to the NSEC query (NSEC RR in authority section instead of answer section). Fetched from name servers "{ns_list}".The following name servers respond with DNSKEY (signed child zone). Name servers: "{ns_list}".The following name servers respond with RCODE "{rcode}" instead of expected "NOERROR" on DNSKEY query with DO bit set. Name servers: "{ns_list}".The following name servers respond with no DNSKEY (unsigned child zone). Name servers: "{ns_list}".The following name servers returned more than one SPF policy. Name servers: {ns_list}.The following name servers returned the same SPF policy. Name servers: {ns_list}.The following nameservers answer AAAA queries without problems : {ns_list}.The following nameservers failed to resolve to an IP address : {nsname_list}.The following nameservers support EDNS0 : {ns_list}.The following parent name servers respond with DS record or records for the child zone. Name servers: "{ns_list}".The following parent name servers respond without DS record for the child zone. Name servers: "{ns_list}".The following servers do not respond to NSEC query. Fetched from name servers "{ns_list}".The following servers give erroneous response to NSEC query. Fetched from name servers "{ns_list}".The following servers respond with NSEC3 iteration value set to zero (as recommended). Fetched from name servers "{ns_list}".The following servers respond with NSEC3 opt-out disabled (as recommended). Fetched from name servers "{ns_list}".The following servers respond with NSEC3 opt-out enabled. Fetched from name servers "{ns_list}".The following servers respond with NSEC3 opt-out enabled. The recommended practice is to disable opt-out. Fetched from name servers "{ns_list}".The following servers respond with a legal empty salt in NSEC3. Fetched from name servers "{ns_list}".The following servers respond with a legal hash algorithm in NSEC3. Fetched from name servers "{ns_list}".The following servers respond with a non-empty salt in NSEC3 ({int} octets). The recommended practice is to use an empty salt. Fetched from name servers "{ns_list}".The following servers respond with an NSEC3 record where an unassigned flag is used (bit {int}). Fetched from name servers "{ns_list}".The following servers respond with an illegal hash algorithm for NSEC3 ({algo_num}). Fetched from name servers "{ns_list}".The following servers respond with the NSEC3 iteration value {int}. The recommended practice is to set this value to 0. Fetched from name servers "{ns_list}".The name servers for parent zone "{domain_parent}" give inconsistent delegation of "{domain_child}". Returned from name servers "{ns_list}".The parent zone cannot be determined on name servers "{ns_list}".The parent zone cannot be found.The parent zone has DS record or records for the signed child zone.The parent zone has no DS record for the signed child zone.The parent zone is "{domain}" as returned from name servers "{ns_list}".The parent zone provides no DS records for the child zone. Fetched from parent name servers "{ns_list}".The returned NSEC record has an unexpected non-apex owner name. Fetched from name servers "{ns_list}".The returned NSEC3 record unexpectedly does not match the zone name. Fetched from name servers "{ns_list}".The returned NSEC3PARAM record has an unexpected non-apex owner name. Fetched from name servers "{ns_list}".The server responded with DNSKEY but not with expected NSEC or NSEC3. Fetched from name servers "{ns_list}".The smallest possible legal referral packet is larger than 512 octets (it is {size}).The smallest possible legal referral packet is smaller than 513 octets (it is {size}).The zone "{domain}" is found.The zone does not use NSEC3. Testing for NSEC3 has been skipped. Fetched from name servers "{ns_list}".The zone has NSEC records. Fetched from name servers "{ns_list}".The zone has NSEC3 records. Fetched from name servers "{ns_list}".The zone has a Null MX mixed with other MX records.The zone has a Null MX with non-zero preference.The zone is a TLD and has an unexpected MX RRset (non-Null MX).The zone is inconsistent on NSEC and NSEC3. NSEC is fetched from name servers "{ns_list_nsec}". NSEC3 is fetched from name servers "{ns_list_nsec3}".The zone is not DNSSEC signed or not properly DNSSEC signed. DNSKEY cannot be tested. Fetched from name servers "{ns_list}".The zone is not DNSSEC signed or not properly DNSSEC signed. Testing for NSEC and NSEC3 has been skipped. Fetched from name servers "{ns_list}".The zone is not DNSSEC signed or not properly DNSSEC signed. Testing for NSEC3 has been skipped. Fetched from name servers "{ns_list}".The zone is not signed.The zone is signed.The zone responds with both NSEC and NSEC3, where only one of them is expected. Fetched from name servers "{ns_list}".There is a DS record with keytag {keytag}. A DS record using digest algorithm 2 (SHA-256) is missing. Fetched from parent name servers "{ns_list}".There is no DNSKEY record matching the RRSIG (signature) with tag {keytag} for the NSEC record. Fetched from name servers "{ns_list}".There is no DNSKEY record matching the RRSIG (signature) with tag {keytag} for the NSEC3 record. Fetched from name servers "{ns_list}".There is no RRSIG (signature) for the NSEC record that can be verified. Fetched from name servers "{ns_list}".There is no delegation (name servers) for "{domain}" which means it does not exist as a zone.There is no misused '@' character in the SOA RNAME field ({rname}).There is no response on query with unknown EDNS option-code from name servers "{ns_ip_list}".There is no valid DNSKEY matched by any of the DS records. Fetched from the nameservers with IP addresses "{ns_ip_list}".There is no working name server for "{domain}" so it is unreachable.There must be no double hyphen ('--') in position 3 and 4 of the domain nameThis is a test of an undelegated domain so finding the parent zone is disregarded.This is a test of the root zone which has no parent zone.To check whether authoritative name servers return an upward referralUDP connectivityUnexpected DNS record in the answer section on an NSEC query. Fetched from name servers "{ns_list}".Unexpected DNS record in the answer section on an NSEC3PARAM query. Fetched from name servers "{ns_list}".Unexpected RCODE value ({rcode}) on the MX query from name servers "{ns_ip_list}".Unexpected or erroneous reply from {ns}.Unexpected response on query for "{query_name}" with query type "{rrtype}" to "{ns}".Unsigned child zone found on nameservers with IP addresses "{ns_ip_list}".Upward referral tests skipped for root zone.Using module {module} version {version}.Using prerequisite module {name} version {version}.Using version {version} of the Zonemaster engine.Valid RRSIG for DNSKEYValidate CDNSKEYValidate CDSValidate trust from DS to CDS and CDNSKEYVerify DNSSEC additional processingVerify NSEC3 parametersWhen asked for {type} records on "{domain}" with different cases, all servers do not reply consistently.When asked for {type} records on "{domain}" with different cases, all servers reply consistently.When asked for {type} records on "{domain}", nameserver {ns} returns nothing.When asked for {type} records on "{query1}" and "{query2}", nameserver {ns} returns different RCODE ("{rcode1}" vs "{rcode2}").When asked for {type} records on "{query1}" and "{query2}", nameserver {ns} returns different answers.When asked for {type} records on "{query1}" and "{query2}", nameserver {ns} returns same RCODE "{rcode}".When asked for {type} records on "{query1}" and "{query2}", nameserver {ns} returns same answers.Wrong owner name ("{domain}") on SOA record in NODATA response with NSEC. Fetched from name servers "{ns_list}".Wrong owner name ("{domain}") on SOA record in NODATA response with NSEC3. Fetched from name servers "{ns_list}".Zone contains NSEC or NSEC3 recordsProject-Id-Version: 1.0.0 Report-Msgid-Bugs-To: PO-Revision-Date: 2026-06-12 20:10+0000 Language-Team: Zonemaster Team Language: sv MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit "{domain_child}" finns inte som DNS-zon. Testa "{domain_super}" istÃ¤llet."{domain_child}" Ã¤r inte en DNS-zon. Det Ã¤r ett alias fÃ¶r "{domain_target}". Testa "{domain_target}" istÃ¤llet. Information frÃ¥n namnservrarna "{ns_list}".Det finns ett CDNSKEY RRset, men det finns inga DNSKEY-poster. HÃ¤mtat frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".Det finns ett CDS RRset, men det finns inga DNSKEY-poster. HÃ¤mtat frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".En namnserver ska inte vara en rekursiv resolver{domain} har en faktisk SPF-policy trots att domÃ¤ntypen (rot, TLD, .ARPA) normalt inte anvÃ¤nds fÃ¶r e-post.{domain} har en null-SPF-policy â€” typiskt fÃ¶r domÃ¤ner (rot, TLD, .ARPA) som inte anvÃ¤nds fÃ¶r e-post.Exakt en CDNSKEY-post av typen "delete" finns pÃ¥ namnservrarna med IP-adresserna "{ns_ip_list}".Exakt en CDS-post av typen "delete" finns pÃ¥ namnservrarna med IP-adresserna "{ns_ip_list}".Exakt en uppsÃ¤ttning namnservrar hittades: ({nsname_list}).Exakt en 'SOA MNAME' hittades: ({mname}).Exakt en 'SOA RNAME' hittades: ({rname}).Exakt ett SOA-serienummer hittades: ({serial}).Exakt en uppsÃ¤ttning SOA-tidsparametrar hittades: (REFRESH={refresh},RETRY={retry},EXPIRE={expire},MINIMUM={minimum}).Alla namnservrar fÃ¶r zonen rapporterade samma SOA-post.AS-spridningAS-databasen gav ingen information fÃ¶r IP-adressen {ns_ip}.Fel pÃ¥ AS-databas. Det finns ingen data att analysera fÃ¶r {ns_ip}.AXFR Ã¤r inte tillgÃ¤nglig frÃ¥n namnservern "{ns}".Alla DNSKEY-algoritmer ska anvÃ¤ndas fÃ¶r att signera zonenIPv4-adresserna fÃ¶r alla auktoritativa namnservrar tillhÃ¶r samma AS ({asn}).IPv4-adresserna fÃ¶r alla auktoritativa namnservrar tillhÃ¶r samma uppsÃ¤ttning AS ({asn_list}).IPv6-adresserna fÃ¶r alla auktoritativa namnservrar tillhÃ¶r samma AS ({asn}).IPv6-adresserna fÃ¶r alla auktoritativa namnservrar tillhÃ¶r samma uppsÃ¤ttning AS ({asn_list}).Alla nycklar i DNSKEY RR-uppsÃ¤ttningen har rÃ¤tt storlek.Alla namnserverns IPv4-adresser tillhÃ¶r samma IPv4-prefix.Alla namnservrars IPv6-adresser tillhÃ¶r samma IPv6-prefix.Alla namnservrar skickade svar frÃ¥n samma IP-adress som frÃ¥gan stÃ¤lldes till.Alla namnservrar kunde slÃ¥s upp till minst en IP-adress.Alla namnservrar (NS-poster) finns bÃ¥de i delegeringen (moderzon) och i dotterzonen.Alla servrar har inte samma CDNSKEY RRset.Alla servrar har inte samma CDS RRset.Varje namnserver har unika IP-adress som inte delas med andra namnservrar.Varje namnserver i dotterzonen har unik IP-adress som inte delas med andra namnservrar.Varje namnserver i delegeringen har unik IP-adress som inte delas med andra namnservrar.Alla namnservrar har en SOA-post.FÃ¶ljande namnservrar har bekrÃ¤ftats vara auktoritativa : {nsname_list}.DomÃ¤nnamnet innehÃ¥ller den versala (stora) bokstaven "{unicode_name}". Det Ã¤r oklart hur den ska omvandlas till den motsvarande gemen (lilla) bokstaven. AnvÃ¤nd bara gemener (smÃ¥ bokstÃ¤ver) istÃ¤llet.Minst tvÃ¥ IPv4-adresser fÃ¶r de auktoritativa namnservrarna tillhÃ¶r tvÃ¥ olika AS-uppsÃ¤ttningar. En ihopslagen lista Ã¶ver alla AS: {asn_list}.Minst tvÃ¥ IPv6-adresser fÃ¶r de auktoritativa namnservrarna tillhÃ¶r tvÃ¥ olika AS-uppsÃ¤ttningar. En ihopslagen lista Ã¶ver alla AS: {asn_list}.Auktoritativt svar pÃ¥ SOA-frÃ¥ga fÃ¶r "{domain}" kommer frÃ¥n namnservrarna "{ns_list}".Beteende gÃ¤llande AAAA-frÃ¥gorStort paket ({size} byte). AnvÃ¤nd kommandot '{command}' fÃ¶r att se svarspaketet.BÃ¥de CDS och CDNSKEY RRsets finns pÃ¥ namnservrar med IP-adresser "{ns_ip_list}", med de stÃ¤mmer inte med varandra.BÃ¥de IPv4 och IPv6 Ã¤r inaktiverade.Felaktigt svar frÃ¥n namnservern "{ns}" pÃ¥ frÃ¥ga efter SOA-post.CDNSKEY RRset finns pÃ¥ namnservrarna med IP-adresserna "{ns_ip_list}", men inget CDS RRset.CDNSKEY och CDS RRsets finns pÃ¥ namnservrarna med IP-adresseserna "{ns_ip_list}".CDS RRset finns pÃ¥ namnservrarna med IP-adresserna "{ns_ip_list}", men inget CDNSKEY RRset.Kontrollera sÃ¥ att ogiltiga algoritmer inte anvÃ¤nds fÃ¶r DNSKEY-posternaKontrollera sÃ¥ att RRSIG-postens livslÃ¤ngd inte Ã¤r fÃ¶r kort eller fÃ¶r lÃ¥ngKontrollera fÃ¶r giltig storlek pÃ¥ DNSKEY av type RSAKontroll av rapporterad version av programvaraDotterzonen listar inte tillrÃ¤ckligt mÃ¥nga namnservrar ({count}) med IPv4-adresser. Minsta tillÃ¥tna antal Ã¤r {minimum}. Namnservrar: {ns_list}.Det finns inte tillrÃ¤ckligt mÃ¥nga namnservrar (NS-poster) i dotterzonen med IPv6-adress. Antal: {count}. Adresser: {ns_list}. Minsta tillÃ¥tna antal Ã¤r {minimum}.Det finns inte tillrÃ¤ckligt mÃ¥nga namnservrar (NS-poster) i dotterzonen. Antal: {count}. Namnservrar: {nsname_list}. Minsta tillÃ¥tna antal Ã¤r {minimum}.Dotterzonen har en eller flera extra namnserver-IP-adresser som inte finns med i moderzonen ({ns_ip_list}).Dotterzonen har en eller flera namnservrar som inte finns i delegeringen i moderzonen ({extra}).Dotterzonen listar tillrÃ¤ckligt mÃ¥nga namnservrar ({count}) med IPv4- adresser. Minsta tillÃ¥tna antal Ã¤r {minimum}. Namnservrar: {ns_list}Dotterzonen listar tillrÃ¤ckligt mÃ¥nga namnservrar ({count}) med IPv6-adresser. Minsta tillÃ¥tna antal Ã¤r {minimum}. Namnservrar: {ns_list}.Dotterzonen har tillrÃ¤ckligt mÃ¥nga namnservrar ({count}). Minsta tillÃ¥tna antal Ã¤r {minimum}. Namnservrar: {nsname_list}.Det finns inga namnservrar (NS-poster) i dotterzonen med IPv4-adress. Om sÃ¥dana finns sÃ¥ Ã¤r minsta tillÃ¥tna antalet {minimum}.Det finns inga namnservrar (NS-poster) i dotterzonen med IPv6-adress. Om sÃ¥dana finns sÃ¥ Ã¤r minsta tillÃ¥tna antalet {minimum}.Glue-poster Ã¥terfinns som auktoritativa adressposterDNS-frÃ¥ga till "{ns}" fÃ¶r {domain}/{type}/{class} misslyckades med felet: '{message}'.DNSKEY-posten med "key tag" {keytag}, som anvÃ¤nds med kryptoalgoritm {algo_num} ({algo_descr}), har en nyckelstorlek ({keysize}) som Ã¤r stÃ¶rre Ã¤n den maximala storleken ({keysizemax}) fÃ¶r den algoritmen.DNSKEY-posten med "key tag" {keytag}, som anvÃ¤nds med kryptoalgoritm {algo_num} ({algo_descr}), har en nyckelstorlek ({keysize}) som Ã¤r mindre Ã¤n den minsta tillÃ¥tna storleken ({keysizemin}) fÃ¶r den algoritmen.DNSKEY-posten med "key tag" {keytag}, som anvÃ¤nds med kryptoalgoritm {algo_num} ({algo_descr}), har en nyckelstorlek ({keysize}) som Ã¤r mindre Ã¤n den minsta rekommenderade storleken ({keysizerec}) fÃ¶r den algoritmen.DNSKEY-posten med "key tag" {keytag} anvÃ¤nds med kryptoalgoritm {algo_num} ({algo_mnemo}) som inte stÃ¶ds av denna installation av Zonemaster. HÃ¤mtad frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".DNSKEY-posten med "key tag" {keytag} anvÃ¤nds med kryptoalgoritm {algo_num} ({algo_mnemo}) som inte stÃ¶ds av denna installation av Zonemaster. HÃ¤mtad frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}". Zonen Ã¤r DNSSEC-signerad och moderzonen innehÃ¥ller motsvarande DS-post.Delegering med DS-post krÃ¤ver DNSSEC-signerad dotterzonDS-posten mÃ¥ste peka pÃ¥ en giltig DNSKEY-post i dotterzonenDet finns DS-post fÃ¶r dotterzonen i moderzonens namnservrar med IP-adresserna "{ns_ip_list}".Det finns inte tillrÃ¤ckligt mÃ¥nga namnservrar (NS-poster) i delegeringen med IPv4-adress. Antal: {count}. Adresser: {ns_list}. Minsta tillÃ¥tna antal Ã¤r {minimum}.Det finns inte tillrÃ¤ckligt mÃ¥nga namnservrar (NS-poster) i delegeringen med IPv6-adress. Antal: {count}. Adresser: {ns_list}. Minsta tillÃ¥tna antal Ã¤r {minimum}.Det finns inte tillrÃ¤ckligt mÃ¥nga namnservrar (NS-poster) i delegeringen. Antal: {count}. Namnservrar: {nsname_list}. Minsta tillÃ¥tna antal Ã¤r {minimum}.Delegeringen listar tillrÃ¤ckligt mÃ¥nga namnservrar ({count}) med IPv4-adresser. Minsta tillÃ¥tna antal Ã¤r {minimum}. Namnservrar: {ns_list}.Delegeringen listar tillrÃ¤ckligt mÃ¥nga namnservrar ({count}) med IPv6-adresser. Minsta tillÃ¥tna antal Ã¤r {minimum}. Namnservrar: {ns_list}.Delegeringen innehÃ¥ller tillrÃ¤ckligt mÃ¥nga namnservrar ({count}). Minsta tillÃ¥tna antal Ã¤r {minimum}. Namnservrar: {nsname_list}Det finns inga namnservrar (NS-poster) i delegeringen med IPv4-adress. Om sÃ¥dana finns sÃ¥ Ã¤r minsta tillÃ¥tna antalet {minimum}.Det finns inga namnservrar (NS-poster) i delegeringen med IPv6-adress. Om sÃ¥dana finns sÃ¥ Ã¤r minsta tillÃ¥tna antalet {minimum}.Spannet mellan hÃ¶gsta och lÃ¤gsta SOA-serienumret ({serial_min} resp {serial_max}) Ã¤r stÃ¶rre Ã¤n det maximalt tillÃ¥tna spannet ({max_variation}).DomÃ¤nnamnet '{domain}' har domÃ¤ndelen '{label}' som slutar med ett bindestreck.DomÃ¤nnamnet '{domain}' har en domÃ¤ndel '{label}' som bÃ¶rjar med ett bindestreck.DomÃ¤ndelen '{label}' i domÃ¤nnamnet {domain} Ã¤r fÃ¶r lÃ¥ng ({dlength} tecken). Maximal lÃ¤ngd Ã¤r {max}.DomÃ¤nnamnet '{domain}' har domÃ¤ndelen '{label}' med bindestreck i position 3 och 4 utan att bÃ¶rja med IDN-prefixet 'xn--'.DomÃ¤nnamnet "{domain}" har en domÃ¤ndel med lÃ¤ngden noll.DomÃ¤ndelarna i domÃ¤nnamnet '{domain}' har antingen inte bindestreck i position 3 och 4 eller har IDN-prefixet 'xn--'.DomÃ¤nens MX ({domain}) har domÃ¤ndelen '{label}' med bindestreck i position 3 och 4 utan att bÃ¶rja med IDN-prefixet 'xn--'.MX-namnet '{domain}' Ã¤r giltigt.DomÃ¤nens MX ('{domain}') Ã¤r i en helnumerisk TLD ({tld}).DomÃ¤nnamnet inkluderar en domÃ¤ndel ("label") som Ã¤r fÃ¶r lÃ¥ng (mer Ã¤n 63 tecken). DomÃ¤ndelen Ã¤r "{label}".DomÃ¤nnamnet inkluderar en domÃ¤ndel ("label"), som inte bara bestÃ¥r av ASCII-tecken, men som inte Ã¤r en giltig U-label enligt IDN. DomÃ¤ndelen Ã¤r "{label}".DomÃ¤nnamnet har domÃ¤ndelen ("label") "{label}", som bara bestÃ¥r av ASCII-tecken, men som innehÃ¥ller ett otillÃ¥tet tecken.DomÃ¤nnamnet har upprepade punkter.DomÃ¤nnamnet Ã¤r tomt.DomÃ¤nnamnet Ã¤r fÃ¶r lÃ¥ngt (mer Ã¤n 253 tecken utan slutpunkt).DomÃ¤nnamnet Ã¤r fÃ¶r lÃ¥ngt ({fqdnlength} tecken). Maximal lÃ¤ngd Ã¤r {max}.DomÃ¤nnamnet startar med en punktEn SOA-frÃ¥ga fick ett svar med svarskoden (RCODE) "NOERROR" frÃ¥n "{ns}", men svaret var tomt.Den felaktiga svarskoden (RCODE) "{rcode}" i svaret pÃ¥ en frÃ¥ga med EDNS version 1. HÃ¤mtat frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".Felaktigt svar frÃ¥n namnservern "{ns}".Varje reversuppslagning (PTR) stÃ¤mmer med motsvarande namnservernamn.Existens av CDS- och CDNSKEY-posterExistens av SOA-postFÃ¶rvÃ¤ntad svarskod (RCODE), men felaktigt svar pÃ¥ en frÃ¥ga med EDNS version 1. HÃ¤mtad frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".Fatalt fel i '{module}': '{msg}'.FlaggfÃ¤ltet som hÃ¶r till DNSKEY-posten med "key tag" {keytag} har inte SEP-flaggan satt trots att det finns en DS-post med samma "key tag" i moderzonen. HÃ¤mtad frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".FlaggfÃ¤ltet i DNSKEY-posten med "key tag" {keytag} har inte "Zone Key"-flaggan satt trots att det finns en DS-post med samma "key tag" i moderzonen. HÃ¤mtad frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}"."{rname}" fanns i "SOA RNAME" pÃ¥ fÃ¶ljande namnservrar: {ns_list}.OtillÃ¥tna tecken hittades i MX ({domain}).OtillÃ¥tna tecken hittades i SOA MNAME ({domain}).Det finns otillÃ¥tna tecken i domÃ¤nnamnet '{domain}'.Det finns otillÃ¥tna tecken i namnservernamnet '{domain}'.{count} NS-uppsÃ¤ttningar hittades.{count} olika 'SOA RNAME' hittades.{count} olika SOA-serienummer hittades.{count} olika uppsÃ¤ttningar med SOA-tidsparametrar hittades.Faktisk primÃ¤r namnserver i SOA MNAMEEn fungerande namnserver hittades. Skickade ingen frÃ¥ga om 'A' fÃ¶r 'www.{zname}' (behÃ¶vdes inte).IP-adresser som Ã¤r globalt nÃ¥bara: {ns_list}.Glue-poster stÃ¤mmer Ã¶verens mellan delegering och auktoritativ data.IP-prefix-spridningIP-adresser som Ã¤r avsedda fÃ¶r dokumentationsÃ¤ndamÃ¥l: {ns_list}.IP-adresser avsedda fÃ¶r lokal anvÃ¤ndning inom nÃ¤tverk eller hos tjÃ¤nsteleverantÃ¶r: {ns_list}.IP-adresser som inte Ã¤r angivna som globalt nÃ¥bara: "{ns_list}".IP-adressen {ns_ip} anvÃ¤nds av flera namnservrar (NS-poster) i dotterzonen ({nsname_list}).IP-adressen {ns_ip} anvÃ¤nds till flera namnservrar (NS-poster) i delegeringen ({nsname_list}).IP-adressen {ns_ip} referrerar till flera namnservrar ({nsname_list}).IPv4 Ã¤r inaktiverat. Skickar ingen frÃ¥ga om '{rrtype}' till {ns}.IPv4 Ã¤r inaktiverat. Inga DNS-frÃ¥gor skickas till "{ns_list}".IPv4 Ã¤r aktiverat. Skickar frÃ¥ga om '{rrtype}' till {ns}.IPv6 Ã¤r inaktiverat. Skickar ingen frÃ¥ga om '{rrtype}' till {ns}.IPv6 Ã¤r inaktiverat. Inga DNS-frÃ¥gor skickas till "{ns_list}".IPv6 Ã¤r aktiverat. Skickar frÃ¥ga om '{rrtype}' till {ns}.OtillÃ¥tet tecken finns i SOA RNAME ({rname}).Delegeringen inkluderar en eller flera IP-adresser ({parent_addresses}) fÃ¶r en eller flera namnservrar som namnmÃ¤ssigt tillhÃ¶r dotterzonen. IP-adressen eller -addresserna stÃ¤mmer inte med motsvarande adressposter i dotterzonen ({zone_addresses}).Inkonsekvent NSEC3-flagglistevÃ¤rde i svaren frÃ¥n olika namnservrar fÃ¶r dotterzonen.Inkonsekvent NSEC3-iterationsvÃ¤rde i svaren frÃ¥n olika namnservrar fÃ¶r dotterzonen.Inkonsekvent hash-algoritm i NSEC3 i svaren frÃ¥n olika namnservrar fÃ¶r dotterzonen.Namnservrar svarar inkonsekvent: nÃ¥gra skickar signerade svar, andra inte.Moderzonens namnservrarna ger olika svar â€” vissa ger DS-poster, andra saknar dem.Inkonsekventa svar frÃ¥n zon med NSEC. HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".Inkonsekventa svar frÃ¥n zon med NSEC3. HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".Inkonsekvent saltlÃ¤ngd i NSEC3 i svaren frÃ¥n olika namnservrar fÃ¶r dotterzonen.Felaktig EDNS-version (fÃ¶rvÃ¤ntad version var 0) i svar frÃ¥n "{ns}" pÃ¥ fÃ¶rfrÃ¥gan med EDNS version 0 (frÃ¥ga efter {domain}).Det kan inte faststÃ¤llas ifall dotterzonen Ã¤r signerad eller inte.Det gÃ¥r inte att faststÃ¤llas om moderzonen har DS-poster fÃ¶r dotterzonen eller inte.Det gÃ¥r inte att fÃ¶lja delegeringen av domÃ¤nnamnet.Kontrollera sÃ¥ att giltiga digest-algoritmer anvÃ¤nds fÃ¶r DS-posternaCallback-funktionen fÃ¶r log-modulen avbrÃ¶t med felmeddelandet: '{exception}'.FÃ¶ljande namnservrar gav ett MX RRset: "{ns_ip_list}".Namnet i MX-post ska inte vara ett aliasEn MX-post mÃ¥ste ha ett giltigt namn ("hostname")MX-post fÃ¶r domÃ¤nen pekar inte pÃ¥ ett CNAME.DomÃ¤nens MX-post pekar pÃ¥ ett alias (CNAME).Test av existens av MX-postMailservrarna i MX RRset Ã¤r fÃ¶ljande: "{mailtarget_list}". FrÃ¥n namnservrarna "{ns_ip_list}".Minsta antal namnservrarDet saknas signaturer (RRSIG-poster) fÃ¶r NSEC-posten eller -posterna. HÃ¤mtad frÃ¥n namnservrarna med IP-adresserna "{ns_list}".Saknad RRSIG (signatur) fÃ¶r NSEC3-posten eller -posterna. HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".Saknad SOA-post i NODATA-svar med NSEC. HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".Saknad SOA-post i NODATA-svar med NSEC3. HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".OtillÃ¥ten anvÃ¤ndning av @-tecken i SOA RNAME-fÃ¤ltetOtillÃ¥tet @-tecken i SOA RNAME ({rname}).Modulen '{module}' avslutades.Flera NSEC-poster hittades dÃ¤r endast en fÃ¶rvÃ¤ntades. HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".Flera NSEC3-poster hittades nÃ¤r endast en fÃ¶rvÃ¤ntades. HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".Namnet i NS-posten kan slÃ¥s uppNSEC-posten fÃ¶r zonens apex innehÃ¥ller en felaktig typ-lista. HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".NSEC3-posten fÃ¶r zonens apex har en felaktig typ-lista. HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".Namnservern "{nsname}" kan inte slÃ¥s upp till en IP-adress.Namnservern "{ns}" svarar inte auktoritativt pÃ¥ en SOA-frÃ¥ga.Namnservern "{ns}" besvarar inte en SOA-frÃ¥ga.Namnservern "{ns}" svarar med den ovÃ¤ntade svarskoden (RCODE) "{rcode}" pÃ¥ en SOA-frÃ¥ga.Namnserver-IP-adressen "{ns_ip}" tillhÃ¶r AS {asn}.Namnserver-IP-adressen "{ns_ip}" tillhÃ¶r prefixet "{prefix}".Samma uppsÃ¤ttning NS-poster Ã¶veralltNamnserverns adress mÃ¥ste vara globalt nÃ¥bar.Namnservern Ã¤r auktoritativInget namnservernamn fÃ¥r peka mot ett CNAME-aliasNamnservern "{ns}" lade inte till en skapad delegering av domÃ¤nen '{domain}' till sig sjÃ¤lv.Dotterzonens namnservrar Ã¤r inkonsekventa nÃ¤r det gÃ¤ller ifall zonen Ã¤r signerad eller inte.Namnservrarna har IPv4-adresser i fÃ¶ljande AS: {asn}.Namnservrarna har IPv6-adresser i fÃ¶ljande AS: {asn}.Namnservrarna mÃ¥ste ha distinkta IP-adresserNamnservern '{domain}' har domÃ¤ndelen ({label}) med bindestreck i position 3 och 4 utan att bÃ¶rja med IDN-prefixet 'xn--'.Namnservernamnet '{domain}' Ã¤r giltigt.Namnserver '{domain}' finns under en helnumerisk TLD ('{tld}').Namnservernamnet '{nsname}' pekar pÃ¥ ett CNAME.Namnservern '{nsname}' har en IP-adress ({ns_ip}) med en reversuppslagning (PTR) till '{names}' som inte stÃ¤mmer med namnservernamnet.Namnservern {nsname} har en IP-adress ({ns_ip}) utan reversuppslagning (PTR).Namnservern "{ns}" tillÃ¥ter zonÃ¶verfÃ¶ringar med AXFR.Namnservern "{ns}" besvarade en A-frÃ¥ga med den ovÃ¤ntade svarskoden (RCODE) "{rcode}".Namnservern "{ns}" besvarade en AAAA-frÃ¥ga med den icke-vÃ¤ntade lÃ¤ngden pÃ¥ 'RDATA' om '{length}' oktetter istÃ¤llet fÃ¶r fÃ¶rvÃ¤ntade 16 oktetter.Namnservern "{ns}" besvarade en AAAA-frÃ¥ga med den ovÃ¤ntade svarskoden (RCODE) "{rcode}".Namnservern "{ns}" besvarade en frÃ¥ga om namnet {query_name} och typ {rrtype} med den ovÃ¤ntade svarskoden (RCODE) "{rcode}".Namnservern "{ns}" svarade inte pÃ¥ fÃ¶rfrÃ¥gan om namnet {query_name} och posttypen {rrtype}.Inget svar frÃ¥n namnserver "{ns}".Namnservern {ns} svarade inte med nÃ¥gra A-poster fÃ¶r '{domain}'.Namnservern "{ns}" svarar inte auktoritativt pÃ¥ en NS-frÃ¥ga Ã¶ver TCP.Namnservern "{ns}" svarar inte auktoritativt pÃ¥ en NS-frÃ¥ga Ã¶ver UDP.Namnservern "{ns}" svarar inte auktoritativt pÃ¥ en SOA-frÃ¥ga Ã¶ver TCP.Namnservern "{ns}" svarar inte auktoritativt pÃ¥ en SOA-frÃ¥ga Ã¶ver UDP.Namnservern "{ns}" bevarar inte skillnaden mellan versaler och gemener frÃ¥n frÃ¥gan ({domain}).Namnservern "{ns}" svarar inte pÃ¥ NS-frÃ¥gor Ã¶ver TCP.Namnservern "{ns}" svarar inte pÃ¥ NS-frÃ¥gor Ã¶ver UDP.Namnservern "{ns}" svarar inte pÃ¥ SOA-frÃ¥gor Ã¶ver TCP.Namnservern "{ns}" svarar inte pÃ¥ SOA-frÃ¥gor Ã¶ver UDP.Namnservern "{ns}" svarar inte pÃ¥ nÃ¥gra DNS-frÃ¥gor Ã¶ver TCP.Namnservern "{ns}" svarar inte pÃ¥ nÃ¥gra DNS-frÃ¥gor Ã¶ver UDP.Namnservern "{ns}" stÃ¶der inte EDNS0 (svarar med 'FORMERR').Namnservern "{ns}" besvarade inte AAAA-frÃ¥gan.Svarspaket frÃ¥n namnservern "{ns}" har en eller flera odefinierade bitar satta i Z-flaggan (EDNS).Namnservern "{ns}" Ã¤r en rekursiv resolver.Namnservern "{ns}" Ã¤r ingen rekursiv resolver.Namnservern "{ns}" bevarade versaler och gemener frÃ¥n frÃ¥gan ({domain}).Namnservern "{ns}" besvarade en SOA-frÃ¥ga frÃ¥n en annan kÃ¤lladress ({source}).Namnservern "{ns}" besvarade en fÃ¶rfrÃ¥gan med EDNS med ett trunkerat svarspaket utan EDNS.Svaret frÃ¥n namnservern "{ns}" har ingen DNSKEY-post.Namnservern "{ns}" svarar pÃ¥ en NS-frÃ¥ga Ã¶ver TCP utan att inkludera NS-poster i svarssektionen.Namnservern "{ns}" svarar pÃ¥ en NS-frÃ¥ga Ã¶ver UDP utan att inkludera NS-poster i svarssektionen.Namnservern "{ns}" svarar pÃ¥ en SOA-frÃ¥ga Ã¶ver TCP utan att inkludera SOA-poster i svarssektionen.Namnservern "{ns}" svarar pÃ¥ en SOA-frÃ¥ga Ã¶ver UDP utan att inkludera SOA-poster i svarssektionen.Namnservern "{ns}" svarar med fel domÃ¤nnamn ("owner name") -- {domain_found} istÃ¤llet fÃ¶r {domain_expected} -- pÃ¥ en NS-frÃ¥ga Ã¶ver TCP.Namnservern "{ns}" svarar med fel "owner name" -- {domain_found} istÃ¤llet fÃ¶r {domain_expected} -- pÃ¥ en NS-frÃ¥ga Ã¶ver UDP.Namnservern "{ns}" svarar med fel domÃ¤nnamn ("owner name") -- {domain_found} istÃ¤llet fÃ¶r {domain_expected} -- pÃ¥ en SOA-frÃ¥ga Ã¶ver TCP.Namnservern "{ns}" svarar med fel "owner name" -- {domain_found} istÃ¤llet fÃ¶r {domain_expected} -- pÃ¥ en SOA-frÃ¥ga Ã¶ver UDP.Namnservern "{ns}" ger fel 'owner name' i svaret ({owner} istÃ¤llet fÃ¶r {name}) pÃ¥ SOA-frÃ¥ga.Namnservern "{ns}" svarar med den ovÃ¤ntade svarskoden (RCODE) "{rcode}" pÃ¥ en NS-frÃ¥ga Ã¶ver TCP.Namnservern "{ns}" svarar med den ovÃ¤ntade svarskoden (RCODE) "{rcode}" pÃ¥ en NS-frÃ¥ga Ã¶ver UDP.Namnservern "{ns}" svarar med den ovÃ¤ntade svarskoden (RCODE) "{rcode}" pÃ¥ en SOA-frÃ¥ga Ã¶ver TCP.Namnservern "{ns}" svarar med den ovÃ¤ntade svarskoden (RCODE) "{rcode}" pÃ¥ en SOA-frÃ¥ga Ã¶ver UDP.Namnservern "{ns}" svarade med multipla ({count}) SOA-poster pÃ¥ SOA-frÃ¥gor.Namnservern "{ns}" svarade inte auktoritativt pÃ¥ {proto} port 53.Namnservern "{ns}" svarade med A-poster fÃ¶r "{domain}".Namnservern "{ns}" skickade en hÃ¤nvisning till moderzonen.Namnservern svarade inte pÃ¥ en A-frÃ¥ga.DomÃ¤nnamnet '{domain}' har ingen domÃ¤ndel som bÃ¶rjar eller slutar med ett bindestreck.Det finns inga CDS eller CDNSKEY RRset i nÃ¥gon namnserver.Det finns inga DS-poster fÃ¶r dotterzonen i moderzonens namnservrar med IP-adresserna "{ns_ip_list}".Det finns ingen IP-adress fÃ¶r servern angiven som SOA MNAME ({mname}).FÃ¶ljande namnservrar gav inget MX RRset: "{ns_ip_list}".{domain} har ingen SPF-policy â€” sÃ¥dana domÃ¤ner (rot, TLD, .ARPA) anvÃ¤nds normalt inte fÃ¶r e-post.Ingen SPF-policy hittades fÃ¶r {domain}.Inget bindestreck ("-") i start eller slut av domÃ¤nnamnsdelInga otillÃ¥tna tecken i SOA MNAME-fÃ¤ltetInga otillÃ¥tna tecken i SOA RNAME-fÃ¤ltetInga otillÃ¥tna tecken i domÃ¤nnamnetEndast tillÃ¥tna tecken i namnet '{domain}'.Inte multipla SOA-posterInga namnservrar kunde hittas.Inget namnservernamn har en CNAME-post.Det gick inte att slÃ¥ upp IP-adressen fÃ¶r nÃ¥gon namnserver.Inget svar frÃ¥n namnserver "{ns}" pÃ¥ frÃ¥ga efter NS-post.Inget svar frÃ¥n namnservern "{ns}" pÃ¥ frÃ¥ga efter SOA-post.Inget svar frÃ¥n namnserver pÃ¥ frÃ¥ga efter MX-post.Inget svar frÃ¥n namnservern pÃ¥ PTR-frÃ¥ga ({domain}).Inget svar frÃ¥n namnserver pÃ¥ frÃ¥ga efter SOA-post.Inget svar frÃ¥n "{ns}" pÃ¥ fÃ¶rfrÃ¥gan efter {domain}.Inget svar frÃ¥n "{ns}" pÃ¥ fÃ¶rfrÃ¥gan med EDNS (frÃ¥ga efter {domain}).Inget svar pÃ¥ MX-fÃ¶rfrÃ¥gan frÃ¥n namnservrar "{ns_ip_list}".DNSKEY-frÃ¥gan misslyckades hos alla namnservrar. Felande servrar: "{ns_list}".Inget svar eller felaktigheter i svarsposten pÃ¥ en frÃ¥ga om DS frÃ¥n moderzonens namnservrar. HÃ¤mtades frÃ¥n fÃ¶ljande namnservrarna "{ns_list}".Inget svar eller felaktigheter i svarsposten pÃ¥ en frÃ¥ga om NSEC. HÃ¤mtad frÃ¥n namnservrarna med IP-adresserna "{ns_list}".Inget svar eller felaktigt svar vid fÃ¶rfrÃ¥gan om NSEC3PARAM. HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".Inget svar pÃ¥ en frÃ¥ga med EDNS version 1. HÃ¤mtad frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".Ingen avkortning av hÃ¤nvisningarIcke-auktoritativt svar pÃ¥ MX-fÃ¶rfrÃ¥gan frÃ¥n namnservrar "{ns_ip_list}".Ingen av fÃ¶ljande nameserverar skickar hÃ¤nvisning till rotzonen: {nsname_list}.Ingen av namnservrarnas IP-adresser Ã¤r angivna som globalt nÃ¥bara.Ingen av de namnservrar som finns i delegeringen (moderzonen) finns i dotterzonen.Ingen av zonens namnservrar svarade auktoritativt pÃ¥ fÃ¶rfrÃ¥gningar om SPF-policys.Det finns inte tillrÃ¤ckligt med data om '{domain}' fÃ¶r att kunna kÃ¶ra tester.En eller flera namnservrar publicerar inte samma SPF-policy som de andra.Delegeringen inkluderar en eller flera IP-adresser ({parent_addresses}) fÃ¶r en eller flera namnservrar som Ã¤r 'out-of-bailiwick'. IP-adressen/addresserna stÃ¤mmer inte med motsvarande adressposter i auktoritativ zon eller zoner ({zone_addresses}).Glue-poster i moderzonen Ã¥terfinns i dotterzonenDelegeringen i moderzonen har en eller flera namnservrar (NS) som inte listas i dotterzonen ({extra}).Moderzonens namnservrarna Ã¤r inkonsekventa nÃ¤r det gÃ¤ller existensen av DS.Fel i prefixdatabasen fÃ¶r IP-adressen {ns_ip}.Databasen Ã¶ver IP-prefix gav ingen information fÃ¶r IP-adressen {ns_ip}.Giltighetstiden fÃ¶r RRSIG-posten med "key tag" {keytag} och som gÃ¤ller posttypen DNSKEY har lÃ¶pt ut. HÃ¤mtad frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".Giltighetstiden fÃ¶r RRSIG-posten med "key tag" {keytag} och som gÃ¤ller posttypen DNSKEY har inte bÃ¶rjat gÃ¤lla. HÃ¤mtad frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".Giltighetstiden fÃ¶r RRSIG-posten med "key tag" {keytag} och som gÃ¤ller posttypen SOA har lÃ¶pt ut. HÃ¤mtad frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".Giltighetstiden fÃ¶r RRSIG-posten med "key tag" {keytag} och som gÃ¤ller posttypen SOA har inte bÃ¶rjat gÃ¤lla. HÃ¤mtad frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".RRSIG-post med "key tag" {keytag} som tÃ¤cker posttyp(er) {types} lÃ¶per ut {date}.RRSIG-posten med "key tag" {keytag} och som tÃ¤cker posttyp(er) {types} har en livslÃ¤ngd pÃ¥ {duration} sekunder (acceptabel livslÃ¤ngd).RRSIG-posten med "key tag" {keytag} och som tÃ¤cker posttyp(er) {types} har en livslÃ¤ngd pÃ¥ {duration} sekunder, vilket Ã¤r fÃ¶r lÃ¥ng tid.RRSIG-posten med "key tag" {keytag} och som tÃ¤cker posttyp(er) {types} har en kvarvarande livslÃ¤ngd pÃ¥ {duration} sekunder, vilket Ã¤r fÃ¶r lÃ¥ng tid.RRSIG-posten med "key tag" {keytag} och som tÃ¤cker posttyp(er) {types} har en kvarvarande livslÃ¤ngd pÃ¥ {duration} sekunder, vilket Ã¤r fÃ¶r kort tid.Giltighetstiden fÃ¶r RRSIG-posten med "key tag" {keytag} och som tÃ¤cker posttyp(er) {types} har lÃ¶pt ut (utgÃ¥ngstiden Ã¤r: {expiration}).RRSIG-posterna fÃ¶r SOA-posten mÃ¥ste vara giltiga och skapade av giltig DNSKEYBegÃ¤ran om att kÃ¶ra den okÃ¤nda metoden '{testcase}' i modulen '{module}'.BegÃ¤ran om att kÃ¶ra metoden '{testcase}' i den okÃ¤nda modulen '{module}'. KÃ¤nda moduler: '{module_list}'.Svaret frÃ¥n namnservern "{ns}" pÃ¥ en frÃ¥ga efter SOA innehÃ¥ller ingen SOA-post.Svar utan EDNS frÃ¥n "{ns}" pÃ¥ fÃ¶rfrÃ¥gan med EDNS0 (frÃ¥ga efter {domain}).Reversuppslagning (PTR) finns fÃ¶r varje namnserveradress.BakÃ¥tuppslagning (PTR) finns fÃ¶r namnserverns IP-adress.BakÃ¥tuppslagningen (PTR) stÃ¤mmer med namnservernamnet.Rotzon med ett ovÃ¤ntat MX RRset (icke-Null MX).Minsta vÃ¤rde fÃ¶r SOA "expire"VÃ¤rdet fÃ¶r SOA 'expire' ({expire}) Ã¤r lika med eller hÃ¶gre Ã¤n det minsta rekommenderade vÃ¤rdet ({required_expire}) och inte lÃ¤gre Ã¤n vÃ¤rdet pÃ¥ 'refresh' ({refresh}).VÃ¤rdet fÃ¶r SOA 'expire' ({expire}) Ã¤r lÃ¤gre Ã¤n rekommenderat ({required_expire}).VÃ¤rdet fÃ¶r SOA 'expire' ({expire}) Ã¤r lÃ¤gre Ã¤n vÃ¤rdet fÃ¶r SOA 'refresh' ({refresh}).LÃ¤gsta och hÃ¶gsta vÃ¤rde fÃ¶r SOA "minimum"VÃ¤rdet fÃ¶r SOA 'minimum' ({minimum}) ligger inom det rekommenderade spannet ({lowest_minimum} - {highest_minimum}).SOA-postens 'minimum'-vÃ¤rde ({minimum}) Ã¤r hÃ¶gre Ã¤n rekommenderat ({highest_minimum}).SOA-postens 'minimum'-vÃ¤rde ({minimum}) Ã¤r lÃ¤gre Ã¤n rekommenderat ({lowest_minimum}).SOA MNAME ('{mname}') har en CNAME-post.SOA MNAME '{mname}' har ingen CNAME-post.Minsta vÃ¤rde fÃ¶r SOA "refresh"SOA-postens 'refresh'-vÃ¤rde ({refresh}) Ã¤r minst lika hÃ¶gt som det lÃ¤gsta rekommenderade vÃ¤rdet ({required_refresh}).'refresh'-vÃ¤rdet i SOA-posten ({refresh}) Ã¤r hÃ¶gre Ã¤n SOA-postens 'retry'-vÃ¤rde ({retry}).SOA-postens 'refresh'-vÃ¤rde ({refresh}) Ã¤r lÃ¤gre Ã¤n rekommenderat ({required_refresh}).SOA-postens 'refresh'-vÃ¤rde ({refresh}) Ã¤r lÃ¤gre Ã¤n dess 'retry'-vÃ¤rde ({retry}).SOA "retry" minst en timmeSOA "retry" lÃ¤gre Ã¤n "refresh"'retry'-vÃ¤rdet i SOA-posten ({retry}) Ã¤r minst lika hÃ¶gt som det lÃ¤gsta rekommenderade vÃ¤rdet ({required_retry}).SOA-postens 'retry'-vÃ¤rde ({retry}) Ã¤r lÃ¤gre Ã¤n rekommenderat ({required_retry}).SOA MNAME '{domain}' har domÃ¤ndelen '{label}' med bindestreck i position 3 och 4 utan att bÃ¶rja med IDN-prefixet 'xn--'.SOA MNAME '{domain}' har tillÃ¥tet format.SOA MNAME '{domain}' Ã¤r i en helnumerisk TLD ({tld}).Samma SOA MNAME Ã¶veralltNamnservernamnet i SOA MNAME Ã¤r ".", vilket normalt betyder "ingen server". HÃ¤mtad frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".Namnservern "{nsname}" angiven i SOA MNAME kan inte slÃ¥s upp till en IP-adress.Namnservern "{nsname}" angiven i SOA MNAME finns inte som NS-post i zonen.Namnservern "{nsname}" angiven i SOA MNAME slÃ¥s upp till IP-adress fÃ¶r "localhost ({ns_ip}).Namnservern "{ns}" angiven som SOA MNAME besvarar inte en SOA-frÃ¥ga.Namnservern "{ns}" angiven i SOA MNAME svarar med den ovÃ¤ntade svarskoden (RCODE) "{rcode}" pÃ¥ en SOA-frÃ¥ga.Namnservern "{ns}" angiven som SOA MNAME Ã¤r inte auktoritativ fÃ¶r zonen.Namnservern "{ns}" angiven som SOA MNAME besvarar en SOA-frÃ¥ga med ett svar utan SOA-poster i svarssektionen.Namnservernamnet i SOA MNAME Ã¤r "localhost" vilket Ã¤r ogiltigt. HÃ¤mtad frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".Namnservrarna "{ns_list}" i SOA MNAME verkar vara masternamnservrar.Namnservrarna "{ns_list}" i SOA MNAME ger inte hÃ¶gsta SOA SERIAL fÃ¶r zonen (fÃ¶rvÃ¤ntat "{soaserial}" men faktiskt "{soaserial_list}").Samma SOA RNAME Ã¶veralltNamnet i SOA MNAME ska inte vara ett aliasSamma SOA Serial Ã¶veralltSamma tidsinstÃ¤llningar i SOA Ã¶veralltValidering av SPF-policyKonsekvent kÃ¤lladressNS-uppsÃ¤ttningen "{nsname_list}" hittades pÃ¥ fÃ¶ljande uppsÃ¤ttning namnservrar: {servers}.SOA-serienumret {serial} hittades pÃ¥ fÃ¶ljande uppsÃ¤ttning namnservrar: {ns_list}.SOA-tidsparametrarna (REFRESH={refresh}, RETRY={retry}, EXPIRE={expire}, MINIMUM={minimum}) hittades pÃ¥ fÃ¶ljande uppsÃ¤ttning namnservrar: {ns_list}.{count} olika 'SOA MNAME' hittades.Namnservern '{server}' skickade {keys} DNSKEY-poster och {sigs} RRSIG-poster.Namnservern '{server}' skickade {keys} DNSKEY-poster, och {sigs} RRSIG-poster.Signerad dotterzon hittades pÃ¥ namnservrarna med IP-adresserna "{ns_ip_list}".En del namnservrar saknar DNSSEC-stÃ¶d eller Ã¤r felkonfigurerade. Information hÃ¤mtad frÃ¥n: "{ns_list}".Vissa namnservrar returnerar MX-poster, medans andra inte gÃ¶r det.NÃ¤tÃ¥tkomst Ã¶ver TCPTEST_CASE_END {testcase}.TEST_CASE_START {testcase}.Test av tillgÃ¤nglighet fÃ¶r zonÃ¶verfÃ¶ring (AXFR)Test av komplett anvÃ¤ndning av DNSSEC-algoritmerTest med avkortat ("truncated") svar pÃ¥ frÃ¥ga med EDNSTest med odefinierad EDNS-versionTest med odefinierad OPTION-CODE i EDNSTest med odefinierad EDNS-flaggaTest av stÃ¶d fÃ¶r EDNS0Den testade zonen Ã¤r rotzonen, men ingen undelegated DS har lÃ¤mnats. DS-test utfÃ¶rs dÃ¤rfÃ¶r inte.Zonen Ã¤r undelegated men saknar undelegated DS-post, dÃ¤rfÃ¶r utfÃ¶rs inget DS-test.Test att skiftlÃ¤get i QNAME bibehÃ¥lls i "Question section"Test att skiftlÃ¤ge i QNAME ignoreras fÃ¶r frÃ¥ganAS-informationen fÃ¶r IP-adress "{ns_ip}" Ã¤r "{data}".Funktionell test av otestbart namnCDNSKEY RRset Ã¤r en blandning av poster av typen "delete" och andra poster. HÃ¤mtat frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".CDNSKEY RRset har inte signerats av den DNSKEY-post som CDNSKEY-posten med "key tag" {keytag} refererar till. HÃ¤mtat frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".CDNSKEY RRset har inte signerats av en DNSKEY-post som nÃ¥gon DS-post refererar till. HÃ¤mtat frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".CDNSKEY RRset Ã¤r inte signerad. HÃ¤mtad frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".CDNSKEY RRset Ã¤r signerad av RRSIG-post med "key tag" {keytag} men den stÃ¤mmer inte med nÃ¥gon DNSKEY-post. HÃ¤mtad frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".CDNSKEY RRset Ã¤r signerat av en RRSIG-post med "key tag" {keytag}, men den stÃ¤mmer inte med den DNSKEY-post som har samma "key tag". HÃ¤mtad frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".CDNSKEY-posten med "key tag" {keytag} stÃ¤mmer inte med nÃ¥gon DNSKEY-post. HÃ¤mtad frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}"CDNSKEY-posten med "key tag" {keytag} har inte SEP-flaggan (bit 15) satt. HÃ¤mtad frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}"CDNSKEY-posten med "key tag" {keytag} har inte "Zone Key"-flaggan (bit 7) satt. HÃ¤mtad frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}.CDS RRset Ã¤r en blandning av poster av typen "delete" och andra poster. HÃ¤mtat frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".CDS RRset har inte signerats av den DNSKEY-post som CDS-posten med "key tag" {keytag} refererar till. HÃ¤mtat frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".CDS RRset har inte signerats av en DNSKEY-post som nÃ¥gon DS-post refererar till. HÃ¤mtat frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".CDS RRset Ã¤r inte signerad. HÃ¤mtad frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".CDS RRset Ã¤r signerad av en RRSIG-post med "key tag" {keytag} men den stÃ¤mmer inte med nÃ¥gon DNSKEY-post. HÃ¤mtad frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".CDS RRset Ã¤r signerat med en RRSIG-post med "key tag" {keytag}, men den stÃ¤mmer inte med den DNSKEY-posten som har samma "key tag". HÃ¤mtad frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".CDS-posten med "key tag" {keytag} stÃ¤mmer inte med nÃ¥gon DNSKEY-post. HÃ¤mtad frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".CDS-posten med "key tag" {keytag} motsvarar en DNSKEY-post som inte har SEP-flaggan (bit 15) satt. HÃ¤mtad frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".CDS-posten med "key tag" {keytag} motsvarar en DNSKEY-post som inte har "Zone Key"-flaggan (bit 7) satt. HÃ¤mtad frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".DNS-svaret innehÃ¥ller en odefinierad OPTION-CODE i EDNS. HÃ¤mtad frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".DNS-svaret, pÃ¥ en DNS-frÃ¥ga med odefinierad OPTION-CODE i EDNS, innehÃ¥ller ingen EDNS frÃ¥n namnservrarna "{ns_ip_list}".DNS-svaret, pÃ¥ en DNS-frÃ¥ga med odefinierad OPTION-CODE i EDNS, innehÃ¥ller inte den fÃ¶rvÃ¤ntade SOA-posten i "Answer section" frÃ¥n namnservrarna "{ns_ip_list}".DNS-svaret, pÃ¥ en DNS-frÃ¥ga med odefinierad OPTION-CODE i EDNS, har den ovÃ¤ntade svarskoden (RCODE) "{rcode}" frÃ¥n namnservrarna "{ns_ip_list}".DNS-svaret, pÃ¥ en DNS-frÃ¥ga med odefinierad OPTION-CODE i EDNS, Ã¤r ovÃ¤ntat icke-auktoritativt frÃ¥n namnservrarna "{ns_ip_list}".DNSKEY "RRset" har inte signerats med nÃ¥gon DNSKEY-post som nÃ¥gon DS-post refererar till. HÃ¤mtat frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".DNSKEY RRset Ã¤r inte signerat av kryptoalgoritm {algo_num} ({algo_mnemo}) som finns med i DNSKEY RRset. HÃ¤mtad frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".DNSKEY RRset har inte signerats av den DNSKEY-post som CDNSKEY-posten med "key tag" {keytag} refererar till. HÃ¤mtat frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".DNSKEY RRset har inte signerats av den DNSKEY-post som CDS-posten med "key tag" {keytag} refererar till. HÃ¤mtat frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".DNSKEY RRset Ã¤r inte signerat av DNSKEY-posten med "key tag" {keytag} som DS-posten refererar till. HÃ¤mtad frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".DNSKEY RRset Ã¤r inte signerat, vilket Ã¤r ovÃ¤ntat. HÃ¤mtad frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".DNSKEY RRset Ã¤r signerat med en RRSIG-post med "key tag" {keytag} som inte kan valideras med motsvarande DNSKEY-post. HÃ¤mtad frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".DNSKEY RRset Ã¤r signerat med en RRSIG-post med "key tag" {keytag} som inte stÃ¤mmer med nÃ¥gon DNSKEY-post. HÃ¤mtad frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".DNSKEY-posten med "key tag" {keytag} som DS-posten refererar till finns inte i DNSKEY RRset. HÃ¤mtad frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".DNSKEY-posten med "key tag" {keytag} anvÃ¤nder kryptoalgoritm {algo_num} ("{algo_descr}", {algo_mnemo}), som inte Ã¤r avsedd fÃ¶r zonsignering. HÃ¤mtades frÃ¥n namnservrarna "{ns_list}".DNSKEY-posten med "key tag" {keytag} anvÃ¤nder kryptoalgoritm {algo_num} ("{algo_descr}", {algo_mnemo}). HÃ¤mtades frÃ¥n namnservrarna "{ns_list}".DNSKEY med "keytag" {keytag} anvÃ¤nder ett algoritmnummer {algo_num} fÃ¶r "privat" anvÃ¤ndning. HÃ¤mtades frÃ¥n namnservrar: "{ns_list}".DNSKEY-posten med "key tag" {keytag} anvÃ¤nder den utfasade kryptoalgoritmen {algo_num} ("{algo_descr}", {algo_mnemo}) pÃ¥ namnservrarna "{ns_list}".DNSKEY med "keytag" {keytag} anvÃ¤nder ett algoritmnummer ({algo_num}) som Ã¤r reserverat fÃ¶r framtiden. HÃ¤mtades frÃ¥n namnservrarna: "{ns_list}".DNSKEY med "keytag" {keytag} anvÃ¤nder ett algoritmnummer ({algo_num}) som inte Ã¤r tilldelat nÃ¥got. HÃ¤mtades frÃ¥n namnservrarna: "{ns_list}".DNSKEY-posten med "key tag" {keytag} anvÃ¤nder kryptoalgoritm {algo_num} ("{algo_descr}", {algo_mnemo}), vilken inte rekommenderas. HÃ¤mtades frÃ¥n namnservrarna "{ns_list}".DS-posten stÃ¤mmer inte med DNSKEY-posten med samma "key tag" {keytag} nÃ¤r det gÃ¤ller kryptoalgoritm eller "digest". HÃ¤mtad frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".DS-posten med "key tag" {keytag} skapades med hashfunktionen ("digest algorithm") {ds_algo_num} ({ds_algo_descr}) som Ã¤r utfasad. HÃ¤mtades frÃ¥n fÃ¶ljande namnservrar fÃ¶r moderzonen: "{ns_list}".DS-posten med "key tag" {keytag} skapades med hashfunktionen {ds_algo_num} ({ds_algo_descr}) som inte Ã¤r avsedd fÃ¶r DS-poster. HÃ¤mtades frÃ¥n fÃ¶ljande namnservrar fÃ¶r moderzonen: "{ns_list}".DS-posten med "keytag" {keytag} skapades med hashfunktionen ("digest algorithm") {ds_algo_num} som Ã¤r fÃ¶r "privat" anvÃ¤ndning. HÃ¤mtades frÃ¥n fÃ¶ljande namnservrar fÃ¶r moderzonen: "{ns_list}".DS-posten med "key tag" {keytag} skapades med kryptoalgoritm {ds_algo_num}. Algoritmnumret Ã¤r undanlagt fÃ¶r framtida behov. HÃ¤mtades frÃ¥n fÃ¶ljande namnservrar fÃ¶r moderzonen: "{ns_list}".DS-posten med "keytag" {keytag} skapades med en hashfunktion med algoritmnummer {ds_algo_num}. Algoritmnumret Ã¤r inte tilldelat nÃ¥gon hashfunktion. HÃ¤mtades frÃ¥n fÃ¶ljande namnservrar fÃ¶r moderzonen "{ns_list}".Namnservrarna ger olika uppsÃ¤ttningar av MX RRset.NS RRset Ã¤r inte signerat av kryptoalgoritm {algo_num} ({algo_mnemo}) som finns med i DNSKEY RRset. HÃ¤mtad frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".En NS-post mÃ¥ste ha ett giltigt namn ("hostname")RRSIG-signaturen fÃ¶r NSEC3-posten kan inte verifieras. HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".RRSIG-signaturen med "key tag" {keytag} fÃ¶r NSEC-posten kan inte verifieras. HÃ¤mtad frÃ¥n namnservrarna med IP-adresserna "{ns_list}".Signaturen (RRSIG) med taggen {keytag} fÃ¶r NSEC-posten har lÃ¶pt ut. HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".RRSIG-signaturen med "key tag" {keytag} fÃ¶r NSEC-posten Ã¤r Ã¤nnu inte giltig. HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".Signaturen (RRSIG) med taggen {keytag} fÃ¶r NSEC3-posten kan inte verifieras. HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".RRSIG-signaturen med "key tag" {keytag} fÃ¶r NSEC3-posten har lÃ¶pt ut. HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".RRSIG-signaturen med "key tag" {keytag} fÃ¶r NSEC3-posten Ã¤r Ã¤nnu inte giltig. HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".Adressen i SOA RNAME ({rname}) Ã¤r giltig enligt RFC822.MaildomÃ¤nen frÃ¥n 'SOA RNAME' ({domain}) kan inte slÃ¥s upp till en mailserver med IP-adress.MaildomÃ¤nen frÃ¥n 'SOA RNAME' ({domain}) slÃ¥s upp till ett alias (CNAME).MaildomÃ¤nen frÃ¥n 'SOA RNAME' ({domain}) slÃ¥s upp till en IP-adress pÃ¥ "localhost" ({localhost}).SOA RRset Ã¤r inte signerat av kryptoalgoritm {algo_num} ({algo_mnemo}) som finns med i DNSKEY RRset. HÃ¤mtad frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".SOA RRset Ã¤r inte signerat, vilket Ã¤r ovÃ¤ntat. HÃ¤mtad frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".SOA RRset Ã¤r signerat med en RRSIG-post med "key tag" {keytag} som inte kan valideras med motsvarande DNSKEY-post. HÃ¤mtad frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".SOA RRset Ã¤r signerat med en RRSIG-post med "key tag" {keytag} som inte stÃ¤mmer med nÃ¥gon DNSKEY-post. HÃ¤mtad frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".SPF-policyn fÃ¶r {domain} innehÃ¥ller ett syntaxfel. HÃ¤mtad frÃ¥n fÃ¶ljande namnservrar: "{ns_list}".SPF-policyn fÃ¶r {domain} har korrekt syntax.Aliaset fÃ¶r "{domain}" Ã¤r inte konsekvent mellan olika namnservrar.Det finns inga mailservrar fÃ¶r domÃ¤nen (ingen MX).Dotterzonen Ã¤r osignerad, men moderzonen har DS-poster.DomÃ¤nnamnet mÃ¥ste ha en moderzonDomÃ¤nnamnet mÃ¥ste ha Ã¥tminstone en fungerande namnserverFÃ¶rsÃ¶ksdelegering av domÃ¤nen '{domain}' innehÃ¥ller en namnservern '{nsname}' som inte kan slÃ¥s upp till nÃ¥gon IP-adress.FÃ¶rsÃ¶ksdelegering av domÃ¤nen '{domain}' innehÃ¥ller en namnservern '{nsname}' som krÃ¤ver en glue-post (krÃ¤ver IP-adress).FÃ¶ljande namnservrar tillhÃ¶r samma IPv4-prefix ({ip_prefix}): "{ns_list}".FÃ¶ljande namnservrar tillhÃ¶r samma IPv6-prefix ({ip_prefix}): "{ns_list}".FÃ¶ljande namnserver eller namnservrar tillhÃ¶r egna IPv4-prefix: "{ns_list}".FÃ¶ljande namnserver eller namnservrar tillhÃ¶r egna IPv6-prefix: "{ns_list}".FÃ¶ljande namnserver eller namnservrar svarar inte eller svarar med SERVFAIL pÃ¥ fÃ¶rfrÃ¥gan om programvaruversion: "{query_name}". Namnservrar: "{ns_list}".FÃ¶ljande namnservrar returnerar inte CH-klassposter vid en CH-klassfÃ¶rfrÃ¥gan. Namnservrar: "{ns_list}".FÃ¶ljande namnserver eller namnservrar avslÃ¶jar inte programvaruversionen. Namnservrar: "{ns_list}".FÃ¶ljande namnservrar svarar pÃ¥ fÃ¶rfrÃ¥gan om programvaruversion ("{query_name}") med strÃ¤ngen "{string}". Namnservrar: "{ns_list}".FÃ¶ljande namnservrar tillhandahÃ¥ller inte DS-poster eller Ã¤r felkonfigurerade. HÃ¤mtades frÃ¥n fÃ¶ljande namnservrar fÃ¶r moderzonen: "{ns_list}".FÃ¶ljande namnservrar lÃ¤mnar inget svar pÃ¥ DNSKEY-frÃ¥ga med DO-bit satt: "{ns_list}".FÃ¶ljande namnservrar stÃ¶der inte DNSSEC eller Ã¤r felkonfigurerade. Testning av NSEC och NSEC3 har hoppats Ã¶ver fÃ¶r dessa servrar. HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".FÃ¶ljande namnservrar stÃ¶der inte DNSSEC eller Ã¤r felkonfigurerade. Testning av NSEC3 har hoppats Ã¶ver fÃ¶r dessa servrar. HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".FÃ¶ljande namnservrar anvÃ¤nder inte NSEC3, medan andra gÃ¶r det. Testning av NSEC3 har hoppats Ã¶ver fÃ¶r dessa servrar. HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".FÃ¶ljande namnservrar ger ett icke-auktoritativa svar vid DNSKEY-frÃ¥gor (DO-bit satt): "{ns_list}".FÃ¶ljande namnservrar ger ett svar pÃ¥ NSEC-fÃ¶rfrÃ¥gan som inte fÃ¶ljer standarden (NSEC-post i "authority" istÃ¤llet fÃ¶r i "answer"). HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".FÃ¶ljande namnservrar returnerar DNSKEY-data fÃ¶r den signerade dotterzonen: "{ns_list}".Dessa namnservrar returnerade RCODE {rcode} istÃ¤llet fÃ¶r fÃ¶rvÃ¤ntade NOERROR vid DNSKEY-frÃ¥ga (DO-bit satt): "{ns_list}".FÃ¶ljande namnservrar svarar utan DNSKEY-poster (osignerad zon): "{ns_list}".FÃ¶ljande namnservrar returnerade flera SPF-policys: "{ns_list}".FÃ¶ljande namnservrarna nedan gav samma SPF-policy: "{ns_list}".FÃ¶ljande namnservrar svarade problemfritt pÃ¥ AAAA-frÃ¥gor : {ns_list}.FÃ¶ljande namnservernamn kunde inte slÃ¥s upp till nÃ¥gon IP-adresser: {nsname_list}.FÃ¶ljande namnservrar stÃ¶der EDNS0: {ns_list}.FÃ¶ljande namnservrar fÃ¶r moderzonen returnerar DS-data fÃ¶r dotterzonen: "{ns_list}".FÃ¶ljande namnservrar fÃ¶r moderzonen svarar utan DS-post fÃ¶r dotterzonen: "{ns_list}".FÃ¶ljande namnservrar svarar inte pÃ¥ NSEC-fÃ¶rfrÃ¥gan. HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".FÃ¶ljande namnservrar ger ett felaktigt svar pÃ¥ NSEC-fÃ¶rfrÃ¥gan. HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".FÃ¶ljande namnservrar har NSEC3-itererationsvÃ¤rdet instÃ¤llt pÃ¥ noll (rekommenderat vÃ¤rde). HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".FÃ¶ljande namnservrar har opt-out fÃ¶r NSEC3 inaktiverat (rekommenderat vÃ¤rde). HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".FÃ¶ljande namnservrar har opt-out fÃ¶r NSEC3 aktiverat. HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".FÃ¶ljande namnservrar har opt-out fÃ¶r NSEC3 aktiverat. Rekommenderad praxis Ã¤r att inaktivera opt-out. HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".FÃ¶ljande namnservrar anvÃ¤nder ett giltigt tomt salt i NSEC3. HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".FÃ¶ljande namnservrar anvÃ¤nder en giltig hash-algoritm i NSEC3. HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".FÃ¶ljande servrar svarar med ett icke-tomt salt i NSEC3 ({int} oktetter). Rekommendationen Ã¤r att anvÃ¤nda ett tomt salt. HÃ¤mtat frÃ¥n namnservrar "{ns_list}".FÃ¶ljande servrar svarar med en NSEC3-post dÃ¤r en odefinierad flagga Ã¤r satt (bit {int}). HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".FÃ¶ljande namnservrar rapporterar en ogiltig hash-algoritm fÃ¶r NSEC3 ({algo_num}). HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".FÃ¶ljande namnservrar rapporterar NSEC3-itererationsvÃ¤rdet {int}. Rekommenderad praxis Ã¤r att sÃ¤tta detta vÃ¤rde till 0. HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".Namnservrarna fÃ¶r moderzonen "{domain_parent}" ger inte konsekvent delegering av "{domain_child}". Information frÃ¥n namnservrarna "{ns_list}".Moderzonen kan inte faststÃ¤llas av namnservrarna "{ns_list}".Moderzonen kan inte faststÃ¤llas.Moderzonen innehÃ¥ller DS-data fÃ¶r den signerade dotterzonen.Moderzonen saknar DS-data fÃ¶r den signerade dotterzonen.Moderzonen Ã¤r "{domain}" vilket har bekrÃ¤ftats av namnservrarna "{ns_list}".Moderzonen tillhandhÃ¥ller ingen DS-post fÃ¶r dotterzonen. HÃ¤mtades frÃ¥n fÃ¶ljande namnservrar fÃ¶r moderzonen: "{ns_list}".Den returnerade NSEC-posten har ett Ã¤garnamn som inte Ã¤r zonens apex, vilket Ã¤r ovÃ¤ntat. HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".Den returnerade NSEC3-posten stÃ¤mmer inte Ã¶verens med zonens namn, vilket Ã¤r ovÃ¤ntat. HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".Den returnerade NSEC3PARAM-posten har ett ovÃ¤ntat Ã¤garnamn som inte Ã¤r zonens apex. HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".Servern svarade med DNSKEY men inte med fÃ¶rvÃ¤ntad NSEC- eller NSEC3-post. HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".Minsta mÃ¶jliga giltiga hÃ¤nvisningspaket Ã¤r {size} byte, vilket Ã¤r stÃ¶rre Ã¤n 512 byte (stÃ¶sta tillÃ¥tna).Minsta mÃ¶jliga giltiga hÃ¤nvisningspaket Ã¤r {size} byte. 512 byte Ã¤r den Ã¶vre grÃ¤nsen.Zonen "{domain}" hittades.Zonen anvÃ¤nder inte NSEC3. Test av NSEC3 har hoppats Ã¶ver. HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".Zonen har NSEC-poster. HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".Zonen har NSEC3-poster. HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".Zonen har en "Null MX" blandat med andra MX-poster.Zonen har en "Null MX" med ett prioritet som Ã¤r icke-noll.Zonen Ã¤r en toppdomÃ¤n (TLD) och har ett ovÃ¤ntat MX RRset (icke-Null MX).Zonen Ã¤r inkonsekvent nÃ¤r det gÃ¤ller NSEC och NSEC3. NSEC-poster kommer frÃ¥n namnservrarna "{ns_list_nsec}". NSEC3-poster kommer frÃ¥n namnservrarna "{ns_list_nsec3}".Zonen Ã¤r osignerad eller felaktigt DNSSEC-signerad. DNSKEY-test gÃ¥r ej att utfÃ¶ra. Information hÃ¤mtad frÃ¥n "{ns_list}".Zonen Ã¤r inte DNSSEC-signerad eller inte korrekt DNSSEC-signerad. Test av NSEC och NSEC3 har hoppats Ã¶ver. HÃ¤mtad frÃ¥n namnservrar "{ns_list}".Zonen Ã¤r inte DNSSEC-signerad eller inte korrekt DNSSEC-signerad. Test av NSEC3 har hoppats Ã¶ver. HÃ¤mtad frÃ¥n namnservrar "{ns_list}".Zonen Ã¤r inte DNSSEC-signerad.Zonen Ã¤r DNSSEC-signerad.Zonen svarar med bÃ¥de NSEC och NSEC3, dÃ¤r endast en fÃ¶rvÃ¤ntades. HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".Det finns en DS-post med "keytag" {keytag}. Det saknas en DS-post med algorithm 2 (SHA-256). HÃ¤mtades frÃ¥n namnservrar fÃ¶r moderzonen: "{ns_list}".Det finns ingen DNSKEY-post som matchar RRSIG-signaturen med "key tag" {keytag} fÃ¶r NSEC-posten. HÃ¤mtad frÃ¥n namnservrarna med IP-adresserna "{ns_list}".Det finns ingen DNSKEY-post som motsvarar signaturen (RRSIG) med taggen {keytag} fÃ¶r NSEC3-posten. HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".Det finns ingen verifierbar signatur (RRSIG) fÃ¶r NSEC-posten. HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".Det finns ingen delegering (inga namnservrar) fÃ¶r "{domain}" vilket betyder att den inte finns som DNS-zon.Inga otillÃ¥tna @-tecken hittades i SOA RNAME ({rname}).PÃ¥ en DNS-frÃ¥ga med odefinierad OPTION-CODE i EDNS kommer det inget svar frÃ¥n namnservrarna "{ns_ip_list}".Det finns inga giltiga DNSKEY-poster som pekas ut frÃ¥n nÃ¥gon av DS-posterna. HÃ¤mtad frÃ¥n namnservrarna med IP-adresserna "{ns_ip_list}".Det finns inga Ã¥tkomliga namnservrar fÃ¶r "{domain}" vilket betyder att domÃ¤nen (zonen) inte kan nÃ¥s.Det fÃ¥r inte finnas dubbla bindestreck ("--") i position 3 och 4 i domÃ¤nnamnsdelDetta Ã¤r ett test av en icke-delegerad domÃ¤n, sÃ¥ att faststÃ¤lla moderzonen ignoreras.Detta Ã¤r ett test av rotzonen som inte har nÃ¥gon moderzon.Kontrollera ifall auktoritativa namnservrar svarar med hÃ¤nvisning till rotNÃ¤tÃ¥tkomst Ã¶ver UDPOvÃ¤ntad DNS-post i svarsdelen pÃ¥ en NSEC-fÃ¶rfrÃ¥gan. HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".OvÃ¤ntad DNS-post i svarssektionen pÃ¥ en NSEC3PARAM-fÃ¶rfrÃ¥gan. HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".OvÃ¤ntat vÃ¤rde, "{rcode}", pÃ¥ svarskoden (RCODE) i svar pÃ¥ MX-frÃ¥ga till namnservrar "{ns_ip_list}".OvÃ¤ntat eller felaktigt svarspaket frÃ¥n "{ns}".OvÃ¤ntat svar pÃ¥ fÃ¶rfrÃ¥gan fÃ¶r "{query_name}" med fÃ¶rfrÃ¥gningstyp "{rrtype}" till "{ns}".Osignerad dotterzon hittades pÃ¥ namnservrarna med IP-adresserna "{ns_ip_list}".Tester fÃ¶r hÃ¤nvisning till moderzon stryks fÃ¶r root-zonen (det finns ingen moderzon).AnvÃ¤nder version {version} av modulen '{module}'.AnvÃ¤nder version {version} av modulen '{name}'.AnvÃ¤nder version {version} av Zonemasters testmotor.Giltig RRSIG-post fÃ¶r DNSKEY-posternaValidera CDNSKEY-posterValidera CDS-posterValidera tillit frÃ¥n DS-poster till CDS- och CDNSKEY-posterVerifiera hantering av RRSIG-poster i "Additional Section"Verifiera NSEC3-parametrarAlla servrar svarar inte konsekvent nÃ¤r fÃ¶rfrÃ¥gade om '{domain}' med olika skiftlÃ¤gen och posttypen '{type}'.Alla servrar svarar konsekvent nÃ¤r fÃ¶rfrÃ¥gade om '{domain}' med olika skiftlÃ¤gen och posttypen '{type}'.Namnservern "{ns}" svarar ingenting nÃ¤r den fÃ¥r frÃ¥gan om '{domain}' med posttypen '{type}'.Namnservern "{ns}" ger olika svarskoder (RCODE) -- "{rcode1}" resp. "{rcode2}" -- nÃ¤r frÃ¥gedomÃ¤nen Ã¤r {query1} resp. {query2} fÃ¶r posttypen "{type}".Namnservern "{ns}" ger olika svar nÃ¤r frÃ¥gan Ã¤r '{query1}' resp. '{query2}' fÃ¶r posttypen '{type}'.Namnservern "{ns}" ger samma svarskod (RCODE), "{rcode}", nÃ¤r frÃ¥gedomÃ¤nen Ã¤r {query1} resp. {query2} fÃ¶r posttypen "{type}".Namnservern "{ns}" ger samma svar nÃ¤r frÃ¥gan Ã¤r '{query1}' resp. '{query2}' fÃ¶r posttypen '{type}'.Felaktigt Ã¤garnamn ("{domain}") pÃ¥ SOA-posten i NODATA-svar med NSEC. HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".Felaktigt Ã¤garnamn ("{domain}") pÃ¥ SOA-posten i NODATA-svar med NSEC3. HÃ¤mtad frÃ¥n namnservrarna "{ns_list}".Zonen har NSEC eller NSEC3