Existing a domain control server, and going to apply for members of the domain to domain control server network port between strategy, whether you need to verify some ports, the domain control server with Windows authentication, firewall do DNS 53 port, for example, in the direction of the inbound firewall disabling DNS 53 ports, but from members of the domain still can through the way of the nslookup and specify the domain control server address resolution domain, the domain control server and domain members caught deployment Wireshark software on both sides, also visible between the DNS protocol packets, is Windows built-in firewall function is invalid? Or my operation has a problem, please expert advice, thank you!

CodePudding user response:

What Windows version? Firewall can't be null and void

CodePudding user response:

reference 1st floor ojc8882003 response:

what version of Windows? Firewall can't be null and void.

Windows 2012 R2 serverr, I do not know where the problem is, please advise, thank you!

CodePudding user response:

Sure is disabled and operative udp53?

CodePudding user response:

refer to the original poster beber2k response:

an existing domain control server, and going to apply for members of the domain to domain control server network port between strategy, whether you need to verify some ports, the domain control server with Windows authentication, firewall do DNS 53 port, for example, in the direction of the inbound firewall disabling DNS 53 ports, but from members of the domain still can through the way of the nslookup and specify the domain control server address resolution domain, the domain control server and domain members caught deployment Wireshark software on both sides, also visible between the DNS protocol packets, is Windows built-in firewall function is invalid? Or my operation has a problem, please expert advice, thank you!

the original poster to find the answer???????

CodePudding user response:

Determine the TCP, UDP 53 are sealed off?