Post by nibiruet on Sept 3, 2007 2:38:46 GMT -5
Have these error reports at DNSstuff.com when checking my domain hosted at AwardSpace. Any idea how to fix them? Color blue is actually yellow at their site but I am using blue here for better visibility.
WARN Glue at parent nameservers WARNING. The parent servers (I checked with b.gtld.biz.) are not providing glue for all your nameservers. This means that they are supplying the NS records (host.example.com), but not supplying the A records (192.0.2.53), which can cause slightly slower connections, and may cause incompatibilities with some non-RFC-compliant programs. This is perfectly acceptable behavior per the RFCs. This will usually occur if your DNS servers are not in the same TLD as your domain (for example, a DNS server of "ns1.example.org" for the domain "example.com"). In this case, you can speed up the connections slightly by having NS records that are in the same TLD as your domain.
WARN Nameservers on separate cl[censored]C's WARNING: We cannot test to see if your nameservers are all on the same Cl[censored]C (technically, /24) range, because the root servers are not sending glue. We plan to add such a test later, but today you will have to manually check to make sure that they are on separate Cl[censored]C ranges. Your nameservers should be at geographically dispersed locations. You should not have all of your nameservers at the same location. RFC2182 3.1 goes into more detail about secondary nameserver location.
FAIL Reverse DNS entries for MX records ERROR: The IP of one or more of your mail server(s) have no reverse DNS (PTR) entries/* (if you see "Timeout" below, it may mean that your DNS servers did not respond fast enough)*/. RFC1912 2.1 says you should have a reverse DNS for all your mail servers. It is strongly urged that you have them, as many mailservers will not accept mail from mailservers with no reverse DNS entry. You can double-check using the 'Reverse DNS Lookup' tool at the DNSstuff site if you recently changed your reverse DNS entry (it contacts your servers in real time; the reverse DNS lookups in the DNS report use our local caching DNS server). The problem MX records are:
52.131.197.82.in-addr.arpa [No reverse DNS entry (rcode: 3 ancount: 0) (check it)]
FAIL Acceptance of postmaster address ERROR: One or more of your mailservers does not accept mail to postmaster@mydomain.us. Mailservers are required (RFC822 6.3, RFC1123 5.2.7, and RFC2821 4.5.1) to accept mail to postmaster.
mail.bbenson.us's postmaster response:<br /> >>> RCPT TO:<postmaster@mydomain.us><br /> <<< 550 <postmaster@mydomain.us>: Recipient address rejected: User unknown in virtual mailbox table <br />
WARN Glue at parent nameservers WARNING. The parent servers (I checked with b.gtld.biz.) are not providing glue for all your nameservers. This means that they are supplying the NS records (host.example.com), but not supplying the A records (192.0.2.53), which can cause slightly slower connections, and may cause incompatibilities with some non-RFC-compliant programs. This is perfectly acceptable behavior per the RFCs. This will usually occur if your DNS servers are not in the same TLD as your domain (for example, a DNS server of "ns1.example.org" for the domain "example.com"). In this case, you can speed up the connections slightly by having NS records that are in the same TLD as your domain.
WARN Nameservers on separate cl[censored]C's WARNING: We cannot test to see if your nameservers are all on the same Cl[censored]C (technically, /24) range, because the root servers are not sending glue. We plan to add such a test later, but today you will have to manually check to make sure that they are on separate Cl[censored]C ranges. Your nameservers should be at geographically dispersed locations. You should not have all of your nameservers at the same location. RFC2182 3.1 goes into more detail about secondary nameserver location.
FAIL Reverse DNS entries for MX records ERROR: The IP of one or more of your mail server(s) have no reverse DNS (PTR) entries/* (if you see "Timeout" below, it may mean that your DNS servers did not respond fast enough)*/. RFC1912 2.1 says you should have a reverse DNS for all your mail servers. It is strongly urged that you have them, as many mailservers will not accept mail from mailservers with no reverse DNS entry. You can double-check using the 'Reverse DNS Lookup' tool at the DNSstuff site if you recently changed your reverse DNS entry (it contacts your servers in real time; the reverse DNS lookups in the DNS report use our local caching DNS server). The problem MX records are:
52.131.197.82.in-addr.arpa [No reverse DNS entry (rcode: 3 ancount: 0) (check it)]
FAIL Acceptance of postmaster address ERROR: One or more of your mailservers does not accept mail to postmaster@mydomain.us. Mailservers are required (RFC822 6.3, RFC1123 5.2.7, and RFC2821 4.5.1) to accept mail to postmaster.
mail.bbenson.us's postmaster response:<br /> >>> RCPT TO:<postmaster@mydomain.us><br /> <<< 550 <postmaster@mydomain.us>: Recipient address rejected: User unknown in virtual mailbox table <br />
