如何正确高效地动态创建与原域名不同IP的子域名？
如何有效地动态创建解析为与原始域不同的 IP 的子域？
我在这里找到的大多数动态子域创建解决方案都会将 *.domain.com A 记录添加到 DNS 服务器（通常使用 BIND），但这不是我想要的。
这是否意味着区域文件需要设置为始终过期？ 这不会给我们的 DNS 服务器带来沉重的负担吗？
但是，如果客户端 ISP 不去获取我刚刚动态更改的新区域文件怎么办？ 他们不会无法解析我们的新子域条目吗？
在 BIND 中设置 DDNS 是否是实现此类系统的逻辑路径？ DDNS 允许我动态插入 A 记录而无需重新启动 BIND，对吧？
我确信有一些方法可以做到这一点，因为大多数大型博客服务并不将所有帐户都指向与博客引擎相同的 IP，而是正在做与我需要的类似的事情。
谢谢你！
How to efficiently create subdomains dynamically that are resolved to different IP than the original domain?
Most dynamic subdomain creation solutions I've found here would add a *.domain.com A-record to the DNS server (usually using BIND), but that's not what I want.
Does that mean the zone file needs to be set to always Expire? Wouldn't that tax our DNS server heavily?
However, what if the client ISP doesn't go and fetch the new zone file I just dynamically changed? Wouldn't they not able to resolve our new sub-domain entry?
Would setting up DDNS in BIND be the logical path for implementing such system? DDNS would allow me dynamically insert A-record without restarting BIND, right?
I'm sure there are some way to do this, since most large blogging service that doesn't point all account to the same IP as the blogging engine, are doing something similar to what I need.
Thank you!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
是的，您可以使用动态 DNS 更新将区域文件更改推送到您的区域中，而无需将它们放入文本区域文件中并每次重新加载 BIND。
许多大型域名注册机构在注册域名时都使用这种技术。
但这并不意味着它是适合您的应用程序的技术。 正如昨天对您的其他问题所建议的那样，确实没有理由不使用通配符选项。
运行 Apache 的低端服务器足以对您的前几千个站点进行前端反向代理，更好的是，您甚至不需要部署它，直到您获得足够的用户来设置第二个分区集群。
Yes, you could use dynamic DNS updates to push zone file changes into your zone without having to put them into a text zone file and reloading BIND each time.
Many large domain name registries use exactly that technique whenever a domain name is registered.
That doesn't mean, though, that it's the right technique for your application. As recommended yesterday to your other question, there's really no reason not to go with the wildcard option.
A low-end server running Apache would be more than enough to front-end reverse proxy your first few thousand sites, and better still you don't even need to deploy it until you get enough users to set up your second partitioned cluster.
我想大多数执行此操作的服务都会为这些帐户设置通配符 (*.) DNS 条目，并可能将其指向负载均衡器，该负载均衡器根据主机名等分发请求。然后它们会进行非标准条目设置与 DNS 中的普通 A 记录一样。
I would imagine that most services that do this have their wildcard (*.) DNS entry setup for these accounts, and probabley point it to a load balancer, that distributes requests based on host name etc. They then have the non-standard entrys setup as normal A records in DNS.