arXivDaily arXiv每日学术速递 周一至周五更新
arXiv 2003.13319cs.NI
收藏

一种扩展动态名称服务的分析--DNS与RFC 6891兼容性的讨论

Analysis of an Extension Dynamic Name Service -- A discussion on DNS compliance with RFC 6891

Ivica Stipovic

摘要:

域名服务(DNS)解析是一种将联网设备的符号名称解析为其对应的互联网协议(IP)地址的机制。随着描述DNS服务定义扩展的文档的出现,DNS实现将需要遵守一些修改的DNS行为变得越来越明显。一个这样的修改是DNS继续使用用户数据报协议(UDP)来传输长于512字节的DNS有效载荷。在扩展DNS(EDNS)规范出现之前,如果响应有效载荷大于512字节,DNS服务器将从UDP切换到传输控制协议(TCP)。有了新的EDNS功能,要求DNS应答将继续以UDP数据报的形式提供应答,即使应答大于512字节。据作者所知,目前还没有学术文章涉及根据EDNS规范评估DNS服务器。本文探讨了一些流行的互联网域名的公共DNS服务器的兼容性水平。它还探讨了一些当代DNS实现的行为,如Microsoft Windows 2012,2016和2019以及基于Linux的BIND与EDNS的关系。

英文摘要:

Domain Name Service (DNS) resolution is a mechanism that resolves the symbolic names of networked devices to their corresponding Internet Protocol (IP) address. With the emergence of the document that describes an extension to a DNS service definition, it was becoming apparent that DNS implementations will need to comply with some modified DNS behaviour. One such modification is that DNS continues to use the User Datagram Protocol (UDP) to transmit DNS payloads that are longer than 512 bytes. Until the emergence of the Extension DNS (EDNS) specification, DNS servers would switch over from UDP to Transmission Control Protocol (TCP) if the response payload was larger than 512 bytes. With the new EDNS capability, it was required that DNS replies would continue to provide responses as UDP datagrams even though the response was larger than 512 bytes. To the author's best knowledge, there are no academic articles dealing with the assessment of the DNS servers against EDNS specification. This paper examines the level of compatibility for a number of public DNS servers for some popular internet domains. It also explores behaviour of some contemporary DNS implementations such as Microsoft Windows 2012, 2016 and 2019 as well as Linux-based BIND in regards to the EDNS.

机构、总结、中文摘要均由AI分析而来,可能存在错误,请以论文正文为准。

↑