Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!
Exchange 2016 getting bounce backs from google
Exchange 2016 getting bounce backs from google:
mx.google.com gave this error:
[2601:40d:8001:dc00:5436:c
I cannot figure this out for the life of me. If it's as simple as a radio box I might just cry. lol
mx.google.com gave this error:
[2601:40d:8001:dc00:5436:c
I cannot figure this out for the life of me. If it's as simple as a radio box I might just cry. lol
Who is Participating?
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get every solution instantly with Premium.
Start your 7-day free trial.
I wear a lot of hats...
"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.
Experts Exchange Solution brought to you by
Your issues matter to us.
Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.
Start your 7-day free trial
Of course the information above is not for your site but maybe it will help you resolve your problem.
You basically need to contact your ISP and ask them to add a PTR record for your mail server's IP address that matches either your domain or your mail server's name. Essentially, Google's system is doing a reverse IP lookup on your IP and finding the PTR record doesn't match your domain, then refusing the connection because they expect it to be spam.
Agreed
1. Goto http://www.dnsstuff.com/tools
2. Under DNS Lookup, type the full URL your mail server hostname... say mail.domain.com
3. In the pull down menu of "Choose a DNS Record type" select PTR and click the blue triangle button next to the input field of the full URL your mail server hostname.
1. Goto http://www.dnsstuff.com/tools
2. Under DNS Lookup, type the full URL your mail server hostname... say mail.domain.com
3. In the pull down menu of "Choose a DNS Record type" select PTR and click the blue triangle button next to the input field of the full URL your mail server hostname.
I called the ISP and they had the wrong static ipv4 and ipv6 information. I had them setup reverse DNS. I'm waiting the 24-48 hrs to see if it is resolved.
http://www.dnsstuff.com/tools
Post back the results on running the tool as mentioned in my previous comment.
Post back the results on running the tool as mentioned in my previous comment.
Did your ISP charge you for Reverse SMS lookup?
Your result Indicates reverse DNS lookup is not yet made.
Your result Indicates reverse DNS lookup is not yet made.
Then, they are not obliged to help you at all. Setup of Reverse DNS lookup is not free as a lot of re-coding work at ISP side needs to be done.
the ipv4 is good to go. the ipv6 is not. i've checked the records on MXtoolbox.com and it will show for the a record but not the AAAA
Google will not entertain you just to give you an exception for no proper reverse DNS setup and they will just think that you are a SPAM source.
http://www.dnsstuff.com/tools
Post back the results on running the tool as mentioned in my previous comment.
Post back the results on running the tool as mentioned in my previous comment.
@Jackie_man your tool keeps failing. But when i run a reverse lookup on mxtoolbox, it shows my ptr being correct.
error-1.png
error-1.png
All of this is a lot easier to deal with if you use a cloud based spam filter and send your outgoing email through that. They generally take care of the reverse DNS and SPF issues. Also, do you have SPF set up on your public DNS to include your IPv6 record?
Just a note here...Based on google's guidelines, not having an SPF record or DKIM configured will cause the issue you see here. You'll also need to make sure you aren't black-listed. That said, sending mail out from Barracuda is a better solution, since it provides you with better mail security.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
IPv6
From novice to tech pro — start learning today.
-
Business CommunicationCertification: PMI ACP® Project Management Institute Agile Certified P… 340 lessons
-
Business CommunicationCertification: PMI RMP Project Management Institute Risk Management… 113 lessons
-
Microsoft ApplicationsCertification: MOS Microsoft Office Specialist - Excel 2016 Part … 212 lessons
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get every solution instantly with Premium.
Start your 7-day free trial.
From Google's point of view, they are trying to verify the identity of the IP address connecting to them, so they will attempt to look up the PTR record for 2a01:4f8:212:27c8::2.
When they resolve that to staging.findix.com, they will then attempt to check that this resolves back to 2a01:4f8:212:27c8::2 - which it doesn't - see this lookup result.
Reverse (PTR record) Lookup
cwatson@thor:~$ nslookup 31.220.4.52
Server: 127.0.0.1
Address: 127.0.0.1#53
Non-authoritative answer:
52.4.220.31.in-addr.arpa name = tyr.vikingserv.net.
Forward (A record) Lookup
cwatson@thor:~$ nslookup tyr.vikingserv.net
Server: 127.0.0.1
Address: 127.0.0.1#53
Non-authoritative answer:
Name: tyr.vikingserv.net
Address: 31.220.4.52