Date: Fri, 29 Mar 2024 13:20:20 +0100 (CET) Message-ID: <929671153.3674.1711714820922@teamwork> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_3673_889917286.1711714820922" ------=_Part_3673_889917286.1711714820922 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
A good working DNS is mandatory to ensure good telephony quality, especi= ally in a hosted environment.
Via this article we want to inform you of the possible security risks wh= en using a public DNS server.
When using a public DNS server, like Google 8.8.8.8 or 8.8.4.4 and many = more, there is a big chance that a Googlebot or similar mechanism will scan= the router of which the DNS enquiry came from and will report the opened p= orts (port forwards you may have setup). As, in this case Google wants to c= ollect as much information about the possible website behind the router, th= ey use this mechanism as they will have more to show in their search engine= .
It was brought to our attention that there are sites (which we will not = reveal in this article) that will make this information available for anyon= e who knows such websites. You can imagine how easy it would be for hackers= to try to attack your systems, especially when they can be found so easily= .
As many hack tools are on the internet, all default passwords and login = names will be tried first and when they are in, they can do whatever they l= ike with your system or worse, your customers system(s).
To narrow down the risk there are several things you can do as always:= p>