• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Soa serial 0 , domain will be switched off off soon

Status
Not open for further replies.

Torsten_Rüger

New Pleskian
Hi,

I have one domain (just one?) that has a serial of 0 (on my server 5.9.57.170 , latest plesk)

Because of that, dns updates don't happen, dns servers don't respond , and my domain issuer is threatening to revoke the domain as it is not working as it should.

> dig auringostaitaan.fi @5.9.57.170 soa +short
robotns3.second-ns.com. torsten\.ruger.gmail.com. 0 10800 3600 604800 10800

You can see the test here http://dnstest.ficora.fi/dnstest.php when you enter the domain auringostaitaan.fi

In trying to fix this i have switched the dns off,changed the mode, enabled RIPE, but i get what it says in the help (http://download1.parallels.com/Ples...inistrator-guide/index.htm?fileName=72042.htm)

Note: See the sample of SOA serial number generated with the selected format. If the resulting number is less, than the current zone number, the modification may cause temporary malfunction of DNS for this domain. Zone updates may be invisible to Internet users for some time.

I am at a loss at how to influence this "little" number with such big effect

Please help

Torsten
 
Hi,
Did you try to update the zone after switching? (Add and then remove some record to increase the serial?)
Run following command:
# plesk db "select * from dns_zone" | grep auringostaitaan.fi
it will show the zone properties from plesk database.
 
What sort of following SQL query:

mysql> select serial_format,serial from dns_zone where name='auringostaitaan.fi';
 
Hi guys, thanks for answering
i guess the two commands do the same (old vs new), plesk db output

| 4 | auringostaitaan.fi | auringostaitaan.fi | 0 | skip | true | [email protected] | master | 86400 | 86400 | 10800 | 3600 | 3600 | 3600 | 604800 | 86400 | 10800 | 3600 | YYYYMMDDNN | 2015042001 | |
| 11 | auringostaitaan.fi | auringostaitaan.fi | 0 | skip | skip | [email protected] | master | 86400 | 86400 | 10800 | 3600 | 3600 | 3600 | 604800 | 86400 | 10800 | 3600 | UNIXTIMESTAMP | 0 | |


There had been some similar problem after the last automatic update (switched those off now)(not relevant: http://talk.plesk.com/threads/plesk-update-destroys-dns-cant-log-in-anymore.331970/)

As far as i remember i switched the zone off and on and that resolved it.

Now it looks like i have two zones, one that has timestamp ok but is not used, and one without that is used.
But how can i switch ?

Thanks

Torsten
 
In 'domains' table check which dns_zone_id is used for your domain auringostaitaan.fi and remove unnecessary record from 'dns_zone' table.
 
Did you change your server hostname to "auringostaitaan.fi" after domain "auringostaitaan.fi" creation?
What does following command return?
# plesk db "select dns_zone_id from domains where name='auringostaitaan.fi'"
 
So, RusianT , yes i did change the server hostname as i had bought ssl for that domain and wanted to use a name to access the server and get rid of the "insecure" warning that comes from using self-signed certs. The command gives
+-------------+
| dns_zone_id |
+-------------+
| 4 |
+-------------+

Which i guess answers IgorG's question. 4 is used , 11 unused. Though 11 is obviously in use as email and serial 0 point to it.

Unfortuantely i don't know how to write sql on the command line beyond slight changes of your examples.
if someone could give me the delete cmd i can issue it
 
So would

plesk db "delete from dns_zone where dns_zone_id=11"

be doing the trick?
But if 11 is used, will the deletion not lead to other problems ?

Thanks

Torsten
 
I ыгппуые нщг recommend to create a request to support team to do in-depth investigation to find the reason of this database inconsistency and to fix it. Please create a ticket to support at https://www.odin.com/support/request/ .
You may have free support, please check what kind of Plesk license you use for available support options at http://kb.odin.com/en/121580 .
If there’s no free support in your case, you can order Plesk per-incident support at http://www.odin.com/support/buy-support/ Support team will contact you as soon as purchase is processed, and they will do the best to resolve it.
 
Well, i did the command and removed the record. Updated the zone and now it works. So i'm good and thank you for your help.

As a developer i do agree that it would be beneficial to find the cause of this malfunction.
But since i am a user of your system and did nothing special, i consider this a bug, and am definitely not willing to pay to get it debugged.

I looked at the support options and am not sure: I have bought my license (30 user on a dedicated machine) from the server supplier. They don't support plesk and it is unclear to me if i now have a "Plesk Web Host Edition" or what.

So if you want a developer to look into this i will help him, but otherwise this is closed for me.
 
Hi
I can reproduce the issue when server hostname zone id is more than domain with same name zone id (PPPM-2755).
But this case (hostname zone id > 1) is really unexpected, was there some specific with this server (manual psa database restore, or migration/restore from old dumps, etc)?
 
Status
Not open for further replies.
Back
Top