Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

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

UTM V9 : Tools/DNS Lookup fehler?

Auf die Anfage nach der Adresse 195.12.234.51

bekam ich die folgende Antwort von der UTM V 9.001-18
-----------------------------------------------------------

Trying "51.234.12.195.in-addr.arpa"

Host 51.234.12.195.in-addr.arpa. not found: 3(NXDOMAIN)

Received 107 bytes from 127.0.0.1#53 in 35 ms

-----------------------------------------------------------

Sieht aus wie verdreht oder sehe ich das irgendwie falsch??


This thread was automatically locked due to age.
Parents
  • Das siehst du falsch [:)], bei einem Reverse DNS Lookup (also "Welcher DNS-Name gehört zu dieser IP-Adresse?") ist diese Schreibweise völlig korrekt.
    Siehe auch Wikipedia: Reverse DNS

    ----------
    Sophos user, admin and reseller.
    Private Setup:

    • XG: HPE DL20 Gen9 (Core i3-7300, 8GB RAM, 120GB SSD) | XG 18.0 (Home License) with: Web Protection, Site-to-Site-VPN (IPSec, RED-Tunnel), Remote Access (SSL, HTML5)
    • UTM: 2 vCPUs, 2GB RAM, 50GB vHDD, 2 vNICs on vServer (KVM) | UTM 9.7 (Home License) with: Email Protection, Webserver Protection, RED-Tunnel (server)
Reply
  • Das siehst du falsch [:)], bei einem Reverse DNS Lookup (also "Welcher DNS-Name gehört zu dieser IP-Adresse?") ist diese Schreibweise völlig korrekt.
    Siehe auch Wikipedia: Reverse DNS

    ----------
    Sophos user, admin and reseller.
    Private Setup:

    • XG: HPE DL20 Gen9 (Core i3-7300, 8GB RAM, 120GB SSD) | XG 18.0 (Home License) with: Web Protection, Site-to-Site-VPN (IPSec, RED-Tunnel), Remote Access (SSL, HTML5)
    • UTM: 2 vCPUs, 2GB RAM, 50GB vHDD, 2 vNICs on vServer (KVM) | UTM 9.7 (Home License) with: Email Protection, Webserver Protection, RED-Tunnel (server)
Children