Skip to main content
Anand_Narayana
Explorer
February 10, 2023
Solved

Firewall unable to resolve Private IP - DNS Translation

  • February 10, 2023
  • 1 reply
  • 3421 views

I have FG-80F (Firmware version 7.2.4 build1396) in one of the branch office which we have recently purchased and configured. I have configured DNS translation as follows and internal hosts behind this firewall is able to resolve to the Private IP 172.24.0.1 as expected. However, when I try ping or configure the hostname (testing.abc.com) in the Threatfeeds configuration, it resolves to Public IP address 181.182.183.184. I have FG-500D (Firmware version 6.4.11 build2030) and that firewall is able to resolve with the private IP. Anything that I am missing here?

 

config firewall dnstranslation
edit 1
set src 181.182.183.184 --> Public IP as an example for "testing.abc.com"
set dst 172.24.0.1 --> Private IP of testing.abc.com

end

 

hostname - "testing.abc.com"

 

PS : Hostname & Public IP address are just an example and not actuals.

Best answer by Anand_Narayana

It appears the issue is resolved now after formatting and re-imaging the FortiGate FG-80F

1 reply

Anand_Narayana
Anand_NarayanaAuthorAnswer
Explorer
February 10, 2023

It appears the issue is resolved now after formatting and re-imaging the FortiGate FG-80F

Thought Leadership Security Summit. Outpace New Threats with AI - enhanced defense. Tuesday, Septmeber 15, 8:30 AM - 2:30 PM PT. The Golf Club at Newcastle, WA.
Fortinet Flag the Hack. Wednesday, August 26, 9:00 AM - 5:00 PM ET, COSM, Atlanta, GA.
Virtual event | September 2026. SASE summit. The age of autonomous trust. Register here!