Mail SMTP Relay - Reverse DNS Question
-
Then the error you are getting is from messages going from Artica to your mail server correct?
-
Honestly at this point I'm a little confused since my mail server did fail last night and Artica 100% did its job.
I guess my real underlying question is getting reverse DNS up and going. If I'm contact who my name server is with or where my virtual is hosted.
And do I simply say "Hey I need a "PTR" record for mail-store1.domain.ca
-
@Sparkum Are you using Artica for outbound proxy aswell? If so, it would be best to change it. If your mail server is sending directly out you can keep it at mail.domain.ca
-
@brianlittlejohn
Outbound is Mandrill -
@Sparkum You should be good then.
-
@Sparkum said:
@scottalanmiller
Oh really?So I need to contact where the virtual is hosted not where the nameserver is hosted?
Yes, if they are the ones that interface with the ISP or are the ISP. They would be the ones. Often if you have something like AWS, Rackspace, etc. they have an interface for this.
-
@scottalanmiller said:
I might not have followed this correctly but... PTR (Reverse DNS) records have to be done at the IP Address point, not with your DNS provider. Whoever does your A and MX records can't be the company with the PTR record. Your ISP has to do the PTR record. The ISP at which your MX record points.
Incorrect. It can be the same one, but someone has to have delegation to perform it.
https://www.arin.net/resources/request/reversedns.html
https://www.apnic.net/services/services-apnic-provides/registration-services/reverse-dns
https://www.ripe.net/manage-ips-and-asns/db/support/configuring-reverse-dns
http://www.lacnic.net/en/web/lacnic/guia-de-sistema-04
https://www.afrinic.net/library/corporate-documents/216-how-to-request-reverse-delegation-in-afrinic-regionAnd for the most part, most ISPs, especially home ISPs, do not delegate out permissions.
-
@scottalanmiller said:
I might not have followed this correctly but... PTR (Reverse DNS) records have to be done at the IP Address point, not with your DNS provider. Whoever does your A and MX records can't be the company with the PTR record. Your ISP has to do the PTR record. The ISP at which your MX record points.
You're assuming that @Sparkum is using a different DNS provider than his ISP. If he is using the ISP to provide DNS for his setup, he's already calling the right people.
And from reading the response he received from the ISP, I'd guess they are one in the same.
Also, as for your Reverse DNS issue, can you have more than one PTR record on an IP? If you can great, but if not, you'll be forced to get a second IP address for the Artica.
-
@Dashrender said:
You're assuming that @Sparkum is using a different DNS provider than his ISP. If he is using the ISP to provide DNS for his setup, he's already calling the right people.
Assuming that his DNS provider is not his VM hoster, that is correct.
-
@Dashrender said:
Also, as for your Reverse DNS issue, can you have more than one PTR record on an IP? If you can great, but if not, you'll be forced to get a second IP address for the Artica.
If you had more than one PTR to an IP it would return results in round robin. Under what scenario would you want that to happen?
-
@scottalanmiller said:
@Dashrender said:
Also, as for your Reverse DNS issue, can you have more than one PTR record on an IP? If you can great, but if not, you'll be forced to get a second IP address for the Artica.
If you had more than one PTR to an IP it would return results in round robin. Under what scenario would you want that to happen?
I don't think you would - so because the OP wants to different domains here mail.domain.ca and mail-store1.domain.ca, he will be required to get a second IP to get what he wants - right?
-
@Dashrender said:
@scottalanmiller said:
@Dashrender said:
Also, as for your Reverse DNS issue, can you have more than one PTR record on an IP? If you can great, but if not, you'll be forced to get a second IP address for the Artica.
If you had more than one PTR to an IP it would return results in round robin. Under what scenario would you want that to happen?
I don't think you would - so because the OP wants to different domains here mail.domain.ca and mail-store1.domain.ca, he will be required to get a second IP to get what he wants - right?
Yes, because when you do a PTR lookup, it would not know which one to return so you'd either have to pick one or have it return at random. Not sure which is worse
-
I easily missed something in the description, but why does he want to have two different domains at that IP address?
-
@scottalanmiller said:
I easily missed something in the description, but why does he want to have two different domains at that IP address?
Because he only has one IP from his host provider.
-
From what I gather, the OP has a VM server running hosted in a DC. That VM server is running both his email server and his Artica server. Both of those are behind his firewall sharing the same outgoing IP.
-
@Dashrender said:
@scottalanmiller said:
I easily missed something in the description, but why does he want to have two different domains at that IP address?
Because he only has one IP from his host provider.
Well that explains why he only has one IP. But the question was why he wants it to identify as two different domains in a PTR record.
-
@Dashrender said:
From what I gather, the OP has a VM server running hosted in a DC. That VM server is running both his email server and his Artica server. Both of those are behind his firewall sharing the same outgoing IP.
And both of those solutions require a unique PTR record? Why?
-
@scottalanmiller said:
@Dashrender said:
@scottalanmiller said:
I easily missed something in the description, but why does he want to have two different domains at that IP address?
Because he only has one IP from his host provider.
Well that explains why he only has one IP. But the question was why he wants it to identify as two different domains in a PTR record.
Because he wants a backup host to accept his email when his email server is offline.
of course, this only works assuming the ISP/DC/VM host are all still running. Once any of those die, the whole box is down, and your email appears down from the outside.
Oh.. and this is a learning thing.. not really production - stated in OP.
-
@Dashrender said:
Because he wants a backup host to accept his email when his email server is offline.
I continue to not understand. How does this relate to the issue at hand? PTRs have nothing to do with receiving emails.
-
PTRs are used to reduce other people seeing you as a spammer. So your PTR record needs to be set. You only need it for sending email. MX records are for receiving email.
Emails coming to this IP address have already arrived once they hit the outside and the PTR record, and DNS altogether, is already past the point of being used. Receiving emails are unaffected by any PTR settings anywhere.
