大网数据广告活动
服务器运维问答

DNS Flag Day: what action is needed for edns512tcp=reset error?

· 52CE 我爱测

Using the domain test at https://dnsflagday.net reports that our domains (hosted at several different DNS companies) all fail with this (note the edns512tcp=reset ): xxxxxxxxx.com. @98.124.243.3 (dns5.name-services.com.): dns=ok …

问题原文

原帖链接 · simpleuser · CC BY-SA 4.0

Using the domain test at https://dnsflagday.net reports that our domains (hosted at several different DNS companies) all fail with this (note the edns512tcp=reset):

xxxxxxxxx.com. @98.124.243.3 (dns5.name-services.com.): dns=ok edns=ok edns1=ok edns@512=ok ednsopt=ok edns1opt=ok do=ok ednsflags=ok docookie=ok edns512tcp=reset optlist=ok,nsid (pdns12.dns.sjl.prod.tucows.net)

The Following Tests Failed

    EDNS - over TCP Response (edns@512tcp)

    dig +vc +nocookie +norec +noad +edns +dnssec +bufsize=512 dnskey zone @server
    expect: NOERROR
    expect: OPT record with version set to 0
    See RFC5966 and See RFC6891

Codes

    ok - test passed.
    nsid - NSID supported [RFC5001].
    reset - TCP connection reset.

But there are no actions explained by the site, and web searches are not making this any clearer.

It seems to be saying it doesn't expect reset? dig shows the domains all reply with the following, which is required:

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags: do; udp: 1452

What is the DNS flag day tester trying to tell me is wrong? And is there anything I can do to fix it, or is it a problem with our authoritative DNS host?

已采纳解答

原帖链接 · Håkan Lindqvist · CC BY-SA 4.0

You don't specify your domain name, but using the command specified in the output that you quoted I get the same "connection reset" behavior that they complain about:

$ dig +vc +nocookie +norec +noad +edns +dnssec +bufsize=512 dnskey example.com @98.124.243.3
;; communications error to 98.124.243.3#53: connection reset
$

As noted in your ednscomp test output, what is expected in this particular test is:

expect: NOERROR
expect: OPT record with version set to 0

Ie, it expects a response with NOERROR status and an EDNS OPT pseudorecord with version 0 for this query.

The reported problem is specifically that your nameserver for whatever reason resets the connection instead of handling the query.


It is worth noting that the ednscomp test suite includes many tests, what you find detailed in the output are the tests that failed. Ie, the dig command above is in itself by no means a comprehensive test, it just corresponds to a particular test scenario where your nameserver fails.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2019-01-25)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 4.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。