[lacnog] Resolución inversa 170.80.0.0/16
Carlos M. Martinez
carlosm3011 en gmail.com
Mie Ago 9 15:44:46 BRT 2017
Hola Gerardo,
Gracias por reportar este problema.
como detalle, el /16 no se debe delegar sino que usamos un esquema
llamado de “zonelets” en la cual nosotros compilamos parte de la
zona 170/8 y se la subimos a ARIN para que ellos la incluyan en sus
zonas. Eso igual es un detalle, para ti como usuario debira ser
transparente.
¿Cual es el bloque que tienes delegado? ¿el /16 entero?
s2
/Carlos
On 9 Aug 2017, at 15:39, Gerardo Guerrero wrote:
> Hola a todos
>
> Alguien se ha visto en la necesidad de hacer resolución inversa con
> IPs asignadas por LACNIC del segmento 170.80.0.0/16?, al parecer en un
> principio estaba asignado a ARIN pero fue cedido a LACNIC, el tema es
> que a la hora de querer resolver inversamente, la solicitud se queda
> en servidores de ARIN, ya lo reporte con ellos pero me mandan a
> LACNIC, pero según yo falta que ARIN delegue el segmento
> 170.80.0.0/16 a Servers de LACNIC. (Ya revise mis DNS Servers y si
> resuelven autoritariamente por el segmento asignado en cuestión).
>
> Prueba de DNS Query hacia IP ejemplo 170.80.28.1
>
> /Step 1//
> //We are at the first step. All DNS queries, if not previously cached
> (and we do NOT cache), starts from the root servers.//
> //
> //98.04 ms i.root-servers.net [192.36.148.17] (Sweden)//
> //;;Authority//
> //in-addr.arpa. 172800 undefined NS a.in-addr-servers.arpa.//
> //in-addr.arpa. 172800 undefined NS b.in-addr-servers.arpa.//
> //in-addr.arpa. 172800 undefined NS c.in-addr-servers.arpa.//
> //in-addr.arpa. 172800 undefined NS d.in-addr-servers.arpa.//
> //in-addr.arpa. 172800 undefined NS e.in-addr-servers.arpa.//
> //in-addr.arpa. 172800 undefined NS f.in-addr-servers.arpa.//
> //;;Additional//
> //a.in-addr-servers.arpa. 172800 undefined AAAA
> 2001:500:13:0:0:0:0:73//
> //b.in-addr-servers.arpa. 172800 undefined AAAA
> 2001:500:87:0:0:0:0:87//
> //c.in-addr-servers.arpa. 172800 undefined AAAA
> 2001:43f8:110:0:0:0:0:10//
> //d.in-addr-servers.arpa. 172800 undefined AAAA
> 2001:13c7:7010:0:0:0:0:53//
> //e.in-addr-servers.arpa. 172800 undefined AAAA
> 2001:dd8:6:0:0:0:0:101//
> //f.in-addr-servers.arpa. 172800 undefined AAAA
> 2001:67c:e0:0:0:0:0:1//
> //a.in-addr-servers.arpa. 172800 undefined A 199.212.0.73//
> //b.in-addr-servers.arpa. 172800 undefined A 199.253.183.183//
> //c.in-addr-servers.arpa. 172800 undefined A 196.216.169.10//
> //d.in-addr-servers.arpa. 172800 undefined A 200.10.60.53//
> //e.in-addr-servers.arpa. 172800 undefined A 203.119.86.101//
> //f.in-addr-servers.arpa. 172800 undefined A 193.0.9.1//
> //
> //We got referrals from i.root-servers.net//
> //Step 2//
> //We've got referrals (e.in-addr-servers.arpa.,
> a.in-addr-servers.arpa., f.in-addr-servers.arpa.,
> b.in-addr-servers.arpa., c.in-addr-servers.arpa.,
> d.in-addr-servers.arpa.) from queries on previous step. We'll query
> them now, until we got an authoritative result//
> //116.77 ms d.in-addr-servers.arpa. [200.10.60.53] (Uruguay)//
> //;;Authority//
> //170.in-addr.arpa. 86400 undefined NS arin.authdns.ripe.net.//
> //170.in-addr.arpa. 86400 undefined NS r.arin.net.//
> //170.in-addr.arpa. 86400 undefined NS u.arin.net.//
> //170.in-addr.arpa. 86400 undefined NS x.arin.net.//
> //170.in-addr.arpa. 86400 undefined NS y.arin.net.//
> //170.in-addr.arpa. 86400 undefined NS z.arin.net.//
> //
> //We got referrals from d.in-addr-servers.arpa.//
> //Step 3//
> //We've got referrals (arin.authdns.ripe.net., x.arin.net.,
> y.arin.net., r.arin.net., z.arin.net., u.arin.net.) from queries on
> previous step. We'll query them now, until we got an authoritative
> result//
> //71.79 ms arin.authdns.ripe.net. [193.0.9.10] (Netherlands)//
> //;;Query failed: "DNS request failed: The domain name referenced in
> the query does not exist."//
> //7.78 ms y.arin.net. [192.82.134.30] (United States)//
> //;;Query failed: "DNS request failed: The domain name referenced in
> the query does not exist."//
> //7.39 ms r.arin.net. [199.180.180.63] (Chantilly, Virginia, United
> States)//
> //;;Query failed: "DNS request failed: The domain name referenced in
> the query does not exist."//
> //7.33 ms z.arin.net. [199.212.0.63] (United States)//
> //;;Query failed: "DNS request failed: The domain name referenced in
> the query does not exist."//
> //91.34 ms x.arin.net. [199.71.0.63] (United States)//
> //;;Query failed: "DNS request failed: The domain name referenced in
> the query does not exist."//
> //1.49 ms u.arin.net. [204.61.216.50] (Berkeley, California, United
> States)//
> //;;Query failed: "DNS request failed: The domain name referenced in
> the query does not exist."//
> //
> //arin.authdns.ripe.net., y.arin.net., r.arin.net., z.arin.net.,
> x.arin.net. and u.arin.net. Query failed: "DNS request failed: The
> domain name referenced in the query does not exist.".//
> //None of queried servers gave any results//
> //Done!
>
> /Saludos
> Gerardo Guerrero
> Coeficiente Comunicaciones CTO/
> /
> _______________________________________________
> LACNOG mailing list
> LACNOG en lacnic.net
> https://mail.lacnic.net/mailman/listinfo/lacnog
> Cancelar suscripcion: https://mail.lacnic.net/mailman/options/lacnog
------------ próxima parte ------------
Se ha borrado un adjunto en formato HTML...
URL: <https://mail.lacnic.net/pipermail/lacnog/attachments/20170809/7546ba3b/attachment-0001.html>
Más información sobre la lista de distribución LACNOG