How do I handle this? DDOS?
-
Well - I'm sure there are times when, for security reasons, running your own private DNS server is a good thing.
But other than that, I agree.
-
-
"for security reasons, running your own private DNS server is a good thing."
Can you give an example?? These are names that you want the WORLD to resolve..What security could you be worried about.. What you want is HA, Speed.. Do you have dns around the globe? Do you have anycast setup? Who do you think pays more attention to security concerns with dns than hosts that provide dns for a shitload of customers??
Other than local dns, I can not see a point to host your own.. Its sure and the hell not cost effective!! And your never going to be able to do it as good as the hosts can..
I love dns, would love more than nothing to host it to the public - it just doesn't make sense to do so!!
-
If everyone said that, then no host would be found… ;)
-
I think there are just times when its good for certain business, organizations etc to control how their DNS gets resolved.
Lots of DNS servers out there, so apparently I'm not alone.
-
Because they don't think it through would be my take on why so many.. Hosting with dns company X does not take away how anything is resolved.. It gives you better infrastructure to host your data is all. You know what the cost would be to have servers around the globe with anycast, etc..
Why should I set that up, pay for it, manage it.. When it comes down to it all I am worried about is that www.something.tld points to the IP I want it too.. The hardware, the location, the software that is done on is really nothing to do with what you need for your public dns.
You want www.something.tld to resolve to an IP, you want it to do it quickly from anywhere on the planet - you want it to do it always do it 99.999% You don't want some script kiddy hit your dns with a shit lot of queries and take down normal users being able to resolve it. You want to be able to change www.something.tld to resolve to different IP when you want, etc..
All of these things is what dns hosting companies do for a living.. That you think your company that does Y for a living should host dns to the public X is just crazy.. Do the math, it just make no sense to host your own public dns.. You can not come close to feature set, reliability, etc. And your going to spend more doing it..
Just my take on it - Do you really think the big companies host their own? Sorry they do not, its not cost effective!! And the same can be said if you have 1 domain that gets 10 queries a day or 10 million..
To the OP.. What do you think your getting by hosting public dns on your own stuff?? Other than problem like this! ;)
-
You could pretty much use that logic for any service. No need to run any yourself because others are doing it better already.
-
You could pretty much use that logic for any service. No need to run any yourself because others are doing it better already.
I think his main point is that DNS has a high risk for low reward, and there's a lot of competition, so the prices are hard to beat compared to finding the talent and training your staff. Not to mention the large infrastructure investment required to do it "correctly".
DNS is also critical infrastructure. Your web app not working is fine, because you can return an HTTP error, but DNS not working is like your Internet link going down.
-
I manage our DNS. We have two Linux VMs that I use with BIND for primary and secondary resolution. I like the flexibility and control that having it local gives me. I don't need global octo mega multicasting. If our DNS is down then it's pretty likely that we're totally down.
-
@KOM:
I manage our DNS. We have two Linux VMs that I use with BIND for primary and secondary resolution. I like the flexibility and control that having it local gives me. I don't need global octo mega multicasting. If our DNS is down then it's pretty likely that we're totally down.
Of course they have you over there, so they have the talent :-) But how many companies really have people who know how things really work? I've met quite a few people who are in charge of very important things, but only know what they've been told with no understanding of how things work.
I could see it being a good rule of thumb to recommend people purchase DNS services than self host. I have little experience in this, so I'm only appreciating the arguments, but I have no experience, but I read enough security articles about how whatever common service is misconfigured on 80% of servers.
-
So in the same geographic location, prob even same network I take it? Yeah not something I would call robust HA sort of setup ;)
Small dns setups can be hosted for FREE or like $29 a year. While it sounds like your just leveraging spare cycles on your VM infrastructure and most likely free linux distros so cost is very low.
From your very knowledgeable posts on all sorts of topics, I take it your very familiar with the subject and you have chosen this route because of your familiarity with the service and how to host it, etc… Also from your past posts I am fairly sure you would know how to handle an attack against the service, and or how to harden the setup against such attacks in the first place..
Not all companies IT personal have such skillsets. You see it all the time where full recursion is allowed on public facing dns that is suppose to be authoritative for 1 or 2 domains.
-
Part of the issue (for me, at least) is that I manage 230+ domains for just the one company (don't ask or you will make me scream again. Hint: executive buzzword bingo as applied to domains…). I've used some domain registrar's DNS tools and they were painful and slow. I couldn't imagine using them to actually deal with hundreds of domains. Give me WinSCP and root credentials and I will happily manage DNS at the filesystem level, thank you very much.
-
@KOM:
Part of the issue (for me, at least) is that I manage 230+ domains for just the one company (don't ask or you will make me scream again. Hint: executive buzzword bingo as applied to domains…). I've used some domain registrar's DNS tools and they were painful and slow. I couldn't imagine using them to actually deal with hundreds of domains. Give me WinSCP and root credentials and I will happily manage DNS at the filesystem level, thank you very much.
Uh. Normally you get some kind of API access for similar amount of domains from quite a couple of registrars here… (No clicking over web forms.)
