Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 8 replies
  • Subscribers 2 subscribers
  • Views 2417 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

No Hostname found

reddyfire
When I view logs and network activity information any internal based IP addresses come up as "hostname not found" under the hostname information.  What would I need to do in order for the internal DNS names to be resolved by the Astaro firewall?  Thanks.


This thread was automatically locked due to age.
  • 0
    Under Network Services -> DNS -> Request Routing, you need to create a route for your internal reverse zone to your internal DNS server, e.g. 0.168.192.in-addr.arpa -> mydns_server
  • 0
    also, you should join it to the domain, so the AD or DNS on you organization can registered so you won't need to do it manually
  • 0
    Great suggestion sgkross!  In fact, one of the most-common reasons people can't get their Astaro to join their AD is because they added the machine name manually at some point in the past.

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0
    Thanks everyone.  I will give the above suggestions a try.

    Edit:  Checked the DNS settings.  We already have a configured route under DNS request routing services to our Domain controller.  The firewall has already been joined to Active Directory as well... Any other ideas?  Thanks.
  • 0
    I suggest you to make sure the ICMP settings are correct on the *Network Security / Packet Filter * and the ICMP Tab; I have the following options selected under Ping Settings:
    Firewall is Ping Vissible
    Ping from Firewal    l

    *just in case after applying this settings try to restart the ASG and check again if the settings were saved properly [:)]
  • 0 in reply to reddyfire
    We already have a configured route under DNS request routing services to our Domain controller.
    For both the forward and reverse zones?
  • 0
    Like Jetkins said above, you also need the Request Route for Reverse DNS: 0.168.192.in-addr.arpa -> mydns_server

    Cheers - Bob
    PS You might want to check out: [SOLVED] DNS Best Practice
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0
    Of course the reverse zone will have to match your internal subnet - 0.168.192.in-addr.arpa is just an example if you use 192.168.0.0/24
Cookie Information Banner