Home Network Community > Deco > Deco M9 plus is querying wrong public NTP server after firmware update
< Deco

Deco M9 plus is querying wrong public NTP server after firmware update

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Deco M9 plus is querying wrong public NTP server after firmware update

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Deco M9 plus is querying wrong public NTP server after firmware update
Deco M9 plus is querying wrong public NTP server after firmware update
2020-06-09 21:50:52
Model: Deco M9 Plus  
Hardware Version: V1
Firmware Version: 1.4.0 Build 20200324 Rel. 51287

After upgrading my M9Plus(1.0) to firmware version 1.4.0 Build 20200324 Rel. 51287
my DNS server gets hammered with non existing NTP server query's (see below)
The correct name should be: europe.pool.ntp.org

eu.pool.ntp.org does not exists.


Can this be fixed?

 

Log DNS Server:

Jun  9 22:52:53 dnsmasq[1074]: cached eu.pool.ntp.org is NODATA-IPv4
Jun  9 22:52:57 dnsmasq[1074]: query[AAAA] eu.pool.ntp.org from 192.168.1.101
Jun  9 22:52:57 dnsmasq[1074]: cached eu.pool.ntp.org is NODATA-IPv6
Jun  9 22:52:57 dnsmasq[1074]: query[A] eu.pool.ntp.org from 192.168.1.101
Jun  9 22:52:57 dnsmasq[1074]: cached eu.pool.ntp.org is NODATA-IPv4
Jun  9 22:52:59 dnsmasq[1074]: query[AAAA] eu.pool.ntp.org from 192.168.1.102
Jun  9 22:52:59 dnsmasq[1074]: cached eu.pool.ntp.org is NODATA-IPv6
Jun  9 22:52:59 dnsmasq[1074]: query[A] eu.pool.ntp.org from 192.168.1.102
Jun  9 22:52:59 dnsmasq[1074]: cached eu.pool.ntp.org is NODATA-IPv4
Jun  9 22:53:03 dnsmasq[1074]: query[AAAA] eu.pool.ntp.org from 192.168.1.101
Jun  9 22:53:03 dnsmasq[1074]: cached eu.pool.ntp.org is NODATA-IPv6
Jun  9 22:53:03 dnsmasq[1074]: query[A] eu.pool.ntp.org from 192.168.1.101
Jun  9 22:53:03 dnsmasq[1074]: cached eu.pool.ntp.org is NODATA-IPv4
Jun  9 22:53:05 dnsmasq[1074]: query[AAAA] eu.pool.ntp.org from 192.168.1.102
Jun  9 22:53:05 dnsmasq[1074]: cached eu.pool.ntp.org is NODATA-IPv6
Jun  9 22:53:05 dnsmasq[1074]: query[A] eu.pool.ntp.org from 192.168.1.102
Jun  9 22:53:05 dnsmasq[1074]: cached eu.pool.ntp.org is NODATA-IPv4
Jun  9 22:53:09 dnsmasq[1074]: query[AAAA] eu.pool.ntp.org from 192.168.1.101
Jun  9 22:53:09 dnsmasq[1074]: cached eu.pool.ntp.org is NODATA-IPv6
Jun  9 22:53:09 dnsmasq[1074]: query[A] eu.pool.ntp.org from 192.168.1.101
Jun  9 22:53:09 dnsmasq[1074]: cached eu.pool.ntp.org is NODATA-IPv4
Jun  9 22:53:11 dnsmasq[1074]: query[AAAA] eu.pool.ntp.org from 192.168.1.102
Jun  9 22:53:11 dnsmasq[1074]: cached eu.pool.ntp.org is NODATA-IPv6
Jun  9 22:53:11 dnsmasq[1074]: query[A] eu.pool.ntp.org from 192.168.1.102
Jun  9 22:53:11 dnsmasq[1074]: cached eu.pool.ntp.org is NODATA-IPv4

 

Made a workaround to add static DNS record to my DNS server to an existing NTP IP address for this non existing pool.

  1      
 
  1      
 
#1
Options
5 Reply
Re:Deco M9 plus is querying wrong public NTP server after firmware update
2020-07-21 20:17:29

@Longface 

 

I facing the same issue. After updating to Deco M9 Plus(EU)_V1_200324 (1.4.0 Build 20200324 Rel. 51287) all my M9 devices are trying to connect to eu.pool.ntp.org

 

Top Clients (total)

Client Requests
192.168.1.100 27818
192.168.1.102 27814

 

 

Is there already a solution?

Will this be solved soon? 

Is there a work around to solve this?


 

2020-07-21 22:01:25 A eu.pool.ntp.org 192.168.1.100 OK (cached) NXDOMAIN (0.1ms)  Blacklist
2020-07-21 22:01:25 AAAA eu.pool.ntp.org 192.168.1.100 OK (cached) NXDOMAIN (0.2ms)  Blacklist
2020-07-21 22:01:19 A eu.pool.ntp.org 192.168.1.100 OK (cached) NXDOMAIN (0.1ms)  Blacklist
2020-07-21 22:01:19 AAAA eu.pool.ntp.org 192.168.1.100 OK (cached) NXDOMAIN (0.2ms)  Blacklist
2020-07-21 22:01:13 A eu.pool.ntp.org 192.168.1.100 OK (cached) NXDOMAIN (0.1ms)  Blacklist
2020-07-21 22:01:13 AAAA eu.pool.ntp.org 192.168.1.100 OK (cached) NXDOMAIN (0.1ms)  Blacklist
2020-07-21 22:01:07 A eu.pool.ntp.org 192.168.1.100 OK (cached) NXDOMAIN (0.1ms)  Blacklist
2020-07-21 22:01:07 AAAA eu.pool.ntp.org 192.168.1.100 OK (cached) NXDOMAIN (0.2ms)  Blacklist
2020-07-21 22:01:01 A eu.pool.ntp.org 192.168.1.100 OK (cached) NXDOMAIN (0.1ms)  Blacklist
2020-07-21 22:01:01 AAAA eu.pool.ntp.org 192.168.1.100 OK (cached) NXDOMAIN (0.1ms)


 

 

 

Time Type Domain Client Status Reply Action
Time Type Domain Client Status Reply Action
2020-07-21 22:08:49 A eu.pool.ntp.org 192.168.1.102 OK (cached) NXDOMAIN (0.1ms)  Blacklist
2020-07-21 22:08:49 AAAA eu.pool.ntp.org 192.168.1.102 OK (cached) NXDOMAIN (0.1ms)  Blacklist
2020-07-21 22:08:43 A eu.pool.ntp.org 192.168.1.102 OK (cached) NXDOMAIN (0.2ms)  Blacklist
2020-07-21 22:08:43 AAAA eu.pool.ntp.org 192.168.1.102 OK (cached) NXDOMAIN (0.2ms)  Blacklist
2020-07-21 22:08:37 A eu.pool.ntp.org 192.168.1.102 OK (cached) NXDOMAIN (0.2ms)  Blacklist
2020-07-21 22:08:37 AAAA eu.pool.ntp.org 192.168.1.102 OK (cached) NXDOMAIN (0.1ms)  Blacklist
2020-07-21 22:08:31 A eu.pool.ntp.org 192.168.1.102 OK (cached) NXDOMAIN (0.1ms)  Blacklist
2020-07-21 22:08:31 AAAA eu.pool.ntp.org 192.168.1.102 OK (cached) NXDOMAIN (0.2ms)  Blacklist
2020-07-21 22:08:24 A eu.pool.ntp.org 192.168.1.102 OK (cached) NXDOMAIN (0.1ms)  Blacklist
2020-07-21 22:08:24 AAAA eu.pool.ntp.org 192.168.1.102 OK (cached) NXDOMAIN (0.1ms)  Blacklist

 

  0  
  0  
#2
Options
Re:Deco M9 plus is querying wrong public NTP server after firmware update
2020-07-24 12:21:09

@Longface 

I solved this issue temporarily by adding a local DNS rule on my pi-hole.

A normal router should have a simular function to redirect dns.

 

The IP address will change over time... but till then this solves a lot of unneeded traffic.

 

ping europ.pool.nts.org

 

 

Enter the incorrect dns [eu.pool.nts.org] and fill the correct given IP address of [europ.pool.nts.org]

 

  0  
  0  
#3
Options
Re:Deco M9 plus is querying wrong public NTP server after firmware update
2020-09-14 02:22:36

@Longface 

 

So glad I found this post!!

 

Just checked my Pi-hole to see one of my 5 Decos has been doing this for the last 24 hours or so (strange how it never did it before or the other Decos aren't doing it).  

 

pool.nts.org appear to have changed their servers though (https://www.ntppool.org/zone/europe) as I can no longer ping europ.pool.nts.org or europe.pool.nts.org.  0.europe.pool.nts.org etc works.

 

Added a local DNS record as suggested and the problem has gone.

 

Thank you both!

  0  
  0  
#4
Options
Re:Deco M9 plus is querying wrong public NTP server after firmware update
2021-06-03 13:31:13

Still not fixed on my M4. Should be quick and easy for tp-link to update the dns.

  0  
  0  
#5
Options
Re:Deco M9 plus is querying wrong public NTP server after firmware update
2021-06-04 09:38:57

@magne 

Hi, the incorrect NTP server on the Deco M9 plus, has been fixed by the latest firmware 1.5.x;

As for Deco M4, can I have some pictures of the wrong NTP server request?

Thank you very much.

Deco Monthly Recap- Check What's Currently Going on With Deco
  0  
  0  
#6
Options

Information

Helpful: 1

Views: 1161

Replies: 5

Related Articles
DECO M9 PLUS IS NOT ROAMING
2048 0
Is the Deco M9 Plus V2 EOL?
3747 1
Deco M9 plus - is this AP setup possible?
825 0
USB port on Deco M9 Plus is useless
14524 5
Deco M9 Plus limitations
280 0
Deco M9 Plus V2
497 0
About Us
Press
Copyright © TP-LINK CORPORATION PTE. LTD. All rights reserved.