| 1 |
On Sat, 7 Jan 2012 09:45:44 -0600 |
| 2 |
Carlos Sura <carlos.sura1@××××××××××.com> wrote: |
| 3 |
|
| 4 |
> Hello mates, |
| 5 |
> |
| 6 |
> I have a problem, my provider does not want to set rDNS to my IP's |
| 7 |
> since I have 5 IP's rotating for my server, I don't know why. So he |
| 8 |
> told me I can do this manually. |
| 9 |
> |
| 10 |
> So I've added this as a master zone: |
| 11 |
> $ttl 38400 |
| 12 |
> 80.236.109.in-addr.arpa. IN SOA dominio.dominio.com. |
| 13 |
> abuse.dominio.com. (notice that last digits are miss) |
| 14 |
> 1325905990 |
| 15 |
> 10800 |
| 16 |
> 3600 |
| 17 |
> 604800 |
| 18 |
> 38400 ) |
| 19 |
> 80.236.109.in-addr.arpa. IN NS dominio.dominio.com. |
| 20 |
> xx.xx.xxx.xxx.in-addr.arpa. IN PTR dominio.com. |
| 21 |
> xx.xx.xxx.xxx.in-addr.arpa. IN PTR mail.dominio.com. |
| 22 |
> xx.xx.xxx.xxx.in-addr.arpa. IN PTR ns1.dominio.com. |
| 23 |
> xx.xx.xxx.xxx.in-addr.arpa. IN PTR dominio.com. |
| 24 |
> xx.xx.xxx.xxx.in-addr.arpa. IN PTR mail.dominio.com. |
| 25 |
> xx.xx.xxx.xxx.in-addr.arpa. IN PTR ns2.dominio.com. |
| 26 |
> xx.xx.xxx.xxx.in-addr.arpa. IN PTR dominio.com. |
| 27 |
> xx.xx.xxx.xxx.in-addr.arpa. IN PTR mail.dominio.com. |
| 28 |
> xx.xx.xxx.xxx.in-addr.arpa. IN PTR dominio.com. |
| 29 |
> xx.xx.xxx.xxx.in-addr.arpa. IN PTR mail.dominio.com. |
| 30 |
> xx.xx.xxx.xxx.in-addr.arpa. IN PTR dominio.com. |
| 31 |
> xx.xx.xxx.xxx.in-addr.arpa. IN PTR mail.dominio.com. |
| 32 |
> |
| 33 |
> |
| 34 |
> But it does not reflect any change in any machine, just in the local |
| 35 |
> machine I get the answer, when I try in any other machine, it still |
| 36 |
> showing me the rDNS of my provider. |
| 37 |
|
| 38 |
|
| 39 |
The reason is quite simple and most sane ISPs will do it that way. |
| 40 |
|
| 41 |
rDNS is NOT your A records in reverse, and you have no right of access |
| 42 |
to the zone. |
| 43 |
|
| 44 |
in-addr.arpa serves an entirely different purpose, it documents the |
| 45 |
layout of the ISPs address space. Your 5 IPs have not been delegated to |
| 46 |
you and you do not own them per whois, they still belong to your ISP and |
| 47 |
are merely recorded in the ISP record as assigned for your use. |
| 48 |
|
| 49 |
Therefore the ISP will use their own documentation standards to |
| 50 |
determine what is in the rDNS zone. |
| 51 |
|
| 52 |
Additionally, delegating out a /29 is a gigantic pain in the arse and |
| 53 |
leads to an unmaintainable mess in very short order (so says the poor |
| 54 |
sucker that's had to fix it...). At work we never sub-delegate out rDNS |
| 55 |
to customers; but we do do it for downstream re-sellers as they are |
| 56 |
ISPs in the in own right. |
| 57 |
|
| 58 |
So your ISP is quite correct in what they are saying. However, I would |
| 59 |
like to see a clarification of what your support contact means when he |
| 60 |
says "do it manually" - that doesn't make any sense |
| 61 |
|
| 62 |
-- |
| 63 |
Alan McKinnon |
Archives