You set up A records for your web site and MX records for your mail service.
example.com SOA some.soa.admin numbers numbers ....
example.com NS ns1.bdm.microsoftonline.com
example.com NS ns2.bdm.microsoftonline.com
example.com A 192.0.2.5 ; web server IP address
example.com A 192.0.2.6 ; another, the load in general will be split between them
Your domain tamamsouq.com have a DNSSEC related problem, which you can see if you go at http://dnsviz.net/d/tamamsouq.com/dnssec/
This is the first problem to address.
In summary, you put a DS record at the parent zone but your nameservers do not publish any related DNSKEY record.
This will make your domain as failed for any recursive nameserver checking ...
Took a few minutes to work this out - the problem is a typo. The nameservers are ns1.checkerinc.net and ns2.checkersinc.net - however you put dns1.checkersinc.net and dns2.checkersinc.net. While the latter domains exist, they do not appear to be authorative servers.
The solution is to log into your registrar and update the DNS records. to remove the "d" ...