multiple ptr record em bind

1

Estou executando um pequeno ISP aqui e possuo alguns intervalos de IP.

Eu dei alguns endereços IP públicos para alguns dos meus clientes e eles estão executando servidores de email neles. Eles me pediram para adicionar entradas DNS reversas ( PTR ) para seus IPs.

Eu tenho o Bind em execução no meu servidor. Posso adicionar vários registros PTR no mesmo servidor / mesmo arquivo?

Faixa de IP que eu possuo: 192.168.10.0/24

Customer A: 192.168.10.103  
Customer B: 192.168.10.199  
Customer C: 192.168.10.169  
Customer D: 192.168.10.69  

Obrigado.

    
por root 18.08.2015 / 14:01

2 respostas

0

Como você pode ver em este exemplo do TLDP , você pode ter vários PTR registros a mesma zona.

$TTL 3D
@               IN      SOA     yourdomain.com. root.yourdomain.com. (
                                199609206       ; Serial
                                28800   ; Refresh
                                7200    ; Retry
                                604800  ; Expire
                                86400)  ; Minimum TTL
                        NS      ns1.yourdomain.com.
                        NS      ns2.yourdomain.net.
;
;       Servers
;
1       PTR     router.yourdomain.com.
2       PTR     server.yourdomain.com.
;
;       Customers
;
69      PTR     mail.customerD.com.
103     PTR     mail.customerA.com.
169     PTR     mail.customerC.com.
199     PTR     mail.customerB.com.

É uma boa ideia colocar os IPs que você alocar no seu arquivo de reversos para evitar duplicatas.

exemplo de trabalho

Isso parece bom para mim:

$ dig -x 103.249.240.224

; <<>> DiG 9.9.5-3ubuntu0.4-Ubuntu <<>> -x 103.249.240.224
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8551
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; QUESTION SECTION:
;224.240.249.103.in-addr.arpa.  IN  PTR

;; ANSWER SECTION:
224.240.249.103.in-addr.arpa. 1685 IN   PTR mk.localhost-server.com.

;; ADDITIONAL SECTION:
mk.localhost-server.com. 21526  IN  A   103.249.240.224

;; Query time: 2 msec
;; SERVER: 127.0.1.1#53(127.0.1.1)
;; WHEN: Wed Aug 19 09:53:51 PDT 2015
;; MSG SIZE  rcvd: 99

$ dig mk.localhost-server.com

; <<>> DiG 9.9.5-3ubuntu0.4-Ubuntu <<>> mk.localhost-server.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61167
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;mk.localhost-server.com.   IN  A

;; ANSWER SECTION:
mk.localhost-server.com. 21520  IN  A   103.249.240.224

;; Query time: 1 msec
;; SERVER: 127.0.1.1#53(127.0.1.1)
;; WHEN: Wed Aug 19 09:53:56 PDT 2015
;; MSG SIZE  rcvd: 57

chicks@silver 09:53:56 ~ !515 $ 

e agora está quebrado

confirmar quebrado:

$ dig -x 103.249.240.224

; <<>> DiG 9.9.5-3ubuntu0.3-Ubuntu <<>> -x 103.249.240.224
;; global options: +cmd
;; connection timed out; no servers could be reached

de link :

PWS3v2 11784ms
  0  c.in-addr-servers.arpa  196.216.169.10  NON-AUTH  296 ms  Received 6 Referrals , rcode=NO_ERROR    103.in-addr.arpa.   86400   IN  NS  ns1.apnic.net,103.in-addr.arpa. 86400 IN    NS  ns2.lacnic.net,103.in-addr.arpa.    86400   IN  NS  ns3.apnic.net,103.in-addr.arpa. 86400   IN  NS  ns4.apnic.net,103.in-addr.arpa. 86400   IN  NS  sec1.authdns.ripe.net,103.in-addr.arpa. 86400   IN  NS  tinnie.arin.net,  

  1  ns4.apnic.net  202.12.31.140  NON-AUTH  187 ms  Received 4 Referrals , rcode=NO_ERROR    240.249.103.in-addr.arpa. 86400   IN  NS ns2.gazonindia.com,240.249.103.in-addr.arpa. 86400   IN  NS ns4.gazonindia.com,240.249.103.in-addr.arpa. 86400   IN  NS ns3.gazonindia.com,240.249.103.in-addr.arpa. 86400   IN  NS  ns1.gazonindia.com,  

  2  ns4.gazonindia.com  103.249.240.10  NON-AUTH  187 ms  Timeout after 3 sec, rcode=NO_ERROR      

  2  ns1.gazonindia.com  103.249.240.8  NON-AUTH  187 ms  Timeout after 3 sec, rcode=NO_ERROR      

  2  ns3.gazonindia.com  103.249.240.9  NON-AUTH  187 ms  Timeout after 3 sec, rcode=NO_ERROR      

  2  ns2.gazonindia.com    NON-AUTH  187 ms  Timeout resolving IP, rcode=NO_ERROR

Parece que os servidores do Gazon não estão respondendo. Então, vamos descobrir quem entrar em contato via whois :

$ whois 103.249.240.224
% [whois.apnic.net]
% Whois data copyright terms    http://www.apnic.net/db/dbcopyright.html

% Information related to '103.249.240.0 - 103.249.243.255'

inetnum:        103.249.240.0 - 103.249.243.255
netname:        GAZON
descr:          Gazon Communications India Limited
admin-c:        KD220-AP
tech-c:         SA683-AP
country:        IN
mnt-by:         MAINT-IN-IRINN
mnt-irt:        IRT-IRINN-IN
status:         ASSIGNED portable
changed:        [email protected] 20130613
mnt-routes:     MAINT-IN-GAZON
source:         APNIC

irt:            IRT-IRINN-IN
address:        Flat no. 6B, Uppals M6 Plaza, 6 Jasola District Centre, New Delhi-110025
e-mail:         [email protected]
abuse-mailbox:  [email protected]
admin-c:        IH175-AP
tech-c:         IH174-AP
auth:           # Filtered
mnt-by:         MAINT-IN-IRINN
changed:        [email protected] 20120907
source:         APNIC

role:           System Admin
address:        Parason House, 28, Venkatesh Nagar, Aurangabad, Maharashtra
country:        IN
phone:          +91-9762055555
fax-no:         +91-2402332944
e-mail:         [email protected]
admin-c:        KD220-AP
tech-c:         KD220-AP
nic-hdl:        SA683-AP
remarks:        send spam and abuse report to [email protected]
notify:         [email protected]
abuse-mailbox:  [email protected]
mnt-by:         MAINT-IN-PARASON
changed:        [email protected] 20140801
source:         APNIC

person:         Kishor Desarda
address:        Parason House, 28, Venkatesh Nagar, Aurangabad, Maharashtra
country:        IN
phone:          +91-9762055555
fax-no:         +91-2402332944
e-mail:         [email protected]
nic-hdl:        KD220-AP
remarks:        send spam and abuse report to [email protected]
notify:         [email protected]
abuse-mailbox:  [email protected]
mnt-by:         MAINT-IN-PARASON
changed:        [email protected] 20140801
source:         APNIC

% Information related to '103.249.240.0/24AS132770'

route:          103.249.240.0/24
descr:          Gazon Communications India Limited
origin:         AS132770
country:        IN
mnt-lower:      MAINT-IN-IRINN
mnt-routes:     MAINT-IN-IRINN
mnt-by:         MAINT-IN-IRINN
changed:        [email protected] 20130708
source:         APNIC

% Information related to '103.249.240.0 - 103.249.243.255'

inetnum:        103.249.240.0 - 103.249.243.255
netname:        GAZON
descr:          Gazon Communications India Limited
admin-c:        KD1-IN
tech-c:         MN8-IN
country:        IN
mnt-by:         MAINT-IN-GAZON
mnt-irt:        IRT-GAZON-IN
status:         ASSIGNED portable
changed:        [email protected]
source:         APNIC

irt:            IRT-GAZON-IN
address:        Pune
phone:          +91 02065101230
fax-no:         +91 2402332944
e-mail:         [email protected]
abuse-mailbox:  [email protected]
admin-c:        KD1-IN
tech-c:         MN8-IN
auth:           CRYPT-PW yx9RQZOlthZT6
remarks:        send spam and abuse report to [email protected]
mnt-by:         MAINT-IN-GAZON
changed:        [email protected] 20130613
source:         IRINN

role:           Manager NOC
address:        Pune
country:        IN
phone:          +91 02065101230
fax-no:         +91 2402332944
e-mail:         [email protected]
admin-c:        KD1-IN
tech-c:         KD1-IN
nic-hdl:        MN8-IN
remarks:        send spam and abuse report to [email protected]
notify:         [email protected]
abuse-mailbox:  [email protected]
mnt-by:         MAINT-IN-GAZON
changed:        [email protected] 20130613
source:         IRINN

person:         Kishor Desarda
address:        Parason House, 28, Venkatesh Nagar, Jalna Road
country:        IN
phone:          +91 02065101230
fax-no:         +91 2402332944
e-mail:         [email protected]
nic-hdl:        KD1-IN
remarks:        send spam and abuse report to [email protected]
notify:         [email protected]
abuse-mailbox:  [email protected]
mnt-by:         MAINT-IN-GAZON
changed:        [email protected] 20130613
source:         IRINN

% Information related to '103.249.240.0/24AS132770'

route:          103.249.240.0/24
descr:          Gazon Communications India Limited
country:        IN
origin:         AS132770
remarks:        [email protected]
notify:         [email protected]
mnt-lower:      MAINT-IN-GAZON
mnt-routes:     MAINT-IN-GAZON
mnt-by:         MAINT-IN-GAZON
changed:        [email protected] 20130625
source:         IRINN

% This query was served by the APNIC Whois Service version 1.69.1-APNICv1r0 (UNDEFINED)
    
por 18.08.2015 / 14:33
0

Sim, você não só pode ter vários PTR registros no mesmo arquivo de zona reversa, se sua rede IP for 192.168.10.0/24 e você tiver uma zona reversa em 10.168.192.in-addr.arpa você não realmente tem uma solução alternativa razoável.

É importante notar que a única coisa que uma zona reversa tem relação direta com a rede IP . Os registros de ponteiro na zona podem se referir a nomes em qualquer número de zonas (quaisquer nomes que sejam os nomes canônicos para esses endereços IP).

Há um equívoco comum em que uma zona reversa é emparelhada com uma zona "avançada". Isso simplesmente não é verdade e só posso adivinhar que essa ideia vem de como documentação e guias frequentemente mostram um exemplo de cada um sem entrar em detalhes sobre o propósito ou que tipo de relação existe ou, como é o caso, não existe t entre os dois exemplos.

    
por 19.08.2015 / 19:26