DDNS & NAT

[#1]

I have an old Fortigate60 I am using for testing. The broadband ADSL connection is just a home connection so no static IP' s. The ADSL connects into the modem/router which I have configured to redirect all traffic to the WAN1 interface on the fortigate. So it goes public IP <NAT Router> 192.168.2.x <NAT Fortigate> my network 192.168.0.x So everything is working great assuming I know what the public IP is.. which I won' t always so I set up Dynamic DNS. I had a NAS configured to update dyndns.com but I would like to switch that off. I spotted the DDNS setting on the Fortigate 60 and though problem solved. Unfortunately when I enable that it sets the DynDNS to 192.168.2.3 (the IP of the WAN1 interface) instead of checking the external address and updating it with that. Is there any way to resolve this issue? Thanks (sorry for the life story)

[ede_pfau]

Hi, and welcome to the forums. The DDNS feature on the FGT will always report the WAN interface IP. Fortinet chose to make this feature independent on external hosts. The (well known and proved) workaround is to switch the ADSL router into bridging mode = to use it as a modem only. No forwarding, just interfacing. The FGT will hold the PPPoE parameters and take care of the dial-out. And the WAN interface will get the public IP. There' s nothing in such a scenario that a router in front of the FGT would improve. Think of DDNS, VPN, WAN failover, and you' ll see direct interfacing is much more promising.

[#3]

Thanks for that, the router isn' t there for any reason other than I don' t have another ADSL modem, that router is also provided by an ISP and is cheap and nasty, I don' t have an option to put it into bridging mode, I did find the router also has a DDNS client on it which solves my issue for now.