Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

This smells like BS, this also isn't the first time that other entities have had to step in to cleanup their crap.

Especially this quote: "Apparently, the Microsoft infrastructure is not able to handle the billions of queries from our customers."

Azure DNS, Microsoft.com, Bing. Yeah, all of those already require billions of DNS queries. I don't doubt things are not working correctly, but insinuating Microsoft can't handle the load just makes their case smell even worse.



Not really. It looks like these domains are hosted on a different platform.

$ host ns1.microsoftinternetsafety.net

ns1.microsoftinternetsafety.net has address 199.2.137.250

$ host ns1.msft.net

ns1.msft.net has address 65.55.37.62

ns1.msft.net has IPv6 address 2a01:111:2005::1:1

$


I think what is insinuated is that they botched the job, not that they're not technically capable of doing it.


I can agree with the fact they probably botched it (potentially on purpose), but the way it's articulated in the No-IP reply leaves little ambiguity that it was intended as an attack on their technical capability.

I am not in love with what Microsoft did here but No-IP is not doing the best job of defending their position.


Try and query anything.no-ip.biz. At the moment, I'm getting regular timeouts on queries to both ns7.microsoftinternetsafety.net and ns8.microsoftinternetsafety.net. It shouldn't take much for microsoft to log all incoming dns requests and put in an NS record to let traffic continue flowing down to no-ip's actual nameservers. A simple `dig whatever.no-ip.biz @a.root-servers.net +trace` will show you this.


My paid No-IP domains actually went offline. Now I know the reason … what's a recommendable No-IP alternative broadly supported by routers?


DynDNS are fairly good, if you're looking for a paid service.


Thanks!




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: