# Technical check problems # M-TO -E- [DOMAIN] TIMOUT, EXITING… #### THE PROBLEM EXPLANATION: This means that you can not download the zone from the name servers. #### SOLUTION OF THIS PROBLEM: Please try again later or write to your service provider. # M-SOF -E- [domain] A record for soa mail host soa_mail_host not found #### THE PROBLEM EXPLANATION: This means that no email server exists for the e-mail address provided in the SOA record. #### SOLUTION OF THIS PROBLEM: Fix the RNAME field or the record that belongs to the mail domain. # M-SOAM -E- [domain] SOA mail address check failed #### THE PROBLEM EXPLANATION: This means that the email address in the SOA record does not exist. #### SOLUTION OF THIS PROBLEM: Fix the email address or configure the mail server to make sure that the email address can receive mail. # M-SOAER -E- [domain] syntax error in SOA record #### THE PROBLEM EXPLANATION: This means that the SOA record is incorrect. #### SOLUTION OF THIS PROBLEM: According to [RFC1035](http://www.ietf.org/rfc/rfc1035.txt "RFC1035"), we need to improve the record. # M-PRIF -E- [domain] Cannot get domain data (nshost_a nshost) #### THE PROBLEM EXPLANATION: This means that you can not download the SOA record from the name server provided. #### SOLUTION OF THIS PROBLEM: Enter the name server or fix the configuration. In case you want to use the domain name on your cPanel hosting account, first add the domain name to your cPanel account as a Addon domain or Alias. # M-PNAU6 -E- [domain] NS at AAAA not responding, not authoritative, or wrong serial: ns #### THE PROBLEM EXPLANATION: The cause of the error is related to the IPv6 AAAA record. The zone file contains a NS record with an AAAA record, but the specified IPv6 address does not provide the same SOA record for the domain. #### SOLUTION OF THIS PROBLEM: Also configure the name server at IPv6 address. # M-PNAU -E- [domain] NS not authoritative: ns #### THE PROBLEM EXPLANATION: This means that the domain is not configured in the destination name server. #### SOLUTION OF THIS PROBLEM: In the specified name server, set the domain name correctly. # M-PMAS -E- [domain] address check for postmaster@domain failed at ALL MX records #### THE PROBLEM EXPLANATION: This means that the specified mail server (s) does not have the postmaster@domain\_name email address. #### SOLUTION OF THIS PROBLEM: By properly configuring the mail server, make sure that the email address can receive mail, or remove the MX record from the domain name zone file during the nameserver change. # M-NSF -E- [domain] A record for NS … not found #### THE PROBLEM EXPLANATION: This means there is no A record found on the named name server. #### SOLUTION OF THIS PROBLEM: Set A record. # M-NOMX -E- [domain] no MX record (nor A record) for domain #### THE PROBLEM EXPLANATION: This means that the domain does not have MX or A record. #### SOLUTION OF THIS PROBLEM: Pick up the correct A or MX record and set up the mail server properly. # M-NOSE -E- [domain] No secondary #### THE PROBLEM EXPLANATION: There is no secondary name server for the domain name. #### SOLUTION OF THIS PROBLEM: Let’s have at least one more authoritative name server. # M-NNAS -E- [domain] Cannot get A for NS host nshost #### THE PROBLEM EXPLANATION: This means that the secondary name server does not have a set A record. #### SOLUTION OF THIS PROBLEM: For the name server, set A record. # M-NMAS -E- [domain] Cannot get A for NS host pserv #### THE PROBLEM EXPLANATION: This means that the primary name server is not set to A record. #### SOLUTION OF THIS PROBLEM: Set A record server for the name server. # M-MXF -E- [domain] canonical A record for MX mx not found #### THE EXPLANATION OF THIS PROBLEM: This means the MX record not belong IP address #### SOLUTION OF THIS PROBLEM: To set the MX record, set the A record IP address.
# M-LASE -E- [domain] Lame secondary #### THE PROBLEM EXPLANATION: This means the secondary nameserver can’t server the domain name zone. #### SOLUTION OF THIS PROBLEM: Make sure the specified server serve the domain name zone: it may not work on a name server at the specified location or it works, but it does not provide a zone or works, but some firewall prevents it from accessing it. # M-DSOA -E- [domain] SOA records differ on servers #### THE PROBLEM EXPLANATION: This means the nameservers not synchronized currently. #### SOLUTION OF THIS PROBLEM: If the different cause the secondary name server don’t download the zone, then fix the configuration. A couple of possible point: - firewall rules - allow-transfer option - Setup the correctt IP address If the excursion causes the refresh late, ask the provider to synchronize the zone manually. # M-DIFN -E- [domain] All nameservers on the same network #### THE PROBLEM EXPLANATION: This means that the name servers provided by your service provider are located in the same network ranges. The verification procedure can not determine this with complete certainty, but it is true if: 1. Two name servers are indifferent /24 address ranges or if 2. The traceroute leading to name servers are different. #### SOLUTION OF THIS PROBLEM: The domain name is set up in name servers that are located on a separate network. It is common that two or more organizations mutually subscribe to each other for a secondary name server. # M-CNAM -E- [domain] NS record CNAME #### THE PROBLEM EXPLANATION: This is mean the nameserver record is a CNAME record not that an A record. #### SOLUTION OF THIS PROBLEM: Use the A record instead of the CNAME record to the nameserver. # M-NOGV -E- [domain] primary on command line pserv and in zone don't match ### THE PROBLEM EXPLANATION: This means that the name server in the SOA record doesn't match the primary name server. ### SOLUTION OF THIS PROBLEM: Fix the SOA record or introduce a proper NS record. ### In the case of foreign name server service provider, we can send the following form letter to the service provider: Write the domain name in place of underscore. ``` ATTN: Administrators Dear Madam/Sir,

The .hu TLD registry has special requirements for domains before nameservers can be changed. The primary nameserver for the domain ______ provided by you does not match the MNAME field in the SOA record in your nameservers, therefore the registry refuses to change nameservers.

You may verify the settings using this site: http://www.domain.hu/domain/English/regcheck/

Thank you for your time ```