Crea una cuenta en la Comunidad HP para personalizar tu perfil y realizar una pregunta
el 06-02-2020 10:39 AM
Estoy teniendo un problema con el envío por correo electrónico impresiones a mi impresora. Consultado mi soporte de Correo, el problema que me reportan es que el servidor MX de HPeprint no cumple con los estándares de correo.
Según intoDNS.com, el problema proviene de:
Category Status Test name Informationsend feedback Parent
Domain NS records Nameserver records returned by the parent servers are:
ns1.hp.com. ['188.8.131.52'] [TTL=172800]
ns2.hp.com. ['184.108.40.206'] [TTL=172800]
ns3.hp.com. ['220.127.116.11'] [TTL=172800]
ns4.hp.com. ['18.104.22.168'] [TTL=172800]
ns5.hp.com. ['22.214.171.124'] [TTL=172800]
ns6.hp.com. ['126.96.36.199'] [TTL=172800]
j.gtld-servers.net was kind enough to give us that information.
TLD Parent Check Good. j.gtld-servers.net, the parent server I interrogated, has information for your TLD. This is a good thing as there are some other domain extensions like "co.us" for example that are missing a direct check.
Your nameservers are listed Good. The parent server j.gtld-servers.net has your nameservers listed. This is a must if you want to be found as anyone that does not know your DNS servers will first ask the parent nameservers.
DNS Parent sent Glue Good. The parent nameserver sent GLUE, meaning he sent your nameservers as well as the IPs of your nameservers. Glue records are A records that are associated with NS records to provide "bootstrapping" information to the nameserver.(see RFC 1912 section 2.3)
Nameservers A records Good. Every nameserver listed has A records. This is a must if you want to be found. NS
NS records from your nameservers NS records got from your nameservers listed at the parent NS are:
ns3.hp.com ['188.8.131.52'] [TTL=3600]
ns6.hp.com ['184.108.40.206'] [TTL=3600]
ns4.hp.com ['220.127.116.11'] [TTL=3600]
ns2.hp.com ['18.104.22.168'] [TTL=3600]
ns1.hp.com ['22.214.171.124'] [TTL=3600]
ns5.hp.com ['126.96.36.199'] [TTL=3600]
Recursive Queries Good. Your nameservers (the ones reported by the parent server) do not report that they allow recursive queries for anyone.
Same Glue The A records (the GLUE) got from the parent zone check are the same as the ones got from your nameservers. You have to make sure your parent server has the same NS records for your zone as you do according to the RFC. This tests only nameservers that are common at the parent and at your nameservers. If there are any missing or stealth nameservers you should see them below!
Glue for NS records INFO: GLUE was not sent when I asked your nameservers for your NS records.This is ok but you should know that in this case an extra A record lookup is required in order to get the IPs of your NS records. The nameservers without glue are:
You can fix this for example by adding A records to your nameservers for the zones listed above.
Mismatched NS records OK. The NS records at all your nameservers are identical.
DNS servers responded Good. All nameservers listed at the parent server responded.
Name of nameservers are valid OK. All of the NS records that your nameservers report seem valid.
Multiple Nameservers Good. You have multiple nameservers. According to RFC2182 section 5 you must have at least 3 nameservers, and no more than 7. Having 2 nameservers is also ok by me.
Nameservers are lame OK. All the nameservers listed at the parent servers answer authoritatively for your domain.
Missing nameservers reported by parent OK. All NS records are the same at the parent and at your nameservers.
Missing nameservers reported by your nameservers OK. All nameservers returned by the parent server j.gtld-servers.net are the same as the ones reported by your nameservers.
Domain CNAMEs OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
NSs CNAME check OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
Different subnets OK. Looks like you have nameservers on different subnets!
IPs of nameservers are public Ok. Looks like the IP addresses of your nameservers are public. This is a good thing because it will prevent DNS delays and other problems like
DNS servers allow TCP connection OK. Seems all your DNS servers allow TCP connections. This is a good thing and useful even if UDP connections are used by default.
Different autonomous systems OK. It seems you are safe from a single point of failure. You must be careful about this and try to have nameservers on different locations as it can prevent a lot of problems if one nameserver goes down.
Stealth NS records sent Ok. No stealth ns records are sent SOA
SOA record The SOA record is:
Primary nameserver: cce02hpiibpe.ams.hp.net
Hostmaster E-mail address: hostmaster.hp.com
Serial #: 443241618
Expire: 2419200 4 weeks
Default TTL: 900
NSs have same SOA serial OK. All your nameservers agree that your SOA serial number is 443241618.
SOA MNAME entry WARNING: SOA MNAME (cce02hpiibpe.ams.hp.net) is not listed as a primary nameserver at your parent nameserver!
SOA Serial Your SOA serial number is: 443241618. The recommended format (per RFC1912 2.2) is YYYYMMDDnn, where 'nn' is the revision.
Your SOA serial appears to be the number of seconds since midnight 01 Jan 1970 when the last DNS change was made. That seems to be 1984/1/17 20:40:18
SOA REFRESH OK. Your SOA REFRESH interval is: 3600. That is OK
SOA RETRY Your SOA RETRY value is: 3600. Looks ok
SOA EXPIRE Your SOA EXPIRE number is: 2419200.Looks ok
SOA MINIMUM TTL Your SOA MINIMUM TTL is: 900. This value was used to serve as a default TTL for records without a given TTL value and now is used for negative caching (indicates how long a resolver may cache the negative answer). RFC2308 recommends a value of 1-3 hours. Your value of 900 is OK. MX
MX Records Your MX records that were reported by your nameservers are:
10 emailinbound-ext-prod.inc.hp.com -> CNAME(s) -> 188.8.131.52 (no glue)
[These are all the MX records that I found. If there are some non common MX records at your nameservers you should see them below. ]
Different MX records at nameservers Good. Looks like all your nameservers have the same set of MX records. This tests to see if there are any MX records not reported by all your nameservers and also MX records that have the same hostname but different IPs
MX name validity Good. I did not detect any invalid hostnames for your MX records.
MX IPs are public OK. All of your MX records appear to use public IPs.
MX CNAME Check WARNING: CNAME was returned for the following MX records:
The CNAME(s) that were returned are listed above. This is not ok per the RFCs and can cause problems including mail being lost!
MX A request returns CNAME WARNING: MX records points to a CNAME. CNAMEs are not allowed in MX records, according to RFC974, RFC1034 3.6.2, RFC1912 2.4, and RFC2181 10.3. The problem MX record(s) are:
emailinbound-ext-prod.inc.hp.com points to ['eprint-emailinbound.glbinc.hp.com']
This can cause problems
MX is not IP OK. All of your MX records are host names.
Number of MX records OK. Looks like you only have one MX record at your nameservers. You should be careful about what you are doing since you have a single point of failure that can lead to mail being lost if the server is down for a long time.
Mismatched MX A OK. I did not detect differing IPs for your MX records.
Duplicate MX A records OK. I have not found duplicate IP(s) for your MX records. This is a good thing.
Reverse MX A records (PTR) Your reverse (PTR) record:
184.108.40.206.in-addr.arpa -> g7t00365g.inc.hp.com
You have reverse (PTR) records for all your IPs, that is a good thing.
¿Alguien tiene idea de como solucionarlo?
el 06-02-2020 05:59 PM
Esa pagina no da la información correcta , esas son sugerencias.
Consulte en mxtoolbox y vera que esta funcionando correctamente oos Mx.
Mi ayuda es voluntaria
- Si lo ayude a solucionar su consulta o problema por favor haga clic sobre ACEPTAR COMO SOLUCION en el mensaje que aporto la solución
- Puede dar las gracias por mi aporte haciendo clic sobre