beevek

7 ms·

1.
by beevek 5y ago
Today's news from NS1 on NetBox: NetBox Cloud - https://techcrunch.com/2021/08/24/ns1-brings-open-source-net...
2.
by beevek 10y ago
Is there a way for teams with production Docker deployments to easily experiment with this kind of scanning on their own infra to understand their own situation? Maybe worth writing up a quick description of how operators can do something
3.
by beevek 11y ago
read part 1? ;)
4.
by beevek 12y ago
We are using Grafana with OpenTSDB and loving it -- really looking forward to some of the 2.0 features and about to buy a bunch more TVs for big shiny Grafana dashboards in our NOC. Way to go guys!
5.
by beevek 12y ago
they are essentially the same thing -- both are "proprietary" names for the same feature, which is behind-the-scenes recursive CNAME chain lookups by the authoritative nameserver, to return A records directly.
6.
by beevek 12y ago
you're correct about ALIAS (although practically, it doesn't matter: people are going to use the apex whether it's proper or not at this point). i'm more referring to other complex usually-proprietary capabilities of bi
7.
by beevek 12y ago
http://blog.cloudflare.com/introducing-cname-flattening-rfc-... is a reasonable explanation. fundamentally a CNAME says "when you get queries for this name, go look at this other name instead". among other thing
8.
by beevek 12y ago
good luck finding any major online property or infrastructure that isn't making use of some kind of proprietary syntactical dns sugar. it doesn't mean you can't span providers, but it does mean it takes a lot more work to do
9.
by beevek 12y ago
hi. i did not mean to spam or kick dnsimple, we know them and they are a great company and service. we are actively receiving inbound queries about this from folks asking for help, so thought it made sense to chime in publicly here. but
10.
by beevek 12y ago
dns is less easily distributed when fancy features like ALIAS (which dnsimple is widely known for) are in the mix. and wide distribution isn't enough to win vs truly volumetric attacks. it takes a lot of ports and compute to absorb 1
11.
by beevek 12y ago
Most of the time we don't actually operate switches of our own, and our setup is simple enough where we don't do a ton of automation around the config where we do. What we do automate end-to-end is our BGP: our prefixes are actua
12.
by beevek 12y ago
A simple example might help. Imagine you have a node in California and a node in NY, and a user in NJ. Let's assume for now that geographic proximity is actually a good arbiter for performance. If we make a bad routing decision and
13.
by beevek 12y ago
Certainly a huge drop-off. There is a lot of noise out there -- a lot of "resolvers" doing very few queries, whether because they have very few users, or because they're one-off special purpose resolvers. Vast majority of the
14.
by beevek 12y ago
Er -- I should have said, that did more than 10 queries from among our sample.
15.
by beevek 12y ago
Hi -- glad you like the post. /32s are individual DNS resolver IPs we observed in each country from among the sample we took (half a percent of the traffic we saw during a 24h period). The >10Q column is how many of those resolvers
16.
by beevek 12y ago
Kris here. Thanks Chris for putting this together, it was a really fun set of questions. I think a lot of what makes NSONE different is the philosophy behind the tech. We're not a DNS company, we're a traffic management company an
17.
Not Your Mother’s DNS: Unique NSONE Algorithms Give Users More Traffic Control(thewhir.com)
3 points by beevek 12y ago|0 comments
18.
by beevek 12y ago
Disclosure: I work for NSONE. At 2M queries/mo our list pricing is $8 ( https://nsone.net/support/billing/ ). Indeed our Biz Plan is $200 -- but that includes 24/7 support, 25M queries, and other bells &a