[dns-esp] Problemas con la zona Inversa
Arturo Servin
aservin en lacnic.net
Vie Nov 16 13:54:43 CLST 2012
Tambien sugiero modificar tu resolucion reversa de 190.6.90.203 a algo
como:
203.90.6.190.in-addr.arpa. IN PTR alexandro.anap.cu
Actualmente:
dig -x 190.6.90.203
; <<>> DiG 9.8.3-P1 <<>> -x 190.6.90.203
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 33794
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;203.90.6.190.in-addr.arpa. IN PTR
;; ANSWER SECTION:
203.90.6.190.in-addr.arpa. 1935 IN CNAME 203.200/29.90.6.190.in-addr.arpa.
;; Query time: 292 msec
;; SERVER: 200.7.84.224#53(200.7.84.224)
;; WHEN: Fri Nov 16 14:38:35 2012
;; MSG SIZE rcvd: 68
Slds
as
On 16/11/2012 14:30, Roberto Alvarado wrote:
> Notese, tienes el A record de tu NS apuntando a una ip privada y a una publica...esto provocara intermitencia en la resolución de tus registros desde internet.
> Debes eliminar el registros que apunta a la ip 192.168.1.3
>
>
>
> dig alexandro.anap.cu
>
> ; <<>> DiG 9.7.3-P3 <<>> alexandro.anap.cu
> ;; global options: +cmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17015
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 1, ADDITIONAL: 0
>
> ;; QUESTION SECTION:
> ;alexandro.anap.cu. IN A
>
> ;; ANSWER SECTION:
> alexandro.anap.cu. 3600 IN A 192.168.1.3
> alexandro.anap.cu. 3600 IN A 190.6.90.203
>
> ;; AUTHORITY SECTION:
> anap.cu. 3594 IN NS alexandro.anap.cu.
>
>> ---- Original Message ----
>> From: "Administrador de red" <yosvany en anap.cu>
>> To: "DNS en español" <dns-esp en listas.nic.cl>
>> Sent: Vie, Nov 16, 2012, 1:14 PM
>> Subject: Re: [dns-esp] Problemas con la zona Inversa
>>
>> Hola
>>
>> Ya he revisado nuevamente,
>> y da este resultado
>> heart en proxy:~$ dig a anap.cu
>>
>> ; <<>> DiG 9.7.0-P1 <<>> a anap.cu
>> ;; global options: +cmd
>> ;; Got answer:
>> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9260
>> ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 2
>>
>> ;; QUESTION SECTION:
>> ;anap.cu. IN A
>>
>> ;; ANSWER SECTION:
>> anap.cu. 839 IN A 190.6.90.203
>>
>> ;; AUTHORITY SECTION:
>> anap.cu. 3518 IN NS alexandro.anap.cu.
>>
>> ;; ADDITIONAL SECTION:
>> alexandro.anap.cu. 1967 IN A 192.168.1.3
>> alexandro.anap.cu. 1967 IN A 190.6.90.203
>>
>> ;; Query time: 1902 msec
>> ;; SERVER: 200.55.128.3#53(200.55.128.3)
>> ;; WHEN: Fri Nov 16 10:48:57 2012
>> ;; MSG SIZE rcvd: 97
>>
>>
>> heart en proxy:~$ dig mx anap.cu
>>
>> ; <<>> DiG 9.7.0-P1 <<>> mx anap.cu
>> ;; global options: +cmd
>> ;; Got answer:
>> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37178
>> ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 3
>>
>> ;; QUESTION SECTION:
>> ;anap.cu. IN MX
>>
>> ;; ANSWER SECTION:
>> anap.cu. 3216 IN MX 10 anap.cu.
>>
>> ;; AUTHORITY SECTION:
>> anap.cu. 3215 IN NS alexandro.anap.cu.
>>
>> ;; ADDITIONAL SECTION:
>> anap.cu. 536 IN A 190.6.90.203
>> alexandro.anap.cu. 1664 IN A 192.168.1.3
>> alexandro.anap.cu. 1664 IN A 190.6.90.203
>>
>> ;; Query time: 6150 msec
>> ;; SERVER: 200.55.128.3#53(200.55.128.3)
>> ;; WHEN: Fri Nov 16 10:53:57 2012
>> ;; MSG SIZE rcvd: 113
>>
>>
>> heart en proxy:~$ dig anap.cu +trace
>>
>> ; <<>> DiG 9.7.0-P1 <<>> anap.cu +trace
>> ;; global options: +cmd
>> . 438326 IN NS e.root-servers.net.
>> . 438326 IN NS c.root-servers.net.
>> . 438326 IN NS f.root-servers.net.
>> . 438326 IN NS i.root-servers.net.
>> . 438326 IN NS l.root-servers.net.
>> . 438326 IN NS m.root-servers.net.
>> . 438326 IN NS a.root-servers.net.
>> . 438326 IN NS j.root-servers.net.
>> . 438326 IN NS h.root-servers.net.
>> . 438326 IN NS k.root-servers.net.
>> . 438326 IN NS b.root-servers.net.
>> . 438326 IN NS d.root-servers.net.
>> . 438326 IN NS g.root-servers.net.
>> ;; Received 512 bytes from 200.55.128.3#53(200.55.128.3) in 5264 ms
>>
>> cu. 172800 IN NS ns2.gip.net.
>> cu. 172800 IN NS ns2.ceniai.net.cu.
>> cu. 172800 IN NS rip.psg.com.
>> cu. 172800 IN NS cu.cctld.authdns.ripe.net.
>> cu. 172800 IN NS ns.dns.br.
>> cu. 172800 IN NS ns.ceniai.net.cu.
>> ;; Received 388 bytes from 192.33.4.12#53(c.root-servers.net) in 49453 ms
>>
>> anap.cu. 3600 IN NS alexandro.anap.cu.
>> ;; Received 65 bytes from 204.59.1.222#53(ns2.gip.net) in 59408 ms
>>
>> Segmentation fault
>>
>> heart en proxy:~$ dig mx anap.cu +short
>> 10 anap.cu.
>>
>>
>> Pero los mensajes siguen sin salir, solo son algunos dominios que no me ven
>> que mas puede ser
>>
>> ----- Original Message -----
>> From: "manuel cano" <manolo en daya.cl>
>> To: "DNS en español" <dns-esp en listas.nic.cl>
>> Sent: Wednesday, November 14, 2012 11:50 AM
>> Subject: Re: [dns-esp] Problemas con la zona Inversa
>>
>>
>> El 9 de noviembre de 2012 11:06, Yosvany Hechavarria
>> <yosvany en anap.cu>escribió:
>>
>>>
>>> Hola a todos
>>> Tengo un problema con la zona inversa de mi DNS
>>> Resulta que algunos correos hacia determinados sitios no salen de mi
>>> servidor, me da el siguiente error.
>>>
>>> Thu 2012-11-08 07:32:25: Waiting for protocol to start...
>>> Thu 2012-11-08 07:32:25: <-- 220 mail-emx1.etecsa.net ESMTP Server
>>> Thu 2012-11-08 07:32:25: --> EHLO anap.cu
>>> Thu 2012-11-08 07:32:25: <-- 250-mail-emx1.etecsa.net
>>> Thu 2012-11-08 07:32:25: <-- 250-PIPELINING
>>> Thu 2012-11-08 07:32:25: <-- 250-SIZE 28311552
>>> Thu 2012-11-08 07:32:25: <-- 250-VRFY
>>> Thu 2012-11-08 07:32:25: <-- 250-ETRN
>>> Thu 2012-11-08 07:32:25: <-- 250-ENHANCEDSTATUSCODES
>>> Thu 2012-11-08 07:32:25: <-- 250-8BITMIME
>>> Thu 2012-11-08 07:32:25: <-- 250 DSN
>>> Thu 2012-11-08 07:32:25: --> MAIL From:< chirino en anap.cu> SIZE=71143
>>> Thu 2012-11-08 07:32:26: <-- 250 2.1.0 Ok
>>> Thu 2012-11-08 07:32:26: --> RCPT To:< marta en oxfam.co.cu>
>>> Thu 2012-11-08 07:32:26: <-- 450 4.7.1 Client host rejected: cannot
>>> find your hostname, [190.6.90.203]
>>> Thu 2012-11-08 07:32:26: --> QUIT
>>> Thu 2012-11-08 07:32:26: <-- 221 2.0.0 Bye
>>> Thu 2012-11-08 07:32:26: This message is 0 days old; it has 5 days left
>>> to get delivered
>>> Thu 2012-11-08 07:32:26: SMTP session terminated (Bytes in/out: 529/178)
>>> El mensaje me dice que es la resolucion inversa de mi DNS, pero como lo
>>> arreglo?
>>>
>>> Disculpen la igorancia, pero soy nuevo en el tema de DNS Propios
>>>
>>> Saludos
>>>
>>> Yosvany
>>>
>>> _______________________________________________
>>> dns-esp mailing list
>>> dns-esp en listas.nic.cl
>>> https://listas.nic.cl/mailman/listinfo/dns-esp
>>>
>>>
>>
>> No, el mensaje no dice eso, dice "cannot find your hostname" (no puedo
>> encontrar tu nombre de host), si miras mas arriba tu server lo saluda
>> indicando su nombre "anap.cu" ( EHLO anap.cu ), y ese es el nombre que no
>> existe:
>>
>> vakita:~ # dig a anap.cu +short
>> vakita:~ #
>>
>> al parecer tu mx se llama de otra forma
>>
>> vakita:~ # dig mx anap.cu +short
>> 10 alexandro.anap.cu.
>>
>> entonces para que funcione tendrás que elegir UNA opción:
>>
>> a) configurar a tu server de correos a saludar como "alexandro.anap.cu"
>>
>> b) crear un registro en tu dns para "anap.cu"
>>
>> Saludos
>> Manuel Cano
>>
>>
>>
>> --------------------------------------------------------------------------------
>>
>>
>> _______________________________________________
>> dns-esp mailing list
>> dns-esp en listas.nic.cl
>> https://listas.nic.cl/mailman/listinfo/dns-esp
>>
>>
>> _______________________________________________
>> dns-esp mailing list
>> dns-esp en listas.nic.cl
>> https://listas.nic.cl/mailman/listinfo/dns-esp
>
> _______________________________________________
> dns-esp mailing list
> dns-esp en listas.nic.cl
> https://listas.nic.cl/mailman/listinfo/dns-esp
>
Más información sobre la lista de distribución dns-esp