Eboy aqui tiene los datos...
El Dominio A probando dnsreport me dice:
WARN All nameservers report identical NS records WARNING: At least one of your nameservers did not return your NS records (it reported 0 answers). This could be because of a referral, if you have a lame nameserver (which would need to be fixed).
216.120.225.19 returns 0 answers (may be a referral)
216.120.238.254 returns 0 answers (may be a referral)
----
FAIL Lame nameservers ERROR: You have one or more lame nameservers. These are nameservers that do NOT answer authoritatively for your domain. This is bad; for example, these nameservers may never get updated. The following nameservers are lame:
216.120.225.19
216.120.238.254
---
FAIL Missing nameservers 2 ERROR: One or more of the nameservers listed at the parent servers are not listed as NS records at your nameservers. The problem NS records are:
dns1.hrnoc.net.
dns2.hrnoc.net.
---
FAIL NS agreement on SOA Serial # ERROR: Your nameservers disagree as to which version of your DNS is the latest! 4294967295 versus 0! This is OK if you have just made a change recently, and your secondary DNS servers haven't yet received the new information from the master. I will continue the report, assuming that 0 is the correct serial #.
----
FAIL SOA MNAME Check ERROR: Your SOA (Start of Authority) record states that your master (primary) name server is: . However, that is not a valid domain name!
---
FAIL SOA RNAME Check ERROR: Your SOA (Start of Authority) record states that your DNS contact E-mail address in hostname format is: . However, that is NOT valid (it must have at least 2 '.''s in it and no '@')!
---
WARN SOA Serial Number WARNING: Your SOA serial number is: 0. That is OK, but the recommended format (per RFC1912 2.2) is YYYYMMDDnn, where 'nn' is the revision. For example, if you are making the 3rd change on 02 May 2000, you would use 2000050203. This number must be incremented every time you make a DNS change.
FAIL SOA REFRESH value WARNING: Your SOA REFRESH interval is : 0 seconds. This seems very low. You should consider increasing this value to about 3600-7200 seconds. RFC1912 2.2 recommends a value between 1200 to 43200 seconds (20 minutes to 12 hours). A value that is too low will unncessarily increase Internet traffic.
---
FAIL SOA RETRY value WARNING: Your SOA RETRY interval is : 0 seconds. This seems very low. You should consider increasing this value to about 120-7200 seconds. The retry value is the amount of time your secondary/slave nameservers will wait to contact the master nameserver again if the last attempt failed.
---
FAIL SOA EXPIRE value WARNING: Your SOA EXPIRE time is : 0 seconds. This seems very low. You should consider increasing this value to about 1209600 to 2419200 seconds (2 to 4 weeks). RFC1912 recommends 2-4 weeks. This is how long a secondary/slave nameserver will wait before considering its DNS data stale if it can't reach the primary nameserver.
---
FAIL SOA MINIMUM TTL value WARNING: Your SOA MINIMUM TTL is : 0 seconds. This seems very low (unless you are just about to update your DNS). You should consider increasing this value to somewhere between 3600 and 10800. RFC2308 suggests a value of 1-3 hours. This value used to determine the default (technically, minimum) TTL (time-to-live) for DNS entries, but now is used for negative caching.
---
MX FAIL MX Category ERROR: I couldn't find any MX records for alogadesign.com. If you want to receive E-mail on this domain, you should have MX record(s). Without any MX records, mailservers should attempt to deliver mail to the A record for dominioA.com. I can't continue in a case like this, so I'm assuming you don't receive mail on this domain.
---
Mail FAIL Connect to mail servers ERROR: I could not find any mailservers for dominioA.com.
---
WWW FAIL WWW Category ERROR: I couldn't find any A records for
www.dominioA.com. If you want a website at
www.dominioA.com, you will need an A record for
www.dominioA.com If you do not want a website at
www.dominioA.com, you can ignore this error.
Y en el otro, Dominio B: me sale los errores y fallos exactamentes iguales.
¿Por qué se produce estos fallos? ¿Cómo se puede solucionar?
Gracias.
¿ Problemas DNS ? 
