Nope. You’re not in control of the SOA record directly.
To be fair, those are warnings.

Aside from what mxtoolbox apparently say, do you have any problems with the current SOA values?

First of all, there is absolutely nothing wrong with the SOA Serial. Yes, YYYYMMDDnn might a commonly recommended format, but the only real requirement is that it is a “unsigned 32 bit version number”, which “wraps and should be compared using sequence space”, to quote RFC 1035. Here you appear to have a serial based on unix time, which is not an uncommon option either.

And for the SOA Expire value, that is definitely something there are different opinions about. Still 604800 seconds are still a week, which ought to be plenty of times for presumably well maintained DNS servers like the ones DigitalOcean provide.

it does not actually “cause” any issues, but it does cause errors/warnings for automated tasks that sys admins have setup. I’ve had to change a few of my sync scripts to process past SOA format error.

If you absolutely do need to have the SOA follow that format, you could install bind on your server, and manually modify your zone file (I wish the digitalocean interface had this option).

Hey guys, sorry but the DO notifications went into the promotions bin in gmail. I’m not having any problems at all. I just noticed that when I was checking some other things.

So far DO is awesome!