Google 域注册主机（胶水记录）在 48 小时后未解析

Question

我正在为我的域使用 Google 域：violetnorthapp.com，我有一些自定义名称服务器运行，我想创建注册主机（这是术语google 用于粘合记录）。我在 test.ns.violetnorthapp.com 下创建了一个注册主机，它应该解析为 8.8.8.8.

已经超过 48 小时了，但仍未解决 dig test.ns.violetnorthapp.com.

; <<>> DiG 9.10.6 <<>> test.ns.violetnorthapp.com.
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 63639
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;test.ns.violetnorthapp.com.    IN  A

;; AUTHORITY SECTION:
violetnorthapp.com. 300 IN  SOA ns-cloud-b1.googledomains.com. cloud-dns-hostmaster.google.com. 6 21600 3600 259200 300

;; Query time: 68 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Sat May 30 18:31:02 EDT 2020
;; MSG SIZE  rcvd: 145

我用 com. 的 TLD 域名服务器试过运行其中之一是 a.gtld-servers.net.，所以请求是 dig test.ns.violetnorthapp.com. @a.gtld-servers.net.:

; <<>> DiG 9.10.6 <<>> test.ns.violetnorthapp.com. @a.gtld-servers.net.
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26571
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 4, ADDITIONAL: 9
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;test.ns.violetnorthapp.com.    IN  A

;; AUTHORITY SECTION:
violetnorthapp.com. 172800  IN  NS  ns-cloud-b1.googledomains.com.
violetnorthapp.com. 172800  IN  NS  ns-cloud-b2.googledomains.com.
violetnorthapp.com. 172800  IN  NS  ns-cloud-b3.googledomains.com.
violetnorthapp.com. 172800  IN  NS  ns-cloud-b4.googledomains.com.

;; ADDITIONAL SECTION:
ns-cloud-b1.googledomains.com. 172800 IN AAAA   2001:4860:4802:32::6b
ns-cloud-b1.googledomains.com. 172800 IN A  216.239.32.107
ns-cloud-b2.googledomains.com. 172800 IN AAAA   2001:4860:4802:34::6b
ns-cloud-b2.googledomains.com. 172800 IN A  216.239.34.107
ns-cloud-b3.googledomains.com. 172800 IN AAAA   2001:4860:4802:36::6b
ns-cloud-b3.googledomains.com. 172800 IN A  216.239.36.107
ns-cloud-b4.googledomains.com. 172800 IN AAAA   2001:4860:4802:38::6b
ns-cloud-b4.googledomains.com. 172800 IN A  216.239.38.107

;; Query time: 85 msec
;; SERVER: 192.5.6.30#53(192.5.6.30)
;; WHEN: Sat May 30 18:32:16 EDT 2020
;; MSG SIZE  rcvd: 349

这就是 Google 域的样子

我是不是遗漏了什么？

Answer 1

您的主机已在注册表中完全注册，whois 证实：

$ whois -h whois.verisign-grs.com 'nameserver test.ns.violetnorthapp.com' | head -6
   Server Name: TEST.NS.VIOLETNORTHAPP.COM
   IP Address: 157.245.176.218
   Registrar: Google LLC
   Registrar WHOIS Server: whois.google.com
   Registrar URL: http://domains.google.com
>>> Last update of whois database: 2020-05-30T22:48:59Z <<<

或更好的 RDAP：

$ curl --silent https://rdap.verisign.com/com/v1/nameserver/test.ns.violetnorthapp.com | jq .
{
  "objectClassName": "nameserver",
  "ldhName": "TEST.NS.VIOLETNORTHAPP.COM",
  "ipAddresses": {
    "v4": [
      "157.245.176.218"
    ]
  },
  "links": [
    {
      "value": "https://rdap.verisign.com/com/v1/nameserver/TEST.NS.VIOLETNORTHAPP.COM",
      "rel": "self",
      "href": "https://rdap.verisign.com/com/v1/nameserver/TEST.NS.VIOLETNORTHAPP.COM",
      "type": "application/rdap+json"
    }
  ],
  "events": [
    {
      "eventAction": "last update of RDAP database",
      "eventDate": "2020-05-30T09:38:51Z"
    }
  ],
  "rdapConformance": [
    "rdap_level_0",
    "icann_rdap_technical_implementation_guide_0",
    "icann_rdap_response_profile_0"
  ],
  "notices": [
    {
      "title": "Terms of Use",
      "description": [
        "Service subject to Terms of Use."
      ],
      "links": [
        {
          "href": "https://www.verisign.com/domain-names/registration-data-access-protocol/terms-service/index.xhtml",
          "type": "text/html"
        }
      ]
    }
  ]
}

但是，胶水有非常特殊的用途。它不是 "free hosting" 在注册表中。您在注册表中创建了一个主机对象，但没有将它关联到任何域。因此，无需在注册表级别的 DNS 中发布它。

一旦您将它关联到 .com 或 .net 下的某个域，它应该会在不久之后开始解析（实际上您需要将 dig 与 @ 标志来查询注册表名称服务器，否则你正在访问本地递归服务器，它可以通过正常分辨率学习 IP 地址，无需任何胶水）。

Google 域注册主机（胶水记录）在 48 小时后未解析

Google domains registered hosts (glue records) are not resolving after 48 hours

dns

nameservers

google-cloud-dns

dig

google-domains