hardsoftMemberJune 15, 2017 at 1:09 pm #167066
I have an internal email server that is hosted locally using a public ip from my isp. i have noticed that i can sen email to yahoo but email send to gmail and others are not been received. emails sent from my server are been received on yahoo mail servers. however emails cannot be sent yahoo to my private email servers. i looked at logs of the delivery failure notification and i have seen that ” google do not accept emails from by my ip 184.108.40.206 because it does not have a PTR record or a reversed lookup for my domain mydomain.com.
i need tech to help resolved this issue.
Thanks/June 15, 2017 at 1:13 pm #191698
Create a PTR (or rDNS) record on your public DNS server pointing your IP to your email domainJune 15, 2017 at 1:30 pm #391609
is this to be done by my ISP or by me. i dont have a public dns server. i used the isp dns ip address on my server for internet connectionJune 15, 2017 at 1:54 pm #191700
You have a domain – someone manages the DNS records for that domainJune 15, 2017 at 10:19 pm #391610
my domain is hosted on digital ozone that is my website and domain. my dns is provide by my ISP. now is it my ISP who should point my DNS to this domain host. I have configured on my email server smtp.myisp.com. now if my ISP and my domain are not the same network that is my confusion.June 16, 2017 at 12:45 am #191703
I’m really confused now. Do you have a public domain (e.g. petri.com)? Presumably (if you do) this is the one Digital Ozone host. Someone (probably them) will have a DNS server where there are the public records.
Suggest you discuss this with the web hosting provider and your ISP – someone will have the appropriate knowledgeJune 16, 2017 at 3:45 am #391612
yes we do have a public domain that is been hosted by digital ozone. the ISP only provide us internet and a public IP that we are using to host our internal email server. now what will be my smtp to send email.June 16, 2017 at 4:11 am #191705
Email will be (if I read your original post right) from your internal mail server (what is it?). Depending on your setup it may go direct to recipient or via a “smarthost” at your ISP. Since my psychic powers are on the blink today, I don’t know which.
You will need to set up a public DNS record (probably with Digital Ozone, but again may be elsewhere) to tell recipients that the IP address the email comes from (your server or smarthost) maps to the domain you are sending from. I refer you to the last point in my previous post.June 17, 2017 at 5:12 pm #391613
the really issue is that my ISP is the one hosting my public domain but through another hosting provider. in my configuratioon i have selected the option for email to be sent directly to the recipient sever.but in my email delivery i put smtp.my_isp.com because if i query mx record for my dns IP address that what i see. the email is delivered to yahoo but i cannot received back from yahoo. it is complaining of no PTR record for my domain.
now the question still remain is my ISP responsible for the PTR.June 18, 2017 at 12:35 am #191708
Whoever hosts your domain will have a DNS control panel. That is where the change should be made. The ISP (from your description) is the organisation to contact, but they will not do anything unless you tell them to.June 19, 2017 at 8:56 am #337297
You should be able to manage your domain name via a control panel or other management page and this is where the DNS management occurs. It is usually your responsibility.
Some domain hosting companies don’t allow you to edit DNS records so if you cannot see the option to edit DNS, you will, as Ossian advises, need to contact the hosting company and ask them to make the changes for you.
Your ISP may be providing your IP address, but the PTR record management will be via the domain host as it is the domain name that SMTP servers will contact in order to check that your domain name resolves to that IP and vice versa.June 19, 2017 at 9:31 am #271503
In hopes of not clouding the water more, PTR records are not in your DNS zone and any changes to them need to be made by the owner of the public IP. So the PTR record does need to be updated by the ISP. All other records are in your zone (A, CNAME, MX, TXT, etc) and need to be updated by whoever is in control of your DNS.June 19, 2017 at 10:17 am #337299
In order to satisfy the requirements for authenticating the source of our emails we had to make sure the mail record (in one case named an @ record), pointed to our ISP provided IP address for each of the domains we own.
It may be useful if the OP described which DNS records have been configured…
An A record for ‘domain name’ that points to the web address for your domain
An A record for the mail subdomain which points to the ISP provided IP address.
A TXT record containing SPF information defining any filtering/forwarding service (if used).
Two (or more) MX records containing the web address(es) of your filtering service provider (if used), or the IP address provided by the ISP.June 20, 2017 at 5:51 am #391616
Great i have really understood this subject matter and i have taken it up with my ISP. you people have been a great resource. ThanksJune 20, 2017 at 8:00 am #337300
I made a mistake in my last post. MX records cannot contain IP addresses, only web addresses. IP addresses are not valid for MX records. You would use mail.yourdomain.com or whichever address is recommended by your hosting provider’s mail setup if you relay via them.June 20, 2017 at 9:35 am #391620
we dont relay, we send directly to the recipient server. but i need smtp for my server. does this have to be my ISP mx. let say my ISP domain is test.com so can i configure smtp.test.com. and my own domain name is sample.com but this is hosted by my isp. my isp has dedicated this public ip to me 220.127.116.11. if you can put it to contect how it will work for me.June 20, 2017 at 9:52 am #191718
The MX records need to be for the domain you use in your email addresses – a public domain that you have purchased.
[Edit] in the example above, do you own the public domain “sample.com”? That is not the same as setting up an authoritative domain in Exchange – you could do that with any domain name you like. The “ISP domain” and “own domain” do not make this clearJune 20, 2017 at 9:59 am #271508
If you want to receive emails at [email protected], you should:
June 20, 2017 at 11:29 am #391622
- Create an A records of smtp.sample.com (or mail.sample.com or whatever you like) and point it to 18.104.22.168 in the sample.com zone.
- Create an MX record “@” (the @ symbol just means the zone origin which should be sample.com) that points to smtp.sample.com (or whatever record you setup) in the sample.com zone.
- Ask your ISP to update the PTR record for 22.214.171.124 to point to smtp.sample.com (or whatever record you setup)
this is absolutely clear. will do just that. you have been a great resource to me. Do you have any materials that i can build up capacity on this subject matterJune 27, 2017 at 10:17 am #391624
Can you help me out more information about SPF. I want to know which ip address should i add to the SPF. how can i track my domain delivery and incoming route if that will help on the spf listJune 28, 2017 at 10:38 am #271519
You’ll want to use either the public IP address that your email will be coming from or a DNS record that resolves to the IP address your email will be coming from. There are also additional considerations like: is there any other location or IP address that will generate legitimate email for your domain? Do you use a smarthost? Etc
Anything that is involved in the sending of email from your domain should be considered to see if it will impact what you put in your SPF record.June 29, 2017 at 12:36 am #391625
no, we dont use smarthost. this means that i can add the public ip for email server, dns ip addresses.July 5, 2017 at 1:20 am #391626
I have problem with blacklist. is the blacklist as result of my email server sending spam or it is my public ip. how can i protect myself from blacklist. I have install a spam filter to protect only my email server so that it will filter email coming in and out of my server. I am also using Ditigal ocean as my domain host is this a good host platform.July 5, 2017 at 1:39 am #191734
The domain host is, IMHO ,immaterial, as it is the domain and IP that lead to blacklisting.
Do you think you have been sending spam, or has someone been using your domain to send spam (check your postmaster mailbox for undeliverables)? If not, it could well be the IP address, especially if you have just got it .
All you can do is request (politely) to be removed from blacklists – you have no way of making the providers remove you. Use tools like mxtoolbox to check who has blacklisted you and follow their instructions to request removal.
What is your mail server platform, and what is the spam filter you are using?July 5, 2017 at 2:13 am #391627
thanks, i have use the tool box , and what is your recommendation for a good host that will handle emails deliveryJuly 5, 2017 at 4:29 am #191735
“host that will handle email delivery” Are you talking about outgoing emails, in which case many ISPs will provide a smarthost (also called a relay server) for free, or you can pay for a service, or are you talking about incoming emails, where there are some paid for services that will receive your emails, spam filter and store them, then pass them onto your server.
I have both I use in the UK, but a lot depends on where you are and how much you want to pay, also on any legal and data protection requirements you may haveJuly 6, 2017 at 12:15 am #391628
Maybe a relay server. When i send email it immediately bounce back if my ip is been blacklisted. I have install a spam filter which is doing a greate job. Now my emails are going out and coming in. What i want is instead of the email bouncing back immediately, i want it to try reseeding for a period let say 24 hours before bouncing back.
You must be logged in to reply to this topic.