What happens if you run sudo mailinabox?
Nothing happen, it’s expected success output. But when it comes to status checking it stuck.
There are similar issues to yours in the project GitHub that were closed with this PR, which was just merged into main (but isn’t in any release version):
The commit added 2 lines to status_checks.py.
I just experienced the “Something went wrong, sorry.” message for the first time, and it was after clicking ‘Enable New-Version Check’. I then logged in through ssh, ran some system updates, rebooted, logged into the dashboard and everything worked fine. I doubt system updates removed the condition, but maybe either a reboot or being forced to log back in MiaB dashboard did.
You don’t seem to have glue records configured.
yesterday i have made changes of DNS, i replace the old server with new server, is it possible the changes not yet take effect? 
The ns records for you domain do not resolve to an IP address, suggesting the glue records are not configured.
Verify they are configured with your registrar. If they are configured in the registrar interface, try deleting them and then re-creating them.
If that does nothing, contact customer support.
You can check with gwhois.org to see the current status. That site resolves every lookup from root servers, so no caching issues.
I have done some testing. Your glue records are still pointing to your old IP address. @jiaswee1995
I recommend contacting domain.com support and asking for their assistance in updating the glue records.
; <<>> DiG 9.11.3-1ubuntu1.14-Ubuntu <<>> @f.nic.tech aquasoft.tech NS
; (2 servers found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26670
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 3
;; WARNING: recursion requested but not available
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;aquasoft.tech. IN NS
;; AUTHORITY SECTION:
aquasoft.tech. 3600 IN NS ns1.box.aquasoft.tech.
aquasoft.tech. 3600 IN NS ns2.box.aquasoft.tech.
;; ADDITIONAL SECTION:
ns1.box.aquasoft.tech. 3600 IN A 206.189.149.207
ns2.box.aquasoft.tech. 3600 IN A 206.189.149.207
;; Query time: 77 msec
;; SERVER: 212.18.249.60#53(212.18.249.60)
;; WHEN: Sat May 08 18:56:01 CEST 2021
;; MSG SIZE rcvd: 114
What command did you use to get that output?
First you need to find a name server serving the TLD.
dig tech NS
; <<>> DiG 9.11.3-1ubuntu1.14-Ubuntu <<>> tech NS
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 397
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;tech. IN NS
;; ANSWER SECTION:
tech. 172800 IN NS f.nic.tech.
tech. 172800 IN NS g.nic.tech.
tech. 172800 IN NS e.nic.tech.
tech. 172800 IN NS b.nic.tech.
tech. 172800 IN NS a.nic.tech.
;; Query time: 89 msec
;; SERVER: 10.9.0.1#53(10.9.0.1)
;; WHEN: Sat May 08 18:55:39 CEST 2021
;; MSG SIZE rcvd: 117
From that output dig the domain in question.
dig @f.nic.tech aquasoft.tech (pick any of the name servers listed in the previous step)
and that outputs the output I showed above… which I compared with the current IP of box.aquasoft.tech to determine that the information is not the same. The rest is based on assumption per the info the OP provided.
I can see that cloudflare.tech resolves as expected.
I think if the name server record for aquasoft.tech is not available for everyone, then the IP address the glue record points to isn’t going to matter.