How to change the reverse dns entry in TATA

[Sudip Dutta]

Hi,

I`m in India and my ISP is TATA INDICOM.I have an infinity 256 plan
with static IP 2.2.2.2.(IP changed here). I have purchased a domain
name and have my own mail server configured. The problem is that the
reverse dns entry for this IP 2.2.2.2 in dns.vsnl.net.in(The name
server responsible) is like that-

2.2.2.2 PTR record: 2.2.2.2.bb-static.vsnl.net.in. [TTL 86400s]
[A=None]

In order to proper working of my mail server (every mail server is
rejecting my mail as SPAM) this PTR record should point to my domain
mail.xyz.net in place of 2.2.22.bb-static.vsnl.net.in.

This is the only purpose why I purchased TATA INDICOM Broadband.I
already have BSNL 512 kbps broadband installed for my other uses.But
they dont provide static Ip with this plan and so I purchased broadband
from TATA.

I have my own dns server also which is working fine.

Please help me to change this PTR record or how to delegate authority
to my DNS server .Any help is appreciable.

Regards,
Sudip Dutta

[Lanwench [MVP - Exchange]]

In news:1154498931....@m79g2000cwm.googlegroups.com,
Sudip Dutta <sudi...@gmail.com> typed:

> Hi,
>
> I`m in India and my ISP is TATA INDICOM.I have an infinity 256 plan
> with static IP 2.2.2.2.(IP changed here).

Why? Is it a secret?

> I have purchased a domain
> name

The actual domain name would also help....

> and have my own mail server configured. The problem is that the
> reverse dns entry for this IP 2.2.2.2 in dns.vsnl.net.in(The name
> server responsible) is like that-
>
> 2.2.2.2 PTR record: 2.2.2.2.bb-static.vsnl.net.in. [TTL 86400s]
> [A=None]
>
> In order to proper working of my mail server (every mail server is
> rejecting my mail as SPAM) this PTR record should point to my domain
> mail.xyz.net in place of 2.2.22.bb-static.vsnl.net.in.
>

Not necessarily. Sensible mail admins do not block mail because the PTR
doesn't match the server's hostname. Now, that isn't to say that there are a
lot of zealots managing mail servers, but this is not the most likely cause.

> This is the only purpose why I purchased TATA INDICOM Broadband.I
> already have BSNL 512 kbps broadband installed for my other uses.But
> they dont provide static Ip with this plan and so I purchased
> broadband from TATA.
>
> I have my own dns server also which is working fine.
>
> Please help me to change this PTR record

You can't.....only the people who own that IP block can do this.

> or how to delegate authority
> to my DNS server .

You can't....your ISP could, but I doubt they will.

> Any help is appreciable.

Try posting your real domain name so we can have a look at your setup. We
won't bite. Well, most people won't. I sometimes do. :)
>
> Regards,
> Sudip Dutta

[Sudip Dutta]

Well , the domain is mail.unisolindia.in.
Thanks for your reply.
Waiting for your comment.

[Steve Foster [SBS MVP]]

Lanwench [MVP - Exchange] wrote:

>>In order to proper working of my mail server (every mail server is
>>rejecting my mail as SPAM) this PTR record should point to my domain
>>mail.xyz.net in place of 2.2.22.bb-static.vsnl.net.in.
>>
>
>Not necessarily. Sensible mail admins do not block mail because the PTR
>doesn't match the server's hostname. Now, that isn't to say that there are
>a lot of zealots managing mail servers, but this is not the most likely
>cause.

There's no good reason that they shouldn't. Mismatched DNS records is
either sloppy administration or possible evidence of spammer laziness.

If it was difficult to arrange consistent DNS naming for email, then it
would be reasonable to expect folks not to check. But it isn't.

I think it's likely that the number of mail servers/mail admins who insist
on matching PTR records is going to increase.

>>or how to delegate authority
>>to my DNS server .
>
>You can't....your ISP could, but I doubt they will.

I'm sure a lot of ISPs aren't even aware that PTR zones can be subdelegated.

>>Any help is appreciable.
>
>Try posting your real domain name so we can have a look at your setup. We
>won't bite. Well, most people won't. I sometimes do. :)

We don't really need it in this instance, do we. The information supplied
was sufficient to suggest options.

--
Steve Foster [SBS MVP]
---------------------------------------
MVPs do not work for Microsoft. Please reply only to the newsgroups.

[Steve Foster [SBS MVP]]

Sudip Dutta wrote:

Your ISP, Tata Indicom, would be the only ones who can do this.

If they won't change the PTR, the easiest solution would be for you to use
the name they've set for your MX record, and have your mail server
(presumably SBS Exchange) emit that as the FQDN (assuming it is Exchange,
SMTP Virtual Server Properties, Delivery tab, Advanced > Fully-Qualified
Domain Name).

[Lanwench [MVP - Exchange]]

In news:xn0ephs1t...@msnews.microsoft.com,
Steve Foster [SBS MVP] <steve....@picamar.co.uk> typed:

I would always rather have the option to run an nslookup or something when
somone says they're having problems sending mail to someone. It saves time
and back&forth, and there's really no reason to hide the information.

It is highly unusual for a mail server to reject mail from a server merely
because the reverse lookup isn't identical to its MX record, or even to the
name Exchange presents when connecting. Overzealous admins do this, and it's
a rookie mistake. I'm pretty sure that, for example, Citibank's mail
servers, and public IPs, aren't configured that way.

[Lanwench [MVP - Exchange]]

In news:u9sS2pkt...@TK2MSFTNGP04.phx.gbl,
Lanwench [MVP - Exchange]
<lanw...@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> typed:
> In news:xn0ephs1t...@msnews.microsoft.com,
\

<snip>

>> We don't really need it in this instance, do we. The information
>> supplied was sufficient to suggest options.
>
> I would always rather have the option to run an nslookup or something
> when somone says they're having problems sending mail to someone. It
> saves time and back&forth, and there's really no reason to hide the
> information.
> It is highly unusual for a mail server to reject mail from a server
> merely because the reverse lookup isn't identical to its MX record,
> or even to the name Exchange presents when connecting. Overzealous
> admins do this, and it's a rookie mistake. I'm pretty sure that, for
> example, Citibank's mail servers, and public IPs, aren't configured
> that way.

....damn, I hit Send too fast.
http://www.dnsreport.com/tools/dnsreport.ch?domain=unisolindia.in indicates
problems connecting to the mail server, as well