Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've installed ISPConfig 3 on my VPS using the brilliant tutorial here:

However, if I go to send an email to an account I've set up on the server I get the following error:

Delivery to the following recipient failed permanently:

Technical details of permanent failure: DNS Error: DNS server returned answer with no data

I've checked my DNS records for that domain, and they are as follows:

setanta A       80.xx.xx.xx   MX  10  80.xx.xx.xx
ftp A       80.xx.xx.xx
mail    A       80.xx.xx.xx
dail    A       80.xx.xx.xx
www A       80.xx.xx.xx
.   A       80.xx.xx.xx

I've also tried to send an email from squirrelmail. I've had no errors come back but I've not had the e-mail come through either.

I'm not sure what's going on, as I thought adding as an MX record would work, but I don't think it has. What do I need to do to make it work?


I've changed the MX record so points to However, e-mails still can't be delivered to the account due to the same error.

Also, the DNS server is handled by 6sync, not ISPConfig 3.

share|improve this question

closed as off-topic by HopelessN00b Mar 8 '15 at 21:02

  • 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.

up vote 1 down vote accepted

@D_Bye is correct; you want to specify the MX record for not for A fully qualified domain name in a zone needs a dot after it. Also, MX records must point to domain names, not IP addresses, so:  IN  MX  10


Just noticed that you're missing IN in each line:

setanta IN A       80.xx.xx.xx IN MX  10  80.xx.xx.xx IN NS IN NS IN NS  
ftp IN A       80.xx.xx.xx
mail IN A       80.xx.xx.xx
dail IN A       80.xx.xx.xx
www IN A       80.xx.xx.xx IN   A       80.xx.xx.xx


It's now just occurred to me that you pasted the output of a GUI you're using to edit the DNS record, not the record itself (because there are other parts missing). If this is the case, then setting the MX for to should solve your problem.

share|improve this answer
Still no joy unfortunately! – mickburkejnr Mar 15 '12 at 18:13
Using dig MX I see no MX records. Either it's still not right, or it may take a little longer to propagate. Are you able to edit the zone file directly or are you using a GUI? A paste of the whole zone file, or a screenshot of the GUI would be helpful. – xofer Mar 15 '12 at 19:11

I think you need to remove the from the MX entry - with it there, you tell the DNS how to handle mail for <user>, instead of <user>

share|improve this answer
I've changed it from to, and changed the destination to go to Or should I just leave it as the IP? – mickburkejnr Mar 15 '12 at 14:25
See nobody's answer - try the format suggested there. It's been a while since I edited a zone file, so my knowledge of the syntax is evidently a little rusty! – D_Bye Mar 15 '12 at 14:33
Assuming you're using the ISPConfig GUI, and that it handles the important details (trailing dots, IN, etc.) you should be done -- setting the destination to a domain name is correct. – xofer Mar 15 '12 at 14:46
I'm not using ISPConfig for DNS, I'm using's servers – mickburkejnr Mar 15 '12 at 15:29

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