动态DNS安全性
我有一些客户每天更改IP的客户，而静态IP不是他们的选择。
如果我让他们安装一个动态DNS客户端，然后在我的应用程序中。Htaccess文件参考该动态DNS域，这对我的应用程序构成了任何安全问题吗？
因此，总结我的.htaccess文件中使用动态DNS域是否对我的应用程序构成任何与安全有关的威胁？
I have some clients whose IP changes every day and static IP is not an option for them.
If I have them install a Dynamic DNS client, and then in my application .htaccess file refer to that Dynamic DNS domain, does that pose any security issue for my application?
So to summarize does using Dynamic DNS domains in my .htaccess files pose any security related threats to my application?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
据我所知，您想将客户IP地址添加到应用程序的白名单中，并且要切换到Dyndns，因为IP地址每天都会更改。
因此，您想为每个客户分配不同的域和白名单，每个域，这是正确的吗？
这里明显的攻击向量将劫持域，并将其指向使用DynDNS服务的客户机以外的Malesous机器。
如果您设法在客户端计算机上注册Dyndns客户端，而无需公开有关可能被盗或丢失的域的任何登录信息，则这应该是安全的。但是我目前看不到您将如何在不存储该计算机上的凭据的情况下为域Dyndn注册客户端。
As far as I understand this, you want to add your clients IP addresses to the whitelist of your application and you want to switch to DynDNS because the IP addresses change every day.
So you want to assign each client a different domain and whitelist each of those domains, is that correct?
The obvious attack vector here would be hijacking a domain and pointing it to a malicous machine other than the clients machine using the DynDNS service.
If you manage to register the DynDNS client on the clients machine without exposing any login information regarding the domain that could be stolen or lost then this should be safe. But I currently do not see how you would be able to register the client for your domains DynDNS without having the credentials stored somewhere on this machine.