大网数据广告活动
服务器运维问答

Why is my A Record in Google Cloud DNS not resolvable immediately after creation?

· 52CE 我爱测

I am creating a DNS A Record via the Google Cloud API, ending up with: DNS Name: some-subdomain.mysite.io Type: A TTL: 1 IP: 35.XXX.XXX.XX After the entry is confirmed as created and viewable in the API, I am trying to resolve it…

问题原文

原帖链接 · mogronalol · CC BY-SA 3.0

I am creating a DNS A Record via the Google Cloud API, ending up with:

  • DNS Name: some-subdomain.mysite.io
  • Type: A
  • TTL: 1
  • IP: 35.XXX.XXX.XX

After the entry is confirmed as created and viewable in the API, I am trying to resolve it using nslookup, but I get:

$ nslookup some-subdomain.mysite.io
 Server:        192.168.178.1
 Address:   192.168.178.1#53

** server can't find some-subdomain.mysite.io: NXDOMAIN

It stays like this for a few minutes, until it eventually resolves.

Because the first lookup is after it's been created, I'd expect it not to miss (And therefore have no miss to cache). Is there anything I can do to make the lookup succeed sooner?

已采纳解答

原帖链接 · mogronalol · CC BY-SA 3.0

The solution we came up with was to use a wildcard DNS entry. So now I have an entry:

*.mysite.io -> 10.XX.XX.XX

This means any sub domain we create is resolvable immediately as the DNS already exists. We then route internally based on the host header.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2017-08-01)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。