问题原文
原帖链接 · 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.
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
