Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
saim
New Contributor

FQDN address is not working

Hi, I have fortigate 1000A I am using version v4.0,build0521,120313 (MR3 Patch 6). I have added in address imap.gmail.com but its not working. I have checked everything is fine as I give IP address it works. any idea.
Saim.... FortiGate 1000A (v4.0,build0535,120511 (MR3 Patch 7)) FortiAnalyzer-800B (v4.0,build0654 (MR3 Patch 3))
Saim.... FortiGate 1000A (v4.0,build0535,120511 (MR3 Patch 7)) FortiAnalyzer-800B (v4.0,build0654 (MR3 Patch 3))
32 REPLIES 32
rwpatterson
Valued Contributor III

Welcome to the forums. What do you have for your DNS servers (in the unit)? Or better yet, can the FGT resolve that address from the CLI?

Bob - self proclaimed posting junkie!
See my Fortigate related scripts at: http://fortigate.camerabob.com

Bob - self proclaimed posting junkie!See my Fortigate related scripts at: http://fortigate.camerabob.com
ede_pfau
SuperUser
SuperUser

...by typing
 exec ping www.whatsmyip.com   // just an example
Ede Kernel panic: Aiee, killing interrupt handler!
Ede Kernel panic: Aiee, killing interrupt handler!
mthayes
New Contributor

In the policy that has the FQDN address, are there any addresses with IP instead of FQDN. There is a bug that makes policies not work with mixed address types. If so create a new policy for each address type, FQDN and IP addresses. While the changelog states that this bug is fixed in patch 6, I still had the issue with some of my policies.
seadave

Thanks for this post. This was driving me nuts. Now I know why it wasn' t working.
saim
New Contributor

Hi All, Thanks for your reply. I am able to ping from FortiGate device. As per the suggestion of " mthayes" I will create a new policy and check. Meanwhile I have talked to Fortigate support they have agree that there is bug and will be solved in next patch which will be released in first week of May 12.
Saim.... FortiGate 1000A (v4.0,build0535,120511 (MR3 Patch 7)) FortiAnalyzer-800B (v4.0,build0654 (MR3 Patch 3))
Saim.... FortiGate 1000A (v4.0,build0535,120511 (MR3 Patch 7)) FortiAnalyzer-800B (v4.0,build0654 (MR3 Patch 3))
saim
New Contributor

I have created individual rule only with FQDN but didn' t get success.
Saim.... FortiGate 1000A (v4.0,build0535,120511 (MR3 Patch 7)) FortiAnalyzer-800B (v4.0,build0654 (MR3 Patch 3))
Saim.... FortiGate 1000A (v4.0,build0535,120511 (MR3 Patch 7)) FortiAnalyzer-800B (v4.0,build0654 (MR3 Patch 3))
saim
New Contributor

Hi All, Fortinet have recently released MR3 Patch 7 and FQDN issue is gone. Thanks,
Saim.... FortiGate 1000A (v4.0,build0535,120511 (MR3 Patch 7)) FortiAnalyzer-800B (v4.0,build0654 (MR3 Patch 3))
Saim.... FortiGate 1000A (v4.0,build0535,120511 (MR3 Patch 7)) FortiAnalyzer-800B (v4.0,build0654 (MR3 Patch 3))
mEjdejBDG
New Contributor

Hi All. I have the same issues with FQDN. I did firmware upgrade to MR3 Patch 7 and it didn' t help.. I need to access from one of my servers placed in LAN, to the URL: maps.google.com. I' ve checked policy many times, I' ve checked with different URLs, and it doesn' t work. I need some solution until tommorow morning. PS. Hmm, it' s very weird - when I pinging Google Maps IP from this server, I get replies.
ede_pfau
SuperUser
SuperUser

Could you please post your policy (from CLI)? Are there other policies for that interface pair ABOVE the one in question? What are you trying to achieve? A policy with a FQDN destination address is not the same as a URL filter, for instance.
Ede Kernel panic: Aiee, killing interrupt handler!
Ede Kernel panic: Aiee, killing interrupt handler!
Announcements

Select Forum Responses to become Knowledge Articles!

Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.

Labels
Top Kudoed Authors