[Pdns-users] Problems setting pdns as master and slave reverse dns.

[Gabriel Garrido]

Yes, the second record is just a test, the other record is the correct 
one, I mean:

8.149.92.190.in-addr.arpa. 86400 IN     PTR ns1.clientsservicesolution.com.

the domains table:

+----+---------------------------------+--------+------------+--------+-----------------+---------+
| id | name                            | master | last_check | type   | 
notified_serial | account |
+----+---------------------------------+--------+------------+--------+-----------------+---------+
| 73 | 149.92.190.in-addr.arpa         | NULL   |       NULL | NATIVE 
|      2010101901 | NULL    |

the records table:

+-------+-----------+--------------------------------+------+---------------------------------------------------------------------------------+-------+------+-------------+
| id    | domain_id | name                           | type | 
content                                                                         
| ttl   | prio | change_date |
+-------+-----------+--------------------------------+------+---------------------------------------------------------------------------------+-------+------+-------------+
| 16542 |        73 | 7.149.92.190.in-addr.arpa      | PTR  | 
ns0.clientsservicesolution.com                                                  
| 86400 |    0 |  2010101901 |
| 16543 |        73 | 8.149.92.190.in-addr.arpa      | PTR  | 
ns1.clientsservicesolution.com                                                  
| 86400 |    0 |  2010101901 |
| 16540 |        73 | ns0.clientsservicesolution.com | A    | 
190.92.149.7                                                                    
| 86400 |    0 |  2010101901 |
| 16541 |        73 | ns1.clientsservicesolution.com | A    | 
190.92.149.8                                                                    
| 86400 |    0 |  2010101901 |
| 16531 |        73 | clientsservicesolution.com     | SOA  | 
ns0.clientsservicesolution.com hostmaster.clientsservicesolution.com 
2010101901 | 86400 |    0 |  2010101901 |
| 16534 |        73 | clientsservicesolution.com     | NS   | 
ns0.clientsservicesolution.com                                                  
| 86400 |    0 |  2010101901 |
| 16535 |        73 | clientsservicesolution.com     | NS   | 
ns1.clientsservicesolution.com                                                  
| 86400 |    0 |  2010101901 |
| 16536 |        73 | 149.92.190.in-addr.arpa        | NS   | 
ns0.clientsservicesolution.com                                                  
| 86400 |    0 |  2010101901 |
| 16537 |        73 | 149.92.190.in-addr.arpa        | NS   | 
ns1.clientsservicesolution.com                                                  
| 86400 |    0 |  2010101901 |
+-------+-----------+--------------------------------+------+---------------------------------------------------------------------------------+-------+------+-------------+

that's the data in the database...

Thanks.

Regards.
Gabriel.


On 10/19/2010 01:27 PM, Christian HofstÀdtler wrote:
>  From what I see from your nameserver, you
> a) don't have a SOA record in place  (dig @190.92.149.7
> 149.92.190.in-addr.arpa soa returns nothing)
> and
> b) you have duplicate PTRs, one pointing to nonsense and the other being right:
>
> probably right ->  8.149.92.190.in-addr.arpa. 86400 IN     PTR
> ns1.clientsservicesolution.com.
> wrong ->  8.149.92.190.in-addr.arpa. 86400 IN     PTR
> 8.149.92.190.in-addr.ARPA.
>
> -ch
>    

-- 
Gabriel Garrido.
Network Administrator.
Workjoy Argentina S.A.
Technology Department.