Cannot update Expire value for a SOA record: SOA Serial Number Format is Invalid

Created:

2017-06-30 18:31:16 UTC

Modified:

2017-08-16 15:47:42 UTC

0

Was this article helpful?


Have more questions?

Submit a request

Cannot update Expire value for a SOA record: SOA Serial Number Format is Invalid

Applicable to:

  • Plesk for Linux

Symptoms

After updating Expire parameter at Plesk > Subscriptions > example.com > Websites & domains > DNS Settings > SOA Record , the updates are not applied. Old value is returned to external clients:

[root@jumper ~]# dig +short SOA example.com
ns1.example.com. 2017063002 10800 3600 604800 10800

DNS check at mxtoolbox.com shows a warning:

SOA Serial Number Format is Invalid 
ns1.example.com reported Serial 1498686726 : Suggested serial format year was 1498 which is before 1970. More Info
SOA Expire Value out of recommended range 
ns1.example.com reported Expire 604800 : Expire is recommended to be between 1209600 and 2419200.

A DNS request to authoritative server from an external location does not work via UDP. It works via UDP and shows the updated value:

[root@jumper ~]# dig +short @203.0.113.2 SOA example.com
;; connection timed out; no servers could be reached

[root@jumper ~]# dig +short +tcp @203.0.113.2 SOA example.com
ns1.example.com. 2017063006 10800 3600 1296000 10800

Traceroute via UDP from external location shows the following:

[root@jumper ~]# traceroute -U -p 53 203.0.113.2
traceroute to 203.0.113.2 (203.0.113.2), 30 hops max, 60 byte packets
1 gw4.externalexample.com (10.33.23.1) 0.284 ms 0.259 ms 0.250 ms
2 ae15.externalexample2.com (203.0.114.2) 176.647 ms 179.655 ms 179.876 ms
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *

Cause

Traffic to UDP port 53 is filtered by intermediary hosts.

Resolution

Contact network administrator or ISP to allow traffic to UDP port 53.

Have more questions? Submit a request
Please sign in to leave a comment.