Discuss mailing list

[Ladislav Laska <laska AT kam.mff.cuni.cz>]

Hi!

I've been experimenting with .bit names recently and noticed, that some of 
them 
are not resolved correctly by the opennic servers.

take, for example, vml.bit (a random, old domain):

{
        "name" : "d/vml",
        "value" : 
        
"{\"ip\":\"212.232.51.96\",\"map\":{\"*\":\"212.232.51.96\"},\"email\":\"namecoin AT mail.com\"}",
        "txid" : 
"f483a9506b26c2e64625b99985b11e6141d9bb88ce74d1430ebed3cfe05162c7",
        "address" : "NKqzXvXxbcHGasgw43kCfUNwW9oz9nXmHT",
        "expires_in" : 11523
}


but the opennic servers does not seem to know anything about it. I've tested 
with these servers:

2a03:f80:ed15:ed15:ed15:ed15:942f:94d0
2001:4ba0:cafe:383::1
109.69.8.34
185.16.40.143

Another non-opennic namecoin bridges resolve the name just fine (for example 
2a01:238:42e3:6400:653a:64a4:217c:7e10).

I've noticed, that a lot of these domains have the address 212.232.51.96 in
common, many others have 10.0.0.1.  I can accept, that the private range does 
not resolve (although it's arguable if it's a good practice), but the 
212.232.51.96 seems to be a bug. 

Could you please, explain this behaviuor, and possibly issue a fix, if it 
really 
is a bug? 

Thanks!


-- 
S pozdravem Ladislav Láska                          <laska AT kam.mff.cuni.cz>
Katedra Aplikované Matematiky, MFF UK               tel.: +420 739 464 167