[npnog] Tweets about .NP being leaked!!

[Kabindra Shrestha]

Hello Gyanu dai,

> On Sep 23, 2017, at 7:15 AM, Gyanendra Mishra <gyanu at mercantile.com.np> wrote:
> 
> 
> Dear Kabindra,
> 
> It is from one of the Australia slave server which we do not have any contact of connect.com.au so it is good we will disable them from list by today.
> Ie Yakima and warana server of connect.com
Yes.

> We will disable and update.
Great :-).

.kabindra

> Thank You.
> Regards
> Gyanendra
> 
> Sent from my Samsung Galaxy smartphone.
> 
> -------- Original message --------
> From: Kabindra Shrestha via npnog <npnog at npnog.org>
> Date: 9/23/17 06:52 (GMT+05:45)
> To: npnog at npnog.org
> Subject: [npnog] Tweets about .NP being leaked!!
> 
> https://twitter.com/i/web/status/911352140580495360
> '"""
> Another day, another ccTLD leak: Nepal !
> (cc
> @IAmMandatory , Thanks again, root 'NP.' leak detected by TLDR project ;) )
> """
> 
> One of the nameserver for .NP is allowing zone transfers for all globally which isn't necessarily bad and is done on purpose but for .NP I am not sure if that is the case :-).
> 
> Interesting tweet from the same guy after analyzing .NP contents :)
> """
> Pretty weird root DNS structure, registrations of "*.np" are not allowed actually, but we have multiple domains in it (hello, beer.np).
> """
> 
> """
> np. -> 285 entries
> com.np. -> 82963 entries
> gov.np. -> 5762 entries
> mil.np. -> 35 entries
> net.np. -> 1548 entries
> org.np. -> 14656 entries
> """
> 
> I did inform about that server allowing zone transfer to .NP operator personally last time :-).
> 
> 
> .kabindra
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 495 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.npnog.org/pipermail/npnog/attachments/20170923/22fe99a0/attachment.sig>