3 ms·

Why risky?

• majewsky 10y ago
  You're needlessly exposing private information about your system to the public, which an attacker can use to learn about the structure of your setup, or to appear more credible during a social engineering attack. And if the IP of the development system happens to be publicly routed, attackers might reach and infiltrate a probably insecure development system.
  • bitJericho 10y ago
    Ah yes I would agree. However, you're best off using a local dns server to route to a private subdomain. It is handy to use a public facing IP to also point towards your service though, if, and only if, you want it web accessible.