DNS Client allowed by firewall rule, but still get blocked


  1. Posts : 10
    Windows 10 Pro 1909
       #1

    DNS Client allowed by firewall rule, but still get blocked


    Hi,

    First; I am using Binisoft/Malwarebytes Windows Firewall Control as frontend for Windows Firewall.

    My problem is that I allowed DNS Client to local gateway with UDP on port 53, but still for some reason it is being blocked. When opening the log window in Windows Firewall Control it says 'Blocked'.

    The name of the rule was set automatically to DNS Client, but as service I notice in the log that DNS Client is reported with Dnscache as service, but in the rules dialog box there is no Dnscache in the Services drop down menu.

    I am not sure if what I wrote in previous paragraph is of any significance, but my initial question would be if there is any other service that also have to be allowed with outbound rule to make DNS Client work? I have a pretty strict rule set, so nothing get out by coincidence.

    Could someone please help me out?

    Thank you,
    GormTheOld

    Windows 10 Pro 1909
      My Computer

  2. Callender's Avatar
    Posts : 2,548
    Windows 10 Home 1903 64-bit
       #2

    It's display name is DNS Client.

    I don't use that firewall.

    DNS Client allowed by firewall rule, but still get blocked-process-hacker-administrator-.jpg
      My Computer

  3. Samuria's Avatar
    Posts : 4,969
    windows 10
       #3

    Welcome to the forum its not clear what your trying to do port it uses port 53 tcp and udp aand repies on another port 1023

    How do I configure my firewall for DNS? - Simple DNS Plus
      My Computer


  4. Posts : 10
    Windows 10 Pro 1909
    Thread Starter
       #4

    Callender said:
    It's display name is DNS Client.
    ....
    Thank you Callender! Good to know.

    - - - Updated - - -

    Samuria said:
    Welcome to the forum its not clear what your trying to do port it uses port 53 tcp and udp aand repies on another port 1023
    ....
    Thank you Samuria.

    I found the issue was caused by the "Host Process for Windows Services" being blocked.

    I was then asked for a new separate rule asking to allow the DNS Client, but then again because the "Host Process for Windows Services" was blocked it didn't work to just allow the new DNS Client request.

    Since I like to have control over when things access the internet, the solution was to just allow "Host Process for Windows Services" for 'LocalSubnet'.

    For the record I was told that the DNS Client already has a rule named "WFC - Core Networking - DNS (UDP-Out)", but when "Host Process for Windows Services" is blocked this wrecks the order of things.
      My Computer


 

Related Threads
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 21:47.
Find Us




Windows 10 Forums