DNS flag day 2020 - 版本历史

2024年5月22日 (三) 04:19 Admin

2024-05-22T04:19:25Z

@@ 第106行： / 第106行： @@
 Knot DNS
 <code>
 server:
@@ 第142行： / 第143行： @@
 The configuration above will have no visible effect if everything works correctly. Some queries will fail to resolve if the TCP transport is not available.

Admin：/* How to test? */

2024-05-22T04:18:42Z

How to test?

←上一版本		2024年5月22日 (三) 12:18的版本
第97行：		第97行：
	<code>		<code>
	options {		options {

	edns-udp-size 1232;		edns-udp-size 1232;

	max-udp-size 1232;		max-udp-size 1232;

	};		};
	</code>		</code>
第110行：		第113行：

	Knot Resolver		Knot Resolver
			<code>
	net.bufsize(1232)		net.bufsize(1232)
			</code>

	PowerDNS Authoritative		PowerDNS Authoritative

Admin：/* How to test? */

2024-05-22T04:18:16Z

How to test?

←上一版本		2024年5月22日 (三) 12:18的版本
第95行：		第95行：
	BIND		BIND

			<code>
	options {		options {

	edns-udp-size 1232;		edns-udp-size 1232;

	max-udp-size 1232;		max-udp-size 1232;

	};		};
			</code>

	Knot DNS		Knot DNS
			<code>
	server:		server:

	max-udp-payload: 1232		max-udp-payload: 1232
			</code>

	Knot Resolver		Knot Resolver

2024年5月22日 (三) 04:17 Admin

2024-05-22T04:17:33Z

@@ 第1行： / 第1行： @@
-It is important for DNS software vendors to comply with DNS standards, and to use a default EDNS buffer size (1232 bytes) that will not cause fragmentation on typical network links.
+= Contents =
 Relevant standards include <nowiki>RFC 7766</nowiki>, <nowiki>RFC 6891</nowiki> section 6.2.3. and <nowiki>RFC 6891</nowiki> section 6.2.4..
@@ 第7行： / 第78行： @@
 The motivation for this effort is described in IETF draft intarea-frag-fragile section 6.1 and IETF draft iab-protocol-maintenance.
 If you’re the owner of a domain or the operator of an authoritative DNS server, you can use our web-based testing tool to check your domains; you can find it above under Action: Authoritative DNS Operators.
@@ 第14行： / 第86行： @@
 You can also test by using the following CLI commands:
+ <code>$ dig +tcp @auth_IP yourdomain.example.
-$ dig +tcp @auth_IP yourdomain.example.
+ $ dig +tcp @resolver_IP yourdomain.example.
+ $ dig @resolver_IP test.knot-resolver.cz. TXT</code>
-$ dig +tcp @resolver_IP yourdomain.example.
+All DNS queries must be successful, and commands should return the same results both with and without the <code>+tcp</code> option.
 If you are a service provider, you can test your authoritative and recursive DNS services by configuring the default EDNS buffer size:

Admin：创建页面，内容为“DNS Software Vendors It is important for DNS software vendors to comply with DNS standards, and to use a default EDNS buffer size (1232 bytes) that will not cause fragmentation on typical network links. Relevant standards include RFC 7766, RFC 6891 section 6.2.3. and RFC 6891 section 6.2.4.. The motivation for this effort is described in IETF draft intarea-frag-fragile section 6.1 and IETF draft iab-protocol…”

2024-05-22T03:14:12Z

创建页面，内容为“DNS Software Vendors It is important for DNS software vendors to comply with DNS standards, and to use a default EDNS buffer size (1232 bytes) that will not cause fragmentation on typical network links. Relevant standards include <nowiki>RFC 7766</nowiki>, <nowiki>RFC 6891</nowiki> section 6.2.3. and <nowiki>RFC 6891</nowiki> section 6.2.4.. The motivation for this effort is described in IETF draft intarea-frag-fragile section 6.1 and IETF draft iab-protocol…”

新页面

DNS Software Vendors

It is important for DNS software vendors to comply with DNS standards, and to use a default EDNS buffer size (1232 bytes) that will not cause fragmentation on typical network links.

Relevant standards include <nowiki>RFC 7766</nowiki>, <nowiki>RFC 6891</nowiki> section 6.2.3. and <nowiki>RFC 6891</nowiki> section 6.2.4..

The motivation for this effort is described in IETF draft intarea-frag-fragile section 6.1 and IETF draft iab-protocol-maintenance.

How to test?

If you’re the owner of a domain or the operator of an authoritative DNS server, you can use our web-based testing tool to check your domains; you can find it above under Action: Authoritative DNS Operators.

Our web-based testing tool for clients and DNS resolver operators can be found above under Action: DNS Resolver Operators.

You can also test by using the following CLI commands:

$ dig +tcp @auth_IP yourdomain.example.

$ dig +tcp @resolver_IP yourdomain.example.

$ dig @resolver_IP test.knot-resolver.cz. TXT

All DNS queries must be successful, and commands should return the same results both with and without the +tcp option.

If you are a service provider, you can test your authoritative and recursive DNS services by configuring the default EDNS buffer size:

BIND

options {

edns-udp-size 1232;

max-udp-size 1232;

};

Knot DNS

server:

max-udp-payload: 1232

Knot Resolver

net.bufsize(1232)

PowerDNS Authoritative

udp-truncation-threshold=1232

PowerDNS Recursor

edns-outgoing-bufsize=1232

udp-truncation-threshold=1232

Unbound

server:

edns-buffer-size: 1232

NSD

server:

ipv4-edns-size: 1232

ipv6-edns-size: 1232

The configuration above will have no visible effect if everything works correctly. Some queries will fail to resolve if the TCP transport is not available.

DNS flag day 2020 - 版本历史

2024年5月22日 (三) 04:19 Admin

Admin：​/* How to test? */

Admin：​/* How to test? */

2024年5月22日 (三) 04:17 Admin

Admin：/* How to test? */

Admin：/* How to test? */