DNS 记录中非最左边的通配符？
假设情况：
假设我经营一家托管公司，为人们托管子域。 你可以注册并每月给我几美元，我会给你 yourname.mycompany.com。
现在，假设我希望 mail.*.mycompany.com 指向一台服务器，而 www.*.mycompany.com 指向另一台服务器。
这可能吗？ RFC 似乎不这么认为，Wikipedia 似乎不这么认为，但是是什么阻止了 DNS 服务器有足够的逻辑来返回正确的东西吗？
如果是这样，是否有 DNS 托管提供商可以为我执行此操作，这样我就不必运行自己的 DNS？
Hypothetical situation:
Suppose I ran a hosting firm where I hosted subdomains for people. You could sign up and give me a few bucks a month, and I'd give you yourname.mycompany.com.
Now, say I wanted mail.*.mycompany.com to point to one server and www.*.mycompany.com to point to another.
Is this possible? The RFC seems to think not, Wikipedia seems to think not, but what's stopping a DNS server from having enough logic to return the right thing?
And if so, are there DNS hosting providers that will do this for me so I don't have to run my own DNS?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我对这个问题的解决方案是运行我自己的 dns，当添加客户端时，以编程方式将记录添加到 dns，这也使我能够确定哪个 www 服务器使用最少，并正确分配客户端。
My solution to this exact problem was to run my own dns, and when a client was added programaticly add the records to the dns, which also allowed me o determine which www server was the least used and apportion the client correctly.
您可以开发自己的 DNS，该 DNS 使用不合格的内部存储机制，但您仍然需要与其他服务器使用相同的协议。 此外，您通常必须有一个非本地备份服务器，它无疑不愿意采用您的 DNS 服务器，并且您仍然必须以标准格式生成所有订阅公司的全名。
You could develop your own DNS that uses a non-conforming internal storage mechanism, but you still need to talk the same protocol as the rest of the servers. Also, you usually have to have a non-local backup server that will undoubtedly be unwilling to adopt your DNS server and you'll still have to generate the full names for all of the subscribing companies in the standard format.
您需要编写自己的 DNS 服务器来支持此 AFAIK。 但没有什么可以阻止你这样做。 很容易响应 DNS 请求，但您愿意！
据我所知，没有托管公司支持通配符 DNS 中间条目。
You need to write your own DNS server to support this AFAIK. Nothing stopping you from doing so though. Easy enough to respond to DNS requests however you'd like!
No hosting company I know of supports wildcarded DNS mid entry.