BC66 NTP synchronization not working with IPv6 address

Hi,

I am trying to synchronize my module’s time with the NTP server using AT+QNTP command.

I am connected to NB-IoT IPv6 only network. I am using the NTP server which supports IPv6 but I am not able to execute this operation successfully. I am getting a error +QNTP:550 (other error) instead of the synched current time.

I also tried giving the IP address of the IPv6 NTP server instead of its domain name. I can only communicate with IPv6 - IPv6 address because of the network operator constraints.

Here are the logs from my serial console:

[2022-09-22_16:11:04:625]At+qntp=1,"2.pool.ntp.org"

[2022-09-22_16:11:04:625]OK
[2022-09-22_16:11:44:633]
[2022-09-22_16:11:44:633]+QNTP: 550

Thanks in advance.

Have you tried using an IP to NTP connection? Still fail?

Yes I tried and it still fails. The error is +QNTP:550 (other error). Can the error be checked in any way that what other error it is?

What is your current firmware version of BC66?

My current firmware version is BC66NBR01A11.

[2022-09-23_10:37:33:481]at+CGMR

[2022-09-23_10:37:33:481]Revision: BC66NBR01A11

[2022-09-23_10:37:33:481]OK

Can modules interact with data? such as using TCP?

Yes I have tested that with Lwm2m and MQTT connections and data transfer. It is working fine.
I was also able to ping to the servers and get their IP address from domain name. Only that thing that is not working is NTP.

ntp: time.google.com
time1.google.com
time2.google.com
time3.google.com

you try it again

Hi I tried with all the servers it is still the same error. I tried pinging all of the servers that you mentioned Ping is successful. I also tried to get its IP by DNS It is also working fine. Here is the output of my console.

[2022-09-23_12:50:25:277]AT+QNTP=1,"time.google.com"

[2022-09-23_12:50:25:277]OK
[2022-09-23_12:51:05:286]
[2022-09-23_12:51:05:286]+QNTP: 550
[2022-09-23_12:51:07:154]AT+QNTP=1,"time1.google.com"

[2022-09-23_12:51:07:154]OK
[2022-09-23_12:51:47:132]
[2022-09-23_12:51:47:132]+QNTP: 550
[2022-09-23_12:52:15:535]AT+QNTP=1,"time2.google.com"

[2022-09-23_12:52:15:535]OK
[2022-09-23_12:52:55:518]
[2022-09-23_12:52:55:518]+QNTP: 550
[2022-09-23_12:53:20:496]AT+QNTP=1,"time3.google.com"

[2022-09-23_12:53:20:496]OK
[2022-09-23_12:54:00:492]
[2022-09-23_12:54:00:492]+QNTP: 550


The console’s output for Ping

[2022-09-23_14:17:02:130]AT+QPING=1,"time.google.com"

[2022-09-23_14:17:02:168]OK
[2022-09-23_14:17:02:715]
[2022-09-23_14:17:02:715]+QPING: 0,"2001:4860:4806:4:0:0:0:0",32,470,59
[2022-09-23_14:17:04:318]
[2022-09-23_14:17:04:318]+QPING: 0,"2001:4860:4806:4:0:0:0:0",32,590,59
[2022-09-23_14:17:05:912]
[2022-09-23_14:17:05:912]+QPING: 0,"2001:4860:4806:4:0:0:0:0",32,590,59
[2022-09-23_14:17:07:534]
[2022-09-23_14:17:07:534]+QPING: 0,"2001:4860:4806:4:0:0:0:0",32,590,59

[2022-09-23_14:17:07:534]+QPING: 0,4,4,0,470,590,560
[2022-09-23_14:17:12:636]AT+QPING=1,"time1.google.com"

[2022-09-23_14:17:12:667]OK
[2022-09-23_14:17:13:957]
[2022-09-23_14:17:13:957]+QPING: 0,"2001:4860:4806:0:0:0:0:0",32,610,107
[2022-09-23_14:17:15:701]
[2022-09-23_14:17:15:701]+QPING: 0,"2001:4860:4806:0:0:0:0:0",32,730,107
[2022-09-23_14:17:17:888]
[2022-09-23_14:17:17:888]+QPING: 0,"2001:4860:4806:0:0:0:0:0",32,1170,107
[2022-09-23_14:17:19:448]
[2022-09-23_14:17:19:448]+QPING: 0,"2001:4860:4806:0:0:0:0:0",32,520,107

[2022-09-23_14:17:19:448]+QPING: 0,4,4,0,520,1170,757
[2022-09-23_14:17:23:664]AT+QPING=1,"time2.google.com"

[2022-09-23_14:17:23:695]OK
[2022-09-23_14:17:24:852]
[2022-09-23_14:17:24:852]+QPING: 0,"2001:4860:4806:4:0:0:0:0",32,230,109
[2022-09-23_14:17:26:304]
[2022-09-23_14:17:26:304]+QPING: 0,"2001:4860:4806:4:0:0:0:0",32,440,59
[2022-09-23_14:17:27:748]
[2022-09-23_14:17:27:748]+QPING: 0,"2001:4860:4806:4:0:0:0:0",32,430,59
[2022-09-23_14:17:29:229]
[2022-09-23_14:17:29:229]+QPING: 0,"2001:4860:4806:4:0:0:0:0",32,430,109

[2022-09-23_14:17:29:229]+QPING: 0,4,4,0,230,440,382
[2022-09-23_14:17:33:398]AT+QPING=1,"time3.google.com"

[2022-09-23_14:17:33:398]OK
[2022-09-23_14:17:34:386]
[2022-09-23_14:17:34:386]+QPING: 0,"2001:4860:4806:8:0:0:0:0",32,270,59
[2022-09-23_14:17:36:037]
[2022-09-23_14:17:36:037]+QPING: 0,"2001:4860:4806:8:0:0:0:0",32,650,59
[2022-09-23_14:17:37:558]
[2022-09-23_14:17:37:558]+QPING: 0,"2001:4860:4806:8:0:0:0:0",32,510,59
[2022-09-23_14:17:39:304]
[2022-09-23_14:17:39:304]+QPING: 0,"2001:4860:4806:8:0:0:0:0",32,690,59

[2022-09-23_14:17:39:304]+QPING: 0,4,4,0,270,690,530

console output for QIDNSGIP

[2022-09-23_14:18:32:561]AT+qidnsgip=1,"time.google.com"

[2022-09-23_14:18:32:561]OK

[2022-09-23_14:18:32:561]+QIURC: "dnsgip",0,1,0

[2022-09-23_14:18:32:561]+QIURC: "dnsgip","2001:4860:4806:4:0:0:0:0"
[2022-09-23_14:18:40:643]AT+qidnsgip=1,"time1.google.com"

[2022-09-23_14:18:40:643]OK

[2022-09-23_14:18:40:643]+QIURC: "dnsgip",0,1,0

[2022-09-23_14:18:40:643]+QIURC: "dnsgip","2001:4860:4806:0:0:0:0:0"
[2022-09-23_14:18:46:389]AT+qidnsgip=1,"time2.google.com"

[2022-09-23_14:18:46:389]OK

[2022-09-23_14:18:46:389]+QIURC: "dnsgip",0,1,0

[2022-09-23_14:18:46:389]+QIURC: "dnsgip","2001:4860:4806:4:0:0:0:0"
[2022-09-23_14:18:54:552]AT+qidnsgip=1,"time3.google.com"

[2022-09-23_14:18:54:552]OK

[2022-09-23_14:18:54:552]+QIURC: "dnsgip",0,1,0

[2022-09-23_14:18:54:552]+QIURC: "dnsgip","2001:4860:4806:8:0:0:0:0"

I have tried most of the debugging methods.

Is this an issue with the version of firmware?