Announcement: New Knowledge Base

4 June 2020: We are pleased to announce the launch of a new Knowledge Base, Changelogs for Business Security Products, where you can find more details, such as bugfixes or new features, about the most recent releases of our business-related products.

[mydns]

How F-Secure firewall determines [mydns] definition in firewall rules? It happens to me that F-Secure Firewall denies connection to one of two DNS servers while I am using VPN. So I would like to know more what is laying behind [mydns] logic. Thanks!

Comments

  • VadVad Posts: 1,050 F-Secure Employee

    Hello Mazarin,

     

    [mydns] actually means ip address 172.16.0.3.

     

    Best regards,

    Vad

  • Why 172.16.0.3? It doesn't make sense. I would rather expect that [mydns] is dynamically assigned by IP addresses of DNS servers according to actual TCP/IP configuration. But in that case, why f-secure fw denies name resolving to one of the DNS servers while I'm using VPN. I'm afraid there is a bug behind [mydns] logic.

     

    Previously I have this FW rule for DNS:

    localmachine -> [mydns] via TCP/UDP 53

     

    To assure that both DNS servers are accessible for DNS resolving while I'm using VPN I have to replace the rule by this:

    localmachine -> 0.0.0.0/0 via TCP/UDP 53

     

    But I'm sill curious how [mydns] in F-Secure works.

  • VadVad Posts: 1,050 F-Secure Employee

    Mazarin, you are right. I'm sorry for incorrect answer. [mydns] is dynamically changing list of DNS servers. The list is updating every time when FW checks the rule.

     

    What product/version do you have?

    If you think it doesn't work as expected, please, contact support. We will need more detailed information and probably debug logs from affected machine.

     

    Best regards,

    Vad

This discussion has been closed.