I have set up an ISPConfig server to host email for several domains and I am having a problem with mail sent from this server not being delivered to some, but not all, valid domains.

When mail is rejected, it contains an error message similar to the following:

: Host or domain name not found for name=comcast.net Type=A: Host found but no data record of requested type

I thought that my domain may have gotten blacklisted, but I didn't find any listings when checked the domain against several BLs.

AFAIK, Type A records are IPv4 addresses and should always exist if a DNS record exists.

I'm at a loss.

Can anyone shed some light on what this message is telling me?

closed as off-topic by HopelessN00b Apr 3 '15 at 13:34

  • This question does not appear to be about server, networking, or related infrastructure administration within the scope defined in the help center.
If this question can be reworded to fit the rules in the help center, please edit the question.


There are A (and MX, too) records for comcast.net. Therefore, I strongly suspect a DNS issue. You should debug your DNS resolver first. For instance, what do dig A comcast.net or dig MX comcast.net yield?

If the problem is temporary, then you'll have to perform the dig when the problem occurs.

And, no, it is perfectly legal to not have A records.


Some of the bigger ISP's will look for a PTR record...they will not allow email..

further they will have a second line of spam filters that will check for an A record. It might be legal to not have an A record, but is a good idea too have an A record for the relay.

On my brightmail servers I have made the decision to not accept mail if an A record is not found. I have not had any reports from the business that they are not able to transact email for any reason.

Verizon and Comcast have the tightest rules that I have found.

I also use optus looking glass (that is my google term I search for) to check to see what I look like DNS wise from the outside world.

Lastly...you might get past some very tight servers if you use a proper SPF record.

  • Although the OP did not provide many details, it seems the error message was locally generated and therefore has nothing to do with Comcast's rules or checks. – bortzmeyer May 18 '09 at 6:43
  • What does your DNS setup look like? and who are you using for your outside DNS servers? – Thomas Denton May 18 '09 at 11:12

I am not sure if it is related to the specific error you are having, but I had a similar issue with Postfix and Comcast related to Reverse DNS lookup.

Ensure your domains are set up for reverse lookup, and give it another shot.

  • Absolutely no connection with the error message he got. – bortzmeyer May 15 '09 at 20:31

You're trying to resolve an address as a domain. While you can do that, there is no guarantee that you'll get what you're after. What you really want is for your MTA to pick up the MX record for comcast.net, and not just resolve to comcast.net.

Also, it sounds like you're attempting delivery to the MTA at a server named "comcast.net", but I suspect you really want to attempt delivery to smtp.comcast.net instead. I'm sure you'll have a bit more luck with that address.

Not the answer you're looking for? Browse other questions tagged or ask your own question.