DYNDNS not working

[#1]

Hello all, i have a dyndns account and i' m trying to configure my fortigate 60 to update the host ip address automatically but it is not working. The Fortigate is connected to a cable modem and gets the wan1 ip address through dhcp. Is there some way to diagnose the problem? Thank you PM

[rwpatterson]

On the network tab, select the WAN1 interface In the drop down, choose the DYNDNS provider for the domain, use the name you have chosen, from your custom host name all the way through to the TLD. Enter the user name and password that you use to log in. That should be all. TLD = Top Level Domain: .com, .org, etc.

[#3]

Hello Bob, thank you for your help. Well, i' ve done that already but unfortunatelly it is not working all the time. Is there some detailed log event i could inspect? PM

[abelio]

You could try sniff the communicatio between wan interface and members.dyndns.org usually they use port 80, but they can use another ones too. members.dyndns.org resolves to 63.208.196.96 cli command:

 diagnose sniffer packet any " host 63.208.196.96" 
 

(turn off and on " DDNS" box in WAN iface configuration to generate some traffic)

[#5]

Great, exactly what i was looking for (i' m a fortigate greenhorn ) So far i' ve tryed it and get the following output (a little bit unsharpened):

 20.027858 91.89.xx.xx.1444 -> 63.208.196.96.80: syn 340132630
 20.126440 63.208.196.96.80 -> 91.89.xx.xx.1444: syn 1925944532 ack 340132631
 20.126542 91.89.xx.xx.1444 -> 63.208.196.96.80: ack 1925944533
 20.127748 91.89.xx.xx.1444 -> 63.208.196.96.80: psh 340132631 ack 1925944533
 20.234570 63.208.196.96.80 -> 91.89.xx.xx.1444: psh 1925944533 ack 340132813
 20.234624 63.208.196.96.80 -> 91.89.xx.xx.1444: fin 1925944656 ack 340132813
 20.235313 91.89.xx.xx.1444 -> 63.208.196.96.80: ack 1925944656
 20.235376 91.89.xx.xx.1444 -> 63.208.196.96.80: ack 1925944657
 20.236435 91.89.xx.xx.1444 -> 63.208.196.96.80: fin 340132813 ack 1925944657
 20.339653 63.208.196.96.80 -> 91.89.xx.xx.1444: ack 340132814
 

Doesn' t seem that bad actually, what do you think?

[abelio]

Doesn' t seem that bad actually, what do you think?

same opinion, it' s not a networking problem. I' ll re-check FGT members.dyndns.org settings user/pass/hostname directly in www.dyndns.org once again

[#7]

Oh boy, i cannot believe! In the text box " Domain" i had only the domain part of the fqdn instead of the all host.fqdn thus it couldn' t match! Big thanks for your help!