Discussion Groups and Issue Reporting (optimized for Google Public DNS groups)
Step one: identify which system is affected
Google operates multiple DNS-related products. Before reporting, determine whether the problem affects Google properties (for example www.google.com or www.youtube.com), Google Domains-hosted authoritative DNS, or Google Public DNS itself. Reporting to the correct system gets your issue to the right team faster. Google for Developers
-
If Google properties are involved and you operate an ISP, use Google’s ISP Portal (request access if needed). If you’re a customer, contact your ISP and ask them to escalate via the ISP Portal. Google for Developers
-
If you used Google Domains default hosting and others can’t reach your domain, contact Squarespace support (Google Domains was migrated to Squarespace). Google for Developers
If the problem occurs only with Google Public DNS (and other resolvers work fine), proceed with the Public DNS-specific diagnostics and reporting steps below. Google for Developers
Discussion groups (subscribe & report non-security issues)
Join or post to the official Google discussion lists to get updates and community feedback related to Google Public DNS groups:
-
public-dns-discuss — forum for proposing ideas, discussing implementations, and getting feedback on Public DNS features. Moderated; posts appear after approval. Do not use this list for security-related disclosures. Google for Developers
-
public-dns-announce — read-only announcements about releases, feature changes, and service status. Google for Developers
Before you report: run diagnostics
If you have a Google Public DNS issue, first run the diagnostic tests recommended by Google. For domain-specific failures, check authoritative and DNSSEC health with tools such as intoDNS and DNSViz — these often reveal name server or DNSSEC problems you can fix yourself. Google for Developers
How to report an issue
If diagnostics don’t resolve the problem, you have two options:
-
Post to public-dns-discuss — public community discussion and feedback for non-security issues. Avoid posting vulnerabilities here. Google for Developers
-
Open an issue in Google’s Issue Tracker — use this for security problems (e.g., DNSSEC validation issues) or other problems requiring private handling. The Issue Tracker assigns a tracking number and a Google Public DNS engineer will be assigned. Google for Developers
What to include with your report
Make your report actionable by including:
-
Date & time the problem occurred (use UTC if possible)
-
Your location (region or city)
-
Platform where you observed the issue (Windows, macOS, router firmware, etc.)
-
The hostname(s) affected
-
Whether the problem is continuous or intermittent
-
Links to the intoDNS / DNSViz / name server diagnostic pages
-
Output from the Google Public DNS diagnostic tests you ran (copy/paste command outputs) Google for Developers
Issue Tracker: public vs. restricted components
Google Public DNS uses two Issue Tracker components:
-
Public Trackers → Public DNS — for non-confidential issues. Templates exist for cache flush, DoH, DoT, domain problems, and general issues. Google for Developers
-
Public Trackers → Public DNS → Restricted — for reports that may contain confidential information (e.g., operator-specific domain problems, rate-limit requests, DDoS/reflection incidents, and vulnerability reports). Use this for sensitive disclosures. Google for Developers
Filing in either component gives you a tracking number and the ability to view the issue’s history and status. For Issue Tracker usage help, consult Google’s Issue Tracker documentation. Google for Developers
Quick checklist (copy for your report)
-
Ran Google Public DNS diagnostics
-
Checked intoDNS and DNSViz reports (attach links)
-
Collected platform & timestamps
-
Determined whether issue requires a public post or a restricted Issue Tracker filing
Footer / Legal
Content source and licensing: The original guidance is from Google Developers’ Public DNS “Discussion Groups and Issue Reporting” page. Content on the original page is licensed under Creative Commons Attribution 4.0 (code samples under Apache 2.0). Last updated on the original page: June 5, 2025. Google for Developers