Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 9 replies
  • Subscribers 6 subscribers
  • Views 4937 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

DNS group for all Teamviewer server

offn

Hello!

I want to create a DNS group, which automatically captures all Teamviewer server. I know how to create a DNS group. But which DNS name should I use?

Thanks in advance for your help.



This thread was automatically locked due to age.
Parents
  • 0

    This is a very dynamic problem...You can not use wildcard (*) with network definitions (e.g. *.teamviewer.com)

    Now it depends on what your aim is?

     

    If teamviewer updates & connections should work everywhere:

     

    In Sophos Webfilter there should already be an exception for Teamviewer like

    ^https?://(?:[A-Za-z0-9-]+\.)+teamviewer\.com/?

     

    Just check/add exception for authentication, URL Filter, SSL-Check, extension blocking and MIME-Typ blocking and teamviewer & updates should work now.

     

    regards

  • 0 in reply to Steve Weißflog

    teamviewer.com resolves the webpage only

    *.teamviewer.com does not work in a DNS group

  • 0 in reply to offn

    As already said this is not really possible/useful for the Firewall because you can't use */wildcard-definitions...

    I know that there is already a feature request for that use case...

     

    Teamviewer is very dynamic - you would need a list with ALL DNS-Server addresses from Teamviewer and add every single DNS-Host and I think there will be still some IPs of Teamviewer missing...

     

    I prefer to use Webfilter/Proxy for Teamviewer traffic...

     

    In your case it is maybe easier to open Teamviewer Port 5938 generally on Firewall than to add every Teamviewer DNS-Host...

     

    regards

Reply
  • 0 in reply to offn

    As already said this is not really possible/useful for the Firewall because you can't use */wildcard-definitions...

    I know that there is already a feature request for that use case...

     

    Teamviewer is very dynamic - you would need a list with ALL DNS-Server addresses from Teamviewer and add every single DNS-Host and I think there will be still some IPs of Teamviewer missing...

     

    I prefer to use Webfilter/Proxy for Teamviewer traffic...

     

    In your case it is maybe easier to open Teamviewer Port 5938 generally on Firewall than to add every Teamviewer DNS-Host...

     

    regards

Children
No Data
Unfiltered HTML