Can't send email to some domain

U

Uball

New member
Joined
Jan 5, 2010
Messages
1
I tried to send a email to [email protected] but, this is the returning message

SMTP error from remote mail server after initial connection:

host mail.telia.com [81.228.8.165]: 521 pne-smtpin2-sn2.hy.skanova.net Service not available - no PTR record for my.server.ip.address

It is not only this domain which I can't send email to but most of email I had send are success

Did I make some setting wrong?
 
I have also come across this issue before. Some domains require you to have proper PTR records setup for your domain or they will reject your email. Go to http://www.intodns.com and check your domain, it will tell you if you have proper PTR records for mail. Then, if you don't, it's as easy as adding the records.

If you find that you have added the records properly and your mail is still being rejected, you may have to contact your ISP and have them add the records on their end for you (which was the case for me after scratching my head for days).

Very simply - rDNS (reverse DNS) is absolutely essential to send email to a lot of domains, even my own. Let us know how it goes for you
 
blaszlo said:
If you find that you have added the records properly and your mail is still being rejected, you may have to contact your ISP and have them add the records on their end for you (which was the case for me after scratching my head for days).
Click to expand...
Don't bother waiting for days. Generally unless you have at least a class C allocation (256 IP#s) or better your upstream won't delegate rDNS for you but rather will expect you to ask them to do it for you.

So that's the best place to start first.

Jeff
 
Hey,

jlasman said:
Don't bother waiting for days. Generally unless you have at least a class C allocation (256 IP#s) or better your upstream won't delegate rDNS for you but rather will expect you to ask them to do it for you.
Click to expand...

Humm... Well in Texas they will... We've got a few subnets (/28's) that we do rDNS for and they are delegated from AT&T... And the clients are on DSL circuits.

David
 
Yes, AT&T will on DSL circuits for which they allow static DNS. Here in California they call it "Legacy DNS", and they don't supply it on new DSL orders at all. We had it on an old DSL circuit, and when we tried to get the circuit changed (simply to a higher speed) they wouldn't offer us static IP at all.

Do they still offer static IP# on new DSL circuits in Texas?

Note that in general my point still stands. Most providers, even those who offer static IP#, won't delegate it at all without a large minimum allocation. An egregious example is Hosting.Com. Even if you get a whole cage from them and multiple Class C allocations, they still won't delegate rDNS to you.

We looked at them for colocation a few years ago, and this was a main reason for us to not go with them.

Jeff
 
You must log in or register to reply here.
Back
Top