Hot!Unable to resolve ip to hostname

New Member
  • Total Posts : 1
  • Scores: 0
  • Reward points: 0
  • Joined: 2019/03/14 12:54:59
  • Status: offline
2019/03/14 13:10:08 (permalink)

Unable to resolve ip to hostname

I just started to use a fortigate router.
 i've got it working but have a configuration problem.
I'm able to ping a hostname but i'm unable to get an ip to hostname name resolving (ping -a)
The clients receive their ip from the dhcp of the fortigate.
Can somebody explain to me how I need to setup this in the webinterface.

2 Replies Related Threads

    Gold Member
    • Total Posts : 125
    • Scores: 21
    • Reward points: 0
    • Joined: 2018/11/28 14:57:58
    • Location: Sedalia, MO
    • Status: offline
    Re: Unable to resolve ip to hostname 2019/04/07 04:22:27 (permalink)
    Where do your clients register their DNS?  ping -a relies on reverse DNS (PTR records), so regardless of who does DHCP, it sounds like you have a DNS issue, so probably not a FortiGate thing at all.
    Expert Member
    • Total Posts : 5927
    • Scores: 466
    • Reward points: 0
    • Joined: 2004/03/09 01:20:18
    • Location: Heidelberg, Germany
    • Status: offline
    Re: Unable to resolve ip to hostname 2019/04/07 08:27:39 (permalink)
    If you created a zone on your FGT, and you need reverse lookup, you need to additionally create a PTR zone. PTR records are not created automatically like with e.g. a Windows DNS. It's quite cumbersome to do so, though.


    " Kernel panic: Aiee, killing interrupt handler!"
    Jump to:
    © 2019 APG vNext Commercial Version 5.5