{
  "acceptance": "The investigation should end with evidence for each tested layer, an identified failure or an explicit unresolved layer, and a repeatable recovery check. Do not manufacture an HTTP status for a request that never reached HTTP.",
  "automated_checks": true,
  "batch_id": "analytics-editorial-20261104-v1",
  "built_at": "2026-11-04T11:50:28.566595+00:00",
  "claims": [
    {
      "id": "c1",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "Google treats DNS and network failures as problems that can slow crawling."
    },
    {
      "id": "c2",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "Some network failures occur before the server can return an HTTP status."
    },
    {
      "id": "c3",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "Google recommends checking DNS A and CNAME records against the intended target."
    },
    {
      "id": "c4",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "Authoritative name-server responses are part of DNS troubleshooting."
    }
  ],
  "description": "Do not turn a missing origin-log entry into a successful request; inspect the layers before HTTP.",
  "diagram": [
    "Resolve the exact hostname",
    "Check connection establishment",
    "Inspect HTTP if reached",
    "Retest the failed layer"
  ],
  "draft_hash": "49b6c2428f571850131106079d20519a5c16ebf9d53f72f24001ad146826bba2",
  "evidence": {
    "observed_at": "2026-11-03T04:00:02.552826+00:00",
    "period": {
      "end": "2026-11-03T04:00:02.552826+00:00",
      "start": "2026-11-03T04:00:02.552826+00:00",
      "timezone": "UTC"
    },
    "rows": [],
    "scope": "Official documentation; no customer or own-site traffic measurement"
  },
  "evidence_kind": "documentation",
  "figure_caption": "Original explanatory diagram based on the dated sources below. Any example values are hypothetical; this is not a screenshot, customer measurement or AI platform result.",
  "figure_kind": "sequence",
  "figure_notes": [
    "Compare records and authoritative name-server responses.",
    "Inspect the relevant firewall and network evidence.",
    "Do not invent a status for a pre-HTTP failure.",
    "Keep unresolved layers explicitly unverified."
  ],
  "figure_title": "No HTTP status in crawl logs: investigate DNS and network failures",
  "group": "Crawl access and indexing",
  "human_review_claim": false,
  "intent": "google-dns-vs-http-failures",
  "interpretation": "A request can fail before the server is able to return an HTTP response. Google’s network troubleshooting guidance covers DNS failures, connection resets and timeouts, including cases with no status code. An empty origin-log search therefore cannot establish that Google never attempted access or that access succeeded. Work from the named failure layer and its timestamp.",
  "keyword_volume": "Not obtained",
  "limits": "An isolated successful lookup does not prove every resolver or Google request is healthy. This guide does not supply a measured incident or a guaranteed indexing-recovery timetable.",
  "paid_api_calls": 0,
  "path": "/ai-analytics/guides/google-dns-vs-http-failures/",
  "policy": "session-evidence-editorial-v1",
  "preparation_mode": "session_editorial_batch",
  "problem": "Search Console reports a connection problem but the origin access log contains no matching status.",
  "product": "/ai-analytics",
  "published_at": "2026-11-05T00:55:12.085410+00:00",
  "reader": "Site owners and analysts investigating search Console reports a connection problem but the origin access log contains no matching status.",
  "related": [
    "origin-logs-cdn-coverage",
    "robots-file-errors-vs-page-errors"
  ],
  "related_links": [
    {
      "path": "/ai-analytics/guides/origin-logs-cdn-coverage/",
      "title": "Explain the cache blind spot in origin-only logs"
    },
    {
      "path": "/ai-analytics/guides/robots-file-errors-vs-page-errors/",
      "title": "Separate robots.txt failures from page errors"
    }
  ],
  "research_document_ids": [
    "04f6f1359a336d42fcf61f3250625a8d"
  ],
  "slug": "google-dns-vs-http-failures",
  "source_signature": "fd93cdd8c31a47256745fd63251de19967462c3a20d29f97a60fbbf8647c21d0",
  "sources": [
    {
      "hash": "f01cffcc010ec9375f1707a168d4d972c219d5a9a282fdc53fcf7c73cd54ec5e",
      "locator": "Debug DNS errors / b10; Debug DNS errors / b13; Debug network and DNS errors for Google's crawlers / b1; Debug network errors / b3",
      "observed_at": "2026-11-03T04:00:02.552826+00:00",
      "title": "Debug network and DNS errors for Google's crawlers",
      "url": "https://developers.google.com/crawling/docs/troubleshooting/dns-network-errors"
    }
  ],
  "sources_required": [],
  "steps": [
    "Save the exact hostname, reported failure type and time window. Check whether your origin log actually covers the requested host and serving layer.",
    "For DNS failures, compare A or CNAME records with the intended target and check authoritative name-server responses for consistency. Keep resolver and timestamp with each result.",
    "For connection resets or timeouts, inspect relevant firewall logs and network health. Ask the hosting provider for the missing layer of evidence if local logs cannot explain the failure.",
    "Retest the same hostname through resolution, connection and HTTP stages. Record which stage failed and which was successfully checked after a change."
  ],
  "title": "No HTTP status in crawl logs: investigate DNS and network failures",
  "worked_example": "Hypothetical case: a reported DNS error has no origin access-log match. Checking an application route alone cannot reproduce a failed name lookup. Record the host’s DNS answers and authoritative-server consistency first; then investigate connection and HTTP behavior if name resolution succeeds."
}