News for hackers. Stuff that matters.

A comment on DNSimple DDOS Attack. Parent comment

Re:DNSimple DDOS Attack by joshdotsmith on Monday December 01, 2014 @05:51PM (#8684535)
Will these services not have the same thin pipe issue that's currently affecting DNSimple?
[ Parent | on HN ]
Re:DNSimple DDOS Attack by dentarg on Monday December 01, 2014 @06:07PM (#8684632)
Not that I have any reliable info, but what I've heard, DNS Made Easy is a pretty stable and established DNS provider.

They brag about "99.9999% uptime history" at http://www.dnsmadeeasy.com/technology/.

Though they doesn't seem as innovative and nice as DNSimple. Really hope things work out for DNSimple (really like the idea of their beta feature GitHub sync).

[ Parent | on HN ]
Re:DNSimple DDOS Attack by stevekemp on Monday December 01, 2014 @06:51PM (#8684878)
How does their beta-feature with github work? I can't find any obvious link and it seems frustratingly close to something I offer over at https://dns-api.com/ ..

(I wrap Amazon's route53 with DNS entries read from github/gitbucket/similar.)

[ Parent | on HN ]
Re:DNSimple DDOS Attack by zuccs on Monday December 01, 2014 @10:54PM (#8685621)
And link to their Git support is here: http://support.dnsimple.com/articles/github-sync/ (if only DNS wasn't down..)
[ Parent | on HN ]
Re:DNSimple DDOS Attack by stevekemp on Tuesday December 02, 2014 @03:16AM (#8686204)
Interesting thanks.

An interesting/custom choice to use JSON, and real github integration rather than using hooks as I did.

[ Parent | on HN ]
Re:DNSimple DDOS Attack by zuccs on Monday December 01, 2014 @10:24PM (#8685528)
Can you use custom nameservers with your service?
[ Parent | on HN ]
Re:DNSimple DDOS Attack by EwanToo on Tuesday December 02, 2014 @04:46AM (#8686385)
AWS Route 53 has added vanity DNS in the last few weeks, so you can make your DNS servers appear to be ns0.yourdomain.com rather than ns153.awsdomain.com (or whatever)

However, making your DNS servers to be responsible for serving their own DNS is a bit of an extra complexity and risk that no customer will ever care about..

[ Parent | on HN ]
Re:DNSimple DDOS Attack by zuccs on Tuesday December 02, 2014 @05:45PM (#8690551)
Nice. Got a link for this one?
[ Parent | on HN ]
Re:DNSimple DDOS Attack by EwanToo on Wednesday December 03, 2014 @03:49AM (#8692565)
It was oddly snuck into the private DNS announcement

http://aws.amazon.com/blogs/aws/route-53-update-private-dns-...

"You can create generic "white label" name servers such as ns1.example.com and ns2.example.com, use them in your delegation set, and point them to your actual Route 53 name servers."

[ Parent | on HN ]
Re:DNSimple DDOS Attack by stevekemp on Tuesday December 02, 2014 @03:15AM (#8686199)
When you upload a new zone it will be assigned a set of nameservers - four. You can't choose what they are in advance, and you can't specify the TLDs. So you might end up with "ns-1933.awsdns-49.co.uk.", "ns-1109.awsdns-10.org.", or similar.

Does that answer the question? I'm a little hazy on what you're actually asking.

[ Parent | on HN ]
Re:DNSimple DDOS Attack by toomuchtodo on Monday December 01, 2014 @11:24PM (#8685703)
Old DnsMadeEasy customer here (used them for several years before moving to AWS). They were rock solid. We used them for hosting DNS for major cruise lines (fancy, very fancy ones), as well as other large Fortune 500 clients.

Their interface is pretty bad, but the backend is hardy.

[ Parent | on HN ]
Re:DNSimple DDOS Attack by EwanToo on Tuesday December 02, 2014 @04:51AM (#8686396)
It's unlikely, DNSimple appear to have relied on a single network provider and a limited number of name servers.

If I do a traceroute to the 5 DNSMadeEasy name server records (they actually run many more hosts) I go via 3 different networks - GTT, NTT, and Tata.

[ Parent | on HN ]