询问者
切换备用宽带后AD域客户机不能上网

问题
-
1.公司目前之前使用的是两台AD域服务器,一条独立联通宽带,正常运行无问题。
主域服务器IP设置如下:
辅域服务器IP设置如下:
2.路由器DHCP分配给客户机的主DNS为主域服务器IP,辅DNS为辅域服务器IP。现在新加一条电信宽带,在同一路由器中接入,作为备用宽带。
宽带接入信息:
域服务器对应DNS转发设置:
3.在故障切换测试中发现,将联通主宽带断开后,路由器能正常切换到备用电信宽带,切换后两台域服务器均能正常访问网络(网站均能正常访问),但客户机均不能访问外网。
4.客户机不能访问外网时,尝试将客户机自动获取的DNS手工指定为114.114.114.114后能正常访问外网,不知道具体是哪里出了问题。
全部回复
-
您好 ,
在客户端不能访问外网的时候,请在CMD中运行nslookup回车键入set d2,回车键入想要解析的外部网站,然后上传整个解析结果。
格式如下:
>NSlookup
>set d2
>www.baidu.com另外,如果你手动指定192.168.1.225能解析成功吗:
>nslookup
>server 192.168.1.225
>www.baidu.com
此致
Candy
Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com -
Dear candy,感谢指导,以下为测试结果 :
C:\Users\enjun.deng>ping baidu.com
Ping 请求找不到主机 baidu.com。请检查该名称,然后重试。
C:\Users\enjun.deng>nslookup
DNS request timed out.
timeout was 2 seconds.
默认服务器: UnKnown
Address: 192.168.1.228
> set d2
> www.baidu.com
服务器: UnKnown
Address: 192.168.1.228
------------
SendRequest(), len 46
HEADER:
opcode = QUERY, id = 2, rcode = NOERROR
header flags: query, want recursion
questions = 1, answers = 0, authority records = 0, additional = 0
QUESTIONS:
www.baidu.com.zj-freight.com, type = A, class = IN
------------
DNS request timed out.
timeout was 2 seconds.
timeout (2 secs)
SendRequest 失败
------------
SendRequest(), len 46
HEADER:
opcode = QUERY, id = 3, rcode = NOERROR
header flags: query, want recursion
questions = 1, answers = 0, authority records = 0, additional = 0
QUESTIONS:
www.baidu.com.zj-freight.com, type = AAAA, class = IN
------------
DNS request timed out.
timeout was 2 seconds.
timeout (2 secs)
SendRequest 失败
------------
SendRequest(), len 31
HEADER:
opcode = QUERY, id = 4, rcode = NOERROR
header flags: query, want recursion
questions = 1, answers = 0, authority records = 0, additional = 0
QUESTIONS:
www.baidu.com, type = A, class = IN
------------
DNS request timed out.
timeout was 2 seconds.
timeout (2 secs)
SendRequest 失败
------------
SendRequest(), len 31
HEADER:
opcode = QUERY, id = 5, rcode = NOERROR
header flags: query, want recursion
questions = 1, answers = 0, authority records = 0, additional = 0
QUESTIONS:
www.baidu.com, type = AAAA, class = IN
------------
DNS request timed out.
timeout was 2 seconds.
timeout (2 secs)
SendRequest 失败
*** 请求 UnKnown 超时
>-----------------------------------------------
手工指定好像也不行
C:\Users\enjun.deng>nslookup
DNS request timed out.
timeout was 2 seconds.
默认服务器: UnKnown
Address: 192.168.1.228
> server 192.168.1.225
DNS request timed out.
timeout was 2 seconds.
默认服务器: [192.168.1.225]
Address: 192.168.1.225
> www.baidu.com
服务器: [192.168.1.225]
Address: 192.168.1.225
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** 请求 [192.168.1.225] 超时
>
-
Hello ,
请到两台DC上通过ipconfig /flushdns的命令请理一下缓存,再在一台有问题的客户端上运行ipconfig /flushdns请理一下缓存,清理完缓存之后,看下这个时候客户端和DC的网络状态分别是什么情况。
此致
Candy
Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com- 已编辑 Candy LuoMicrosoft contingent staff 2020年12月14日 9:05
-
Dear candy,感谢关注。
我在域服务器上执行了ipconfig/flushdns命令,然后客户机上执行同样命令,结果还是一样,以下是操作结果:
--------------------------------------------------------------
C:\Users\enjun.deng>ipconfig/flushdns
Windows IP 配置
已成功刷新 DNS 解析缓存。
C:\Users\enjun.deng>ping baidu.com
Ping 请求找不到主机 baidu.com。请检查该名称,然后重试。
C:\Users\enjun.deng>nslookup
DNS request timed out.
timeout was 2 seconds.
默认服务器: UnKnown
Address: 192.168.1.228
> server 192.168.1.225
DNS request timed out.
timeout was 2 seconds.
默认服务器: [192.168.1.225]
Address: 192.168.1.225
> www.baidu.com
服务器: [192.168.1.225]
Address: 192.168.1.225
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** 请求 [192.168.1.225] 超时
>--------------------------------------------------------
- 已编辑 blueidea9 2020年12月15日 1:17
-
Hi ,
我怀疑DC端现在用的是root hints进行解析,请帮忙在DC上测试一下与转发器之间的网络,看下结果是否可以ping通:
ping 114.114.114.114
如果ping也没有问题的话,那这个问题从论坛的角度很难进行排查了,需要去抓包看问题到底出在什么地方了。
但是作为论坛的工程师,log分析已经超出了我们的支持范围,而且由于论坛是公共开放的,我们没有隐私渠道来收集用户的log信息。因此建议联系微软客户服务代表,他们会帮你向微软开启电话或者是邮件case,这样可以保证隐私信息的情况下,通过1对1的方式进行技术支持。
https://support.microsoft.com/en-us/gp/customer-service-phone-numbers
此致
Candy
Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com -
Hi ,
那我们关闭动态dns转发器功能再试试看,看看问题是否是和第二个转发器有关系。
windows server从2012R2版本开始引入了动态dns转发器功能,默认情况下转发顺序会根据列表中的响应时间进行排序,然后选择最快的dns转发器进行递归查询。如果我们disable这个功能,可以让客户端查询记录的时候先向第一个转发器发送request。在您的案例下,就是让客户端查询记录的时候先向114.114.114.114去发送request。
可以通过以下Powershell命令来关闭动态转发器功能,关闭以上功能后,dns服务器选择转发器时,会根据转发器的配置顺序来进行递归查找对应的dns记录。
Set-DnsServerForwarder -EnableReordering $False -PassThru
如果要重新开启动态转发功能的话,把false改成true即可。
如果还是不能解决问题的话,那我建议还是和微软开case抓包分析问题的具体原因了。
此致
Candy
Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com- 已建议为答案 Candy LuoMicrosoft contingent staff 2020年12月17日 2:40
-
您好 ,
请问目前问题是否还需要进行更进?
此致
Candy
Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com -
好的,如果问题比较紧急的话,我建议和微软开case进行深度分析。后续如果您有关于此问题的解决方案,欢迎随时来论坛分享,我相信会帮助到其他遇到类似问题的论坛用户。
感谢您的理解。祝您工作愉快!
Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com