论坛和问题报告
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
第 1 步:使用哪个系统?
Google 提供多种与 DNS 相关的产品和系统。请务必在适当的位置报告问题,以便与可以帮助您处理受影响系统的人员联系。
- 如果问题与解析
www.google.com
、www.youtube.com
或其他 Google 媒体资源(包括地理位置定位)有关,请执行以下操作:
- 如果您使用 Google Domains 的默认设置托管授权 DNS(并且其他人遇到了与您的域名相关的问题),请与 Squarespace 支持团队联系。Squarespace 于 2023 年 9 月 7 日收购了 Google Domains。
- 如果您发现 Google 公共 DNS 出现问题,但其他解析器没有问题,请继续阅读本页内容。
论坛
您可以向以下群组发布帖子,以及订阅这些论坛以获取有关 Google 公共 DNS 的最新动态,并讨论 Google 公共 DNS 和 DNS 基础架构的总体设计与实现:
报告问题
如果您在使用 Google 公共 DNS 时遇到问题,请先运行诊断测试。如果问题是 Google 公共 DNS 无法解析某个特定网域,请使用 intoDNS 和 DNSViz 检查是否存在域名服务器问题或 DNSSEC 问题。它们是大多数已报告问题的根源,您通常可以自行解决。
如果您无法解决问题,并且想要报告问题,则有以下两种选择:
无论哪种情况,请在报告中提供以下信息:
- 您遇到问题的日期和时间
- 您所在的位置
- 出现该问题的平台(例如 Mac、Windows、路由器等)
- 您遇到问题的主机名
- 问题是连续性还是间歇性的
- 指向工具的域名服务器诊断报告页面的链接
- 您在诊断测试过程中运行的命令的输出
有关问题跟踪器的详细信息
问题跟踪器中有两个部分面向公共 DNS。它们提供常见问题的模板,帮助您提供适当的信息供我们调查。
在任一组件中提交问题时,系统都会为该问题生成一个跟踪编号,并分配一名 Google 公共 DNS 工程师来处理该问题。您可以在问题更新时查看其历史记录和状态。如需有关问题跟踪器本身的更多帮助,请参阅其文档。
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-07-25。
[null,null,["最后更新时间 (UTC):2025-07-25。"],[[["\u003cp\u003eGoogle offers various DNS-related products; ensure you report issues to the correct platform for efficient resolution.\u003c/p\u003e\n"],["\u003cp\u003eFor problems with Google Public DNS specifically, run diagnostic tests and check domain health using online tools before reporting.\u003c/p\u003e\n"],["\u003cp\u003eUtilize the Issue Tracker for reporting security vulnerabilities or persistent issues with Google Public DNS after preliminary checks.\u003c/p\u003e\n"],["\u003cp\u003eWhen reporting an issue, provide detailed information like timestamps, location, platform, and diagnostic outputs for better assistance.\u003c/p\u003e\n"],["\u003cp\u003eGoogle's Issue Tracker allows you to track the status and history of your reported issue, ensuring transparency and follow-up.\u003c/p\u003e\n"]]],["To address DNS-related problems, first identify the affected system: Google properties, Google Domains, or Google Public DNS. ISPs should use Google's ISP Portal; others should contact their ISP. For Google Public DNS issues, run diagnostic tests and check domains with intoDNS and DNSViz. Report unresolved issues via the public-dns-discuss group or Issue Tracker, especially for security concerns. Issue Tracker has templates and requires including details like date, location, and hostnames.\n"],null,["# Discussion Groups and Issue Reporting\n\nStep one: which system?\n-----------------------\n\nGoogle has multiple DNS related products and systems. Be sure to report your\nproblems in the appropriate place, to reach someone who can help with the\naffected system.\n\n- If the problem relates to resolving `www.google.com`, `www.youtube.com`, or other Google properties in general, including geo-targeting:\n - If you operate an ISP use [Google's ISP Portal](https://isp.google.com/) to report the issue. ([Request access](https://isp.google.com/portalaccess) first, if necessary.) Or, read the [peering FAQ](https://peering.google.com/#/learn-more/faq) for more.\n - If you are a customer of an ISP please contact them, and ask them to reach out to Google as per the above bullet point.\n- If you used Google Domains' default settings to host your authoritative DNS (and others are having trouble with your domain), reach out to Squarespace support. [Google domains was acquired by Squarespace on September 7th, 2023](https://support.squarespace.com/hc/en-us/articles/17131164996365-About-the-Google-Domains-migration-to-Squarespace).\n- If you are observing a problem that happens with Google Public DNS but not other resolvers, continue reading this page.\n\nDiscussion groups\n-----------------\n\nYou can post and subscribe to the following groups to get updates on Google\nPublic DNS, and to discuss the design and implementation of Google Public DNS\nand DNS infrastructure in general:\n\n- [public-dns-discuss](//groups.google.com/group/public-dns-discuss)\n\n This is a forum for presenting and discussing new ideas, products, and\n initiatives that improve DNS infrastructure across the Internet.\n You can also use it to provide feedback on Google Public DNS features.\n This forum is moderated; your message only appears after it is approved.\n ***Do not use this to report security-related issues***;\n report them on the Issue Tracker as noted below.\n- [public-dns-announce](//groups.google.com/group/public-dns-announce)\n\n This is a read-only list where you can get information on new versions,\n releases, and features of Google Public DNS, as well as current status of\n the service.\n\nReporting issues\n----------------\n\nIf you encounter a problem with Google Public DNS, first please run the\n[diagnostic tests](/speed/public-dns/docs/troubleshooting).\nIf the issue is that a specific domain cannot be resolved by Google Public DNS,\ncheck it with [intoDNS](http://intodns.com/) and [DNSViz](http://dnsviz.net/) for name server or DNSSEC problems.\nThese cause most reported issues, and you can often solve them yourself.\n\nIf you are unable to resolve the problem, and would like to report an issue,\nyou have two options:\n\n- Post to [public-dns-discuss](//groups.google.com/group/public-dns-discuss).\n This shares your report publicly, and allows you to get feedback from other\n Google Public DNS users.\n If your report is security-related, ***do not post it here***;\n please use the Issue Tracker as noted below.\n\n- Open an issue in the [Issue Tracker](//issuetracker.google.com/bookmark-groups/77752).\n Please use this option to report any security-related issues,\n such as Google Public DNS returning results that should fail DNSSEC validation.\n See the [details](#issue_tracker) section below.\n\nIn either case, please include the following information in your report:\n\n- The date and time you encountered the problem\n- Your location\n- The platform on which you are noticing the problem (e.g. Mac, Windows, router, etc.)\n- The hostname(s) for which you are having a problem\n- Whether the problem is continuous or intermittent\n- The links to the tools' name server diagnosis report page\n- The output of the commands you ran in the [diagnostic tests](/speed/public-dns/docs/troubleshooting)\n\nDetails on Issue Tracker\n------------------------\n\nThere are two components for Public DNS in the Issue Tracker. They have\ntemplates for common problems to help you provide the right information for us\nto investigate.\n\n- [Public Trackers \\\u003e Public DNS](https://issuetracker.google.com/issues/new?component=191657)\n For issues with no confidential information. Available templates:\n\n - [Cache Flush](https://issuetracker.google.com/issues/new?component=191657&template=1021881): Problems flushing domain names.\n - [DNS-over-HTTPS](https://issuetracker.google.com/issues/new?component=191657&template=1189745)\n - [DNS-over-TLS](https://issuetracker.google.com/issues/new?component=191657&template=1189719)\n - [Domain Problems](https://issuetracker.google.com/issues/new?component=191657&template=1211345): Problems with a domain that are specific to Google Public DNS.\n - [Other](https://issuetracker.google.com/issues/new?component=191657&template=847301)\n- [Public Trackers \\\u003e Public DNS \\\u003e Restricted](https://issuetracker.google.com/issues/new?component=191885)\n For issues that may have confidential information related to an operator or\n domain. Also report security vulnerabilities here. This keeps your report\n private to yourself and Google Public DNS engineers. Available templates:\n\n - [Domain Problems](https://issuetracker.google.com/issues/new?component=191885&template=1213505): Problems with a domain that are specific to Google Public DNS.\n - [Rate Limit Request](https://issuetracker.google.com/issues/new?component=191885&template=1024641): Requests to increase rate limits for ISPs and network operators.\n - [Recursive Denial of Service](https://issuetracker.google.com/issues/new?component=191885&template=1024952): Authoritative nameservers receiving high-volume of DNS queries from Google Public DNS.\n - [Reflection Denial of Service](https://issuetracker.google.com/issues/new?component=191885&template=1024950): Receiving large volume of DNS responses from Google Public DNS (8.8.8.8).\n - [Vulnerability Report](https://issuetracker.google.com/issues/new?component=191885&template=1023681)\n - [Other](https://issuetracker.google.com/issues/new?component=191885&template=847501)\n\nFiling an issue in either of the two components gives the issue a tracking\nnumber and a Google Public DNS engineer will be assigned to handle it. You can\nview the issue's history and status as it is updated. For more help with the\nIssue Tracker itself please see its\n[documentation](https://developers.google.com/issue-tracker/)."]]