Skip to main content
ilya-draigor
New Member
February 5, 2026
Question

FTM push responses not working (dns problem ?)

  • February 5, 2026
  • 2 replies
  • 200 views

Hi,

 

I'm trying to setup the FTM with FortiToken Cloud.

 

  • User login in FortiClient IPsec VPN
  • FortiGate sends push request to my phone
  • Tapping Allow 
  • Getting notification on my phone “request sent”
  • And nothing happen

 

fortigate debug:

diagnose debug reset
diagnose debug console timestamp enable
diagnose debug application forticldd -1
diagnose debug enable
2026-02-05 20:51:20 [263] fds_resolv_addr: resolve 'eufctupdate.fortinet.net'  2026-02-05 20:51:20 [189] fds_get_addr: name=eufctupdate.fortinet.net, id=10208, cb=0x5555ff9c60  2026-02-05 20:51:20 [185] fds_svr_default_timeout: try to get IPs for Forticlient-svr  2026-02-05 20:51:20 [52] dns_parse_resp: DNS resp-id=10208  2026-02-05 20:51:20 [74] dns_parse_resp: eufctupdate.fortinet.net: rcode=3  2026-02-05 20:51:20 [52] dns_parse_resp: DNS resp-id=10208  2026-02-05 20:51:20 [74] dns_parse_resp: eufctupdate.fortinet.net: rcode=3  2026-02-05 20:51:21 [4089] fds_handle_request: Received cmd 117 from pid-1328, len 4  2026-02-05 20:51:21 [3838] fds_check_request: Image list was updated within 86400 secs.  2026-02-05 20:51:21 [583] fds_send_reply2: Sending 4768 bytes data, data2len=0.  2026-02-05 20:51:26 [4089] fds_handle_request: Received cmd 116 from pid-1328, len 0  2026-02-05 20:51:26 [583] fds_send_reply2: Sending 72 bytes data, data2len=0.  2026-02-05 20:51:26 [4089] fds_handle_request: Received cmd 116 from pid-1328, len 0  2026-02-05 20:51:26 [583] fds_send_reply2: Sending 72 bytes data, data2len=0.  2026-02-05 20:51:35 [263] fds_resolv_addr: resolve 'eufctupdate.fortinet.net'  2026-02-05 20:51:35 [189] fds_get_addr: name=eufctupdate.fortinet.net, id=10224, cb=0x5555ff9c60  2026-02-05 20:51:35 [185] fds_svr_default_timeout: try to get IPs for Forticlient-svr  2026-02-05 20:51:35 [52] dns_parse_resp: DNS resp-id=10224  2026-02-05 20:51:35 [74] dns_parse_resp: eufctupdate.fortinet.net: rcode=3  2026-02-05 20:51:35 [52] dns_parse_resp: DNS resp-id=10224  2026-02-05 20:51:35 [74] dns_parse_resp: eufctupdate.fortinet.net: rcode=3  2026-02-05 20:51:50 [263] fds_resolv_addr: resolve 'eufctupdate.fortinet.net'  2026-02-05 20:51:50 [189] fds_get_addr: name=eufctupdate.fortinet.net, id=10240, cb=0x5555ff9c60  2026-02-05 20:51:50 [185] fds_svr_default_timeout: try to get IPs for Forticlient-svr  2026-02-05 20:51:50 [52] dns_parse_resp: DNS resp-id=10240  2026-02-05 20:51:50 [74] dns_parse_resp: eufctupdate.fortinet.net: rcode=3  2026-02-05 20:51:50 [52] dns_parse_resp: DNS resp-id=10240  2026-02-05 20:51:50 [74] dns_parse_resp: eufctupdate.fortinet.net: rcode=3  2026-02-05 20:52:05 [263] fds_resolv_addr: resolve 'eufctupdate.fortinet.net'  2026-02-05 20:52:05 [189] fds_get_addr: name=eufctupdate.fortinet.net, id=10256, cb=0x5555ff9c60  2026-02-05 20:52:05 [185] fds_svr_default_timeout: try to get IPs for Forticlient-svr  2026-02-05 20:52:05 [52] dns_parse_resp: DNS resp-id=10256  2026-02-05 20:52:05 [74] dns_parse_resp: eufctupdate.fortinet.net: rcode=3  2026-02-05 20:52:05 [52] dns_parse_resp: DNS resp-id=10256  2026-02-05 20:52:05 [74] dns_parse_resp: eufctupdate.fortinet.net: rcode=3  2026-02-05 20:52:20 [263] fds_resolv_addr: resolve 'eufctupdate.fortinet.net'  2026-02-05 20:52:20 [189] fds_get_addr: name=eufctupdate.fortinet.net, id=10272, cb=0x5555ff9c60  2026-02-05 20:52:20 [185] fds_svr_default_timeout: try to get IPs for Forticlient-svr  2026-02-05 20:52:20 [52] dns_parse_resp: DNS resp-id=10272  2026-02-05 20:52:20 [74] dns_parse_resp: eufctupdate.fortinet.net: rcode=3  2026-02-05 20:52:20 [52] dns_parse_resp: DNS resp-id=10272  2026-02-05 20:52:20 [74] dns_parse_resp: eufctupdate.fortinet.net: rcode=3  2026-02-05 20:52:35 [263] fds_resolv_addr: resolve 'eufctupdate.fortinet.net'  2026-02-05 20:52:35 [189] fds_get_addr: name=eufctupdate.fortinet.net, id=10288, cb=0x5555ff9c60  2026-02-05 20:52:35 [185] fds_svr_default_timeout: try to get IPs for Forticlient-svr  2026-02-05 20:52:35 [52] dns_parse_resp: DNS resp-id=10288  2026-02-05 20:52:35 [74] dns_parse_resp: eufctupdate.fortinet.net: rcode=3  2026-02-05 20:52:35 [52] dns_parse_resp: DNS resp-id=10288  2026-02-05 20:52:35 [74] dns_parse_resp: eufctupdate.fortinet.net: rcode=3  2026-02-05 20:52:50 [263] fds_resolv_addr: resolve 'eufctupdate.fortinet.net'  2026-02-05 20:52:50 [189] fds_get_addr: name=eufctupdate.fortinet.net, id=10304, cb=0x5555ff9c60  2026-02-05 20:52:50 [185] fds_svr_default_timeout: try to get IPs for Forticlient-svr  2026-02-05 20:52:50 [52] dns_parse_resp: DNS resp-id=10304  2026-02-05 20:52:50 [74] dns_parse_resp: eufctupdate.fortinet.net: rcode=3  2026-02-05 20:52:50 [52] dns_parse_resp: DNS resp-id=10304  2026-02-05 20:52:50 [74] dns_parse_resp: eufctupdate.fortinet.net: rcode=3

 

dns_parse_resp: eufctupdate.fortinet.net: rcode=3

FortiGate can't resolve the hostname? 

 

Latest version: v7.6.6

What i'm missing here ?

 

Regards!

 

2 replies

AEK
SuperUser
SuperUser
February 8, 2026

Hi Ilya

I didn't work work with FTK cloud before but first thing I notice is eufctupdate.fortinet.net doesn't resolve to any public IP.

AEK
Markus_M
Staff & Editor
Staff & Editor
February 8, 2026

Please add the fortitoken debug to the set:
diag debug console timestamp enable
diag debug app forticldd -1
diag fortitoken debug enable
diag debug enable
Do you have any logs on FortiTokenCloud that'd say anything about these push responses from the phone?

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.
Virtual event | September 2026. SASE summit. The age of autonomous trust. Register here!