FOTA- download_client: Failed to resolve hostname firmware.nrfcloud.com on IPv4

[zsn]

Hi. 

I tried to test FOTA on the nrf9160dk board with NCS2.2.0 using the nRF Cloud.  I followed these instructions: 

https://docs.nrfcloud.com/Devices/FirmwareUpdate/FOTATutorial/

So, I am getting this error:

2023-01-12T22:41:59.766Z DEBUG modem << +CSCON: 1
2023-01-12T22:42:02.295Z DEBUG modem << [01:10:18.341,400] [1;33m<wrn> download_client: Failed to resolve hostname firmware.nrfcloud.com on IPv4[0m
2023-01-12T22:42:02.356Z DEBUG modem << [01:10:18.341,430] [1;31m<err> nrf_cloud_fota: Failed to start FOTA download: -118[0m
2023-01-12T22:42:02.363Z DEBUG modem << [01:10:18.341,461] [1;31m<err> nrf_cloud_transport: NRF_CLOUD_FOTA_EVT_ERROR[0m
2023-01-12T22:42:02.369Z DEBUG modem << [01:10:18.341,522] [0m<inf> app_event_manager: CLOUD_EVT_FOTA_ERROR[0m
2023-01-12T22:42:02.378Z DEBUG modem << [01:10:18.471,160] [0m<inf> nrf_cloud_fota: Job 7b3c4a61-4dae-43a1-ac5d-f14b14f0144f already completed... skipping[0m
2023-01-12T22:42:02.384Z DEBUG modem << [01:10:18.473,052] [0m<inf> nrf_cloud_fota: Job 7b3c4a61-4dae-43a1-ac5d-f14b14f0144f already completed... skipping[0m
2023-01-12T22:42:08.343Z DEBUG modem << +CSCON: 0
2023-01-12T22:42:08.555Z DEBUG modem << %CESQ: 55,2,24,3

P.S

when I create an asset-tracker app, it does not establish a connection to nrf cloud unless I change/define the hostname in the .prj file as 

CONFIG_NRF_CLOUD_HOST_NAME="a2n7tk1kp18wix-ats.iot.us-east-1.amazonaws.com"

Thanks

[Michal]

Hello,

I am looking into it and will come back when I'll have more information.

Best regards,

Michal

[Michal]

Sorry for the delays, I am still looking at it and will return to you as soon as possible. If there have been any changes in the meantime please let me know.

Best regards,

Michal

[Michal]

I did the FOTA on Asset Tracker v2 on NCS 2.2.0 without any issues using nRF Cloud and the provided tutorial.

I am not sure why would you need to configure the nRF Cloud host name.

Best regards,

Michal

[zsn]

Hi Michal, I solved the problem, its related to the service provider in my region, But I still don't understand how this hostname is not working while the other is working!

[Michal]

I will consult our experts about it.

Best regards,

Michal