FQDN address is not working

[saim]

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.

[mEjdejBDG]

After nslookup on this server, I get ' DNS request timed out' When I added in Windows hosts file, IP nad name of google maps it works in the browser, but it seems weird. There' s no map etc.. I' ve changed policy to ALL in destination, and it works :| I have no idea what' s wrong

[ede_pfau]

just to clarify: if you put one single object into the policy, it works. Which kind of object then, FQDN or IP?

[FlavioB]

Hallo Ede. Yes, if I put a single FQDN-based Firewall Object in the source of the policy, it works. F.

[mEjdejBDG]

Hi, It doesn' t work for me... I' ve put address object in group, I' ve changed names of addresses to single-word. Nothing works.

[FlavioB]

Hy. That' s really quite strange. I managed to put all the FQDN objects (which have spaces in their names too!) into a group (which too has spaces in its name). I re-created a policy with that group and it works! MR3 Patch7 Regards, F.

[RindlisE]

Hi mEjdejBDG After lots of tests try this as a Workaround: 1. Use a dedicated Policy with Address Obects (IP/Subnet). 2. Use a second Policy with FQDN Objects. Do not mix different types of Objects (FQDN, IP/Subnet..). Keep in mind, this is only a Workaround. Hope Fortinet will fix this bug soon... Regards Erich

[FlavioB]

Hy. Actually Fortinet knows that it is a bug. Don' t know when it' ll be solved though... F.

[Phuoc_Ngo]

Anyone know whether this issue get resolve in MR3 patch7? This issue seem to impact us big time.

[FlavioB]

The problem is not solved in v4p3mr7, as we have that version on the " faulty" device config. It has been recognised as a bug, actually. Regards, F.

[RindlisE]

Hi, Try to use this Workaround. create a Group Object and put your Address Object in this Group. Use the Group Object in your Rule. Regards Erich