1 |
On Saturday, January 07, 2012 at 16:15:47 UTC, carlos.sura1@××××××××××.com confabulated: |
2 |
|
3 |
> On 7 January 2012 10:08, Duane Hill <duihi77@×××××.com> wrote: |
4 |
|
5 |
>> On Saturday, January 07, 2012 at 15:45:44 UTC, carlos.sura1@××××××××××.comconfabulated: |
6 |
>> |
7 |
>> > Hello mates, |
8 |
>> |
9 |
>> > I have a problem, my provider does not want to set rDNS to my IP's since |
10 |
>> I |
11 |
>> > have 5 IP's rotating for my server, I don't know why. So he told me I can |
12 |
>> > do this manually. |
13 |
>> |
14 |
>> > So I've added this as a master zone: |
15 |
>> > $ttl 38400 |
16 |
>> > 80.236.109.in-addr.arpa. IN SOA dominio.dominio.com. abuse.dominio.com. |
17 |
>> > (notice that last digits are miss) |
18 |
>> > 1325905990 |
19 |
>> > 10800 |
20 |
>> > 3600 |
21 |
>> > 604800 |
22 |
>> > 38400 ) |
23 |
>> > 80.236.109.in-addr.arpa. IN NS dominio.dominio.com. |
24 |
>> > xx.xx.xxx.xxx.in-addr.arpa. IN PTR dominio.com. |
25 |
>> > xx.xx.xxx.xxx.in-addr.arpa. IN PTR mail.dominio.com. |
26 |
>> > xx.xx.xxx.xxx.in-addr.arpa. IN PTR ns1.dominio.com. |
27 |
>> > xx.xx.xxx.xxx.in-addr.arpa. IN PTR dominio.com. |
28 |
>> > xx.xx.xxx.xxx.in-addr.arpa. IN PTR mail.dominio.com. |
29 |
>> > xx.xx.xxx.xxx.in-addr.arpa. IN PTR ns2.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 |
>> > xx.xx.xxx.xxx.in-addr.arpa. IN PTR dominio.com. |
33 |
>> > xx.xx.xxx.xxx.in-addr.arpa. IN PTR mail.dominio.com. |
34 |
>> > xx.xx.xxx.xxx.in-addr.arpa. IN PTR dominio.com. |
35 |
>> > xx.xx.xxx.xxx.in-addr.arpa. IN PTR mail.dominio.com. |
36 |
>> |
37 |
>> |
38 |
>> > But it does not reflect any change in any machine, just in the local |
39 |
>> > machine I get the answer, when I try in any other machine, it still |
40 |
>> showing |
41 |
>> > me the rDNS of my provider. |
42 |
>> |
43 |
>> > Any help? |
44 |
>> |
45 |
>> The setting up rDNS on the one server would only be for that local |
46 |
>> server. All other servers that are not using the one local server |
47 |
>> for DNS resolution would look to your provider. You would either have |
48 |
>> to 1) get your provider to delegate rDNS to you, 2) duplicate the rDNS |
49 |
>> setup on the additional servers, or 3) point DNS (resolv.conf) to |
50 |
>> the one server that is working locally. |
51 |
>> |
52 |
>> Without your provider delegating rDNS to you, the "rest of the |
53 |
>> world" would still be looking to your provider for rDNS, regardless. |
54 |
>> |
55 |
>> -- |
56 |
>> If at first you don't succeed... |
57 |
>> ...so much for skydiving. |
58 |
>> |
59 |
>> |
60 |
>> |
61 |
> Hello Duane, |
62 |
|
63 |
> Thank your for answer. I just have one question: What you mean that my |
64 |
> provider has to delegate rDNS to me? I have the resolv.conf with my own |
65 |
> nameservers. |
66 |
|
67 |
> Locally it shows as I want, but not on the Internet. What would I need to |
68 |
> ask to my provider? |
69 |
|
70 |
> Thanks! |
71 |
|
72 |
You would have to find out if your provider would delegate rDNS for |
73 |
the IP address range to you. You would have to provide them with the |
74 |
name server IP addresses that would be serving rDNS. I can only assume |
75 |
if they will not set up the rDNS for you, they may not delegate rDNS |
76 |
either. |
77 |
|
78 |
If you are trying to set up an email server and your provider will not |
79 |
delegate or set up the rDNS, just set up your email server to relay |
80 |
outbound messages through your provider. That is exactly what I am |
81 |
doing here and have been for 5+ years without any issues. |
82 |
|
83 |
-- |
84 |
If at first you don't succeed... |
85 |
...so much for skydiving. |