[bdNOG] Reverse delegation problem with 144/8 prefixes

Anurag Bhatia me at anuragbhatia.com
Mon May 9 05:59:30 BDT 2016


Hi Moinur



Yeah it seems like an issue.


% Information related to '144.48.0.0/24AS135311'

route:          144.48.0.0/24
descr:          Golam Mohammad T/A 29Communication
origin:         AS135311
mnt-by:         MAINT-M29COMMUNICATION2-BD
changed:        admin at 29com.net 20160412
source:         APNIC

% This query was served by the APNIC Whois Service version 1.69.1-APNICv1r0
(UNDEFINED)


Confirms that pool is with AS135311 in Bangladesh while
0.48.144.in-addr.arpa doesn't seem to be a valid zone.

dig 0.48.144.in-addr.arpa. ns |grep status
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 46569





The entire 144.in-addr.arpa seems to be delegated to ARIN.



;; QUESTION SECTION:
;48.144.in-addr.arpa. IN NS

;; AUTHORITY SECTION:
144.in-addr.arpa. 21414 IN NS r.arin.net.
144.in-addr.arpa. 21414 IN NS arin.authdns.ripe.net.
144.in-addr.arpa. 21414 IN NS z.arin.net.
144.in-addr.arpa. 21414 IN NS u.arin.net.
144.in-addr.arpa. 21414 IN NS y.arin.net.
144.in-addr.arpa. 21414 IN NS x.arin.net.




Probably someone from APNIC could check on this zone delegation.



Thanks.

On Mon, May 9, 2016 at 12:12 AM, Muhammad Moinur Rahman <5u623l20 at gmail.com>
wrote:

> Hi Everyone,
>
> Anyone facing problem with 144/8 prefixes reverse delegation in APNIC
> region. Whenever I am trying to query; the query is forwarded to ARIN
> rather than APNIC. It seems a problem in the root servers.
>
> bofh at BOFH-MBP:~ % dig -x 144.48.0.0
>
> ; <<>> DiG 9.8.3-P1 <<>> -x 144.48.0.0
>
> ;; global options: +cmd
>
> ;; Got answer:
>
> ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 30447
>
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
>
>
> ;; QUESTION SECTION:
>
> ;0.0.48.144.in-addr.arpa. IN PTR
>
>
> ;; AUTHORITY SECTION:
>
> 144.in-addr.arpa. 10800 IN SOA z.arin.net. dns-ops.arin.net. 2016031549
> 1800 900 691200 10800
>
>
> ;; Query time: 90 msec
>
> ;; SERVER: 192.168.43.1#53(192.168.43.1)
>
> ;; WHEN: Mon May  9 00:25:32 2016
>
> ;; MSG SIZE  rcvd: 95
>
>
> bofh at BOFH-MBP:~ % dig -x 144.48.0.0 +trace
>
>
> ; <<>> DiG 9.8.3-P1 <<>> -x 144.48.0.0 +trace
>
> ;; global options: +cmd
>
> . 362847 IN NS g.root-servers.net.
>
> . 362847 IN NS d.root-servers.net.
>
> . 362847 IN NS m.root-servers.net.
>
> . 362847 IN NS c.root-servers.net.
>
> . 362847 IN NS h.root-servers.net.
>
> . 362847 IN NS a.root-servers.net.
>
> . 362847 IN NS j.root-servers.net.
>
> . 362847 IN NS k.root-servers.net.
>
> . 362847 IN NS e.root-servers.net.
>
> . 362847 IN NS l.root-servers.net.
>
> . 362847 IN NS i.root-servers.net.
>
> . 362847 IN NS f.root-servers.net.
>
> . 362847 IN NS b.root-servers.net.
>
> ;; Received 496 bytes from 192.168.43.1#53(192.168.43.1) in 58 ms
>
>
> in-addr.arpa. 172800 IN NS a.in-addr-servers.arpa.
>
> in-addr.arpa. 172800 IN NS b.in-addr-servers.arpa.
>
> in-addr.arpa. 172800 IN NS c.in-addr-servers.arpa.
>
> in-addr.arpa. 172800 IN NS d.in-addr-servers.arpa.
>
> in-addr.arpa. 172800 IN NS e.in-addr-servers.arpa.
>
> in-addr.arpa. 172800 IN NS f.in-addr-servers.arpa.
>
> ;; Received 417 bytes from 192.203.230.10#53(192.203.230.10) in 56 ms
>
>
> 144.in-addr.arpa. 86400 IN NS z.arin.net.
>
> 144.in-addr.arpa. 86400 IN NS u.arin.net.
>
> 144.in-addr.arpa. 86400 IN NS arin.authdns.ripe.net.
>
> 144.in-addr.arpa. 86400 IN NS r.arin.net.
>
> 144.in-addr.arpa. 86400 IN NS y.arin.net.
>
> 144.in-addr.arpa. 86400 IN NS x.arin.net.
>
> ;; Received 161 bytes from 193.0.9.1#53(193.0.9.1) in 339 ms
>
>
> 144.in-addr.arpa. 10800 IN SOA z.arin.net. dns-ops.arin.net. 2016031549
> 1800 900 691200 10800
>
> ;; Received 95 bytes from 204.61.216.50#53(204.61.216.50) in 40 ms
>
>
> bofh at BOFH-MBP:~ % whois -A 144.48.0.0
>
> % [whois.apnic.net]
>
> % Whois data copyright terms    http://www.apnic.net/db/dbcopyright.html
>
>
> % Information related to '144.48.0.0 - 144.48.3.255'
>
>
> inetnum:        144.48.0.0 - 144.48.3.255
>
> netname:        M29COMMUNICATION2-BD
>
> descr:          Golam Mohammad T/A 29Communication
>
> descr:          12/C, 8/1, Mirpur, Pallabi Dhaka-1216 Bangladesh
>
> country:        BD
>
> admin-c:        RA550-AP
>
> tech-c:         RA550-AP
>
> status:         ALLOCATED PORTABLE
>
> mnt-by:         APNIC-HM
>
> mnt-lower:      MAINT-M29COMMUNICATION2-BD
>
> mnt-routes:     MAINT-M29COMMUNICATION2-BD
>
> mnt-irt:        IRT-M29COMMUNICATION2-BD
>
> remarks:        --------------------------------------------------------
>
> remarks:        To report network abuse, please contact mnt-irt
>
> remarks:        For troubleshooting, please contact tech-c and admin-c
>
> remarks:        Report invalid contact via www.apnic.net/invalidcontact
>
> remarks:        --------------------------------------------------------
>
> changed:        hm-changed at apnic.net 20160406
>
> source:         APNIC
>
>
> irt:            IRT-M29COMMUNICATION2-BD
>
> address:        12/C, 8/1, Mirpur, Pallabi Dhaka-1216 Bangladesh, DHAKA
> MIRPUR 1216
>
> e-mail:         admin at 29com.net
>
> abuse-mailbox:  admin at 29com.net
>
> admin-c:        RA550-AP
>
> tech-c:         RA550-AP
>
> auth:           # Filtered
>
> mnt-by:         MAINT-M29COMMUNICATION2-BD
>
> changed:        hm-changed at apnic.net 20160405
>
> source:         APNIC
>
>
> role:           R29Communication administrator
>
> address:        12/C, 8/1, Mirpur, Pallabi Dhaka-1216 Bangladesh, DHAKA
> MIRPUR 1216
>
> country:        BD
>
> phone:          +8801552398917
>
> fax-no:         +8801552398917
>
> e-mail:         admin at 29com.net
>
> admin-c:        RA550-AP
>
> tech-c:         RA550-AP
>
> nic-hdl:        RA550-AP
>
> mnt-by:         MAINT-M29COMMUNICATION2-BD
>
> changed:        hm-changed at apnic.net 20160405
>
> source:         APNIC
>
>
> % Information related to '144.48.0.0/24AS135311'
>
>
> route:          144.48.0.0/24
>
> descr:          Golam Mohammad T/A 29Communication
>
> origin:         AS135311
>
> mnt-by:         MAINT-M29COMMUNICATION2-BD
>
> changed:        admin at 29com.net 20160412
>
> source:         APNIC
>
>
> % This query was served by the APNIC Whois Service version
> 1.69.1-APNICv1r0 (UNDEFINED)
>
> ​The source is from APNIC. Hence APNIC nameservers should be noted in the
> root Servers. I have checked some other prefixes ​and each one is producing
> the same results.
>
> ​Anyone have a clue?​
>
>
> Best Regards,
> Moin
>
> _______________________________________________
> nog mailing list
> nog at bdnog.org
> http://mailman.bdnog.org/mailman/listinfo/nog
>
>


-- 


Anurag Bhatia
anuragbhatia.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.bdnog.org/pipermail/nog/attachments/20160509/c5457b64/attachment-0001.html>


More information about the nog mailing list