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

windows server 2016 DC + VPN Roles - DNS Issue

· 52CE 我爱测

I have a server running Windows Server 2016 with ADDS, DNS, DHCP and RRAS roles. I am experiencing the following issue: My server's LAN IP is 192.168.0.1 and the second interface, connected to DMZ, has IP 192.168.18.1. The client…

问题原文

原帖链接 · Deep Space · CC BY-SA 3.0

I have a server running Windows Server 2016 with ADDS, DNS, DHCP and RRAS roles. I am experiencing the following issue:

My server's LAN IP is 192.168.0.1 and the second interface, connected to DMZ, has IP 192.168.18.1.

The clients sometimes resolve the server's name with IP 192.168.18.1, I have noticed that the record is automatically created in DNS Server in the direct zone "my.domain.com" (even if the ".18" IP is fixed and not DHCP assigned) Each time I delete the record 192.168.18.1 all connections from clients to the server works, until the record gets automatically recreated.

When the record gets re-created this issue starts happening again (as LAN clients have no routes to the DMZ IP).

How can I prevent the wrong record to be automatically recreated on the dns server?

Or is there any other kind of fix?

已采纳解答

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

The DNS server will register the ip address for each interface that it is bound to. The fix is to "unbind" the 192.168.18.1 interface in the DNS server properties.

From the DNS management console, right click the server, select properties from the context menu, and on the interface tab select the Only the following ip addresses radio button, and uncheck the 192.168.18.1 box.

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

资料来源与适用范围

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

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

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