1,621 karma · joined February 21, 2010
A common setup is a private nameserver that you host yourself, wherever, that isn't publicly used. You then contract UltraDNS/Neustar or their brethren and set them up as your public servers, doing zone transfers from your private ones. You get the advantages of direct management of your zones, and the global scale infrastructure needed to largely eliminate nameserver issues.
If they run additional business in hosting DNS, websites, email, and so on, as is common - that's really got nothing to do with the setup they need to act as a registrar.
Those changes, though, take time to cache out, and depending on your registrar's procedures and whatnot, you could be looking at hours or a couple of days to get things to stabilize back to normal; not to mention finding a new provider and getting things set up. You'll need ot make sure you have the zone data on hand ready to get set up with a new provider, and so on. You could have a procedure in place to do this, sure, with everything tested and validated, but at that point it's much easier to just have a DNS provider of the proper class who can handle these things for you. And keep in mind, if it's your domain they are trying to shut down, and not your DNS provider specifically, the attack will very likely just follow the change, leaving you in quite a mess.
So the short answer: self-host if it's not revenue impacting. If there is money at stake, spend a little bit for a top-notch provider.
The DNS service that is being attacked is the one they offer end users, usually along with domain registration. There is no particular reason you need to use their services when registering a domain with them, although, like most rigistrars, their website will make this deliberately confusing, and may require you to use their DNS service if you also want to use some of their other value-added services along with your registration (like email forwarding, websites, stuff like that).
Unless you are using other services from NetSol that require you to use their DNS, you are free to use whatever DNS infrastructure you like, including your own.
(If DDOS is a business concern, I'd go with someone big who deliberately does just DNS.. Neustar or one of those)
So during day to day business and life, you can call yourself whatever you want. Others can insist on identification if it's important to them, and that gets trickier.. but using a pen-name on a book or a hotel reservation is no different than using a fake name at starbucks while waiting for your coffee.
Forging documents is of course illegal, so that puts a crimp on things - but there is no particular reason that you are required to use your "real" name except when dealing with government documents (and things that rely on them)
What surprised me was this.
After using a quickstart toturial or two and diving right in, I was all happy that my dwarves had started doing, well, something, and I was getting used to it. I started collecting some materials, as the tutorial said, and I dug some stuff, as the tutorial said. Then I noticed the water in the map seemed ot have changed colour, and the ground, in all it's pixellated ascii glory, appeared whiter than it used to. "could it be winter, are there seasons?" I googled, letting the dwarves work. Yes, there was winter. Water froze. When I eventually got back to my game, there was a food shortage, and much worse, we ran out of liqour. We also had no water. The dwarves stopped working. Investigating their stats, they were rather angry about the situation. Eventually one, then two, went berzerk and killed their fellow dwarves in a rampage. I tried my best to guide them to gather some foliage so we could make some booze and get things back on track.. but I was too late. By spring, everyone was dead.
The next time.. I made it through winter, but not the next... overpopulation got me. With the immigrants that keep showing up, I had more and more dwarves, and I didn't know how to manage it. Hilarity ensued.. from a kobold thief stealing babies to animals mating in the bedroom to checking on the dining area to find a horse sitting at the table with a bunch of partying dwarves.
Eventually I made it a few seasons... only to be raided by goblins. I had no militia, I hadn't figured that part out yet. I hadn't needed it. Everyone died.
And so it goes...
The awesome part, and I think a critical thing most players who like the game clue in to, is that it's always like this. You won't get to a feeling of mastery where you can just hone your skills like most games. You'll always be analyzing what you see, looking stuff up, talking with others, and resolving yourself to try a new strategy next time - imagination really pays off here. There are always hippos in the sewers, or cats breeding out of control, or ant-people that want to eat you, or a berzerk dwarf baby killing his family, or some monster from down deep getting up your stairwell and terrorizing your fortress, or a magma accident, or a dwarf who decides to lock himself in a workshop, depriving you of that shop abilities while he spends his sweet time making stuff. There's dwarves that promte themselves to nobles and demand stuff, and they generally need to be dealt with. Usually by death. Dwarves must be sacrificed on on occasion for the good of the fortress.
My point, I guess, is that the funny/sad/epic stories you read about aren't really embellished much - the game actually provides you with that level of detail... even early-on. Your imagination fills in the blanks.. but there aren't many blanks.
We don't have to worry about the rocket fuel.. but those guys are in that tiny little space with the sub holding back 500 atmospheres of pressure outside. Holding in less than 1 atmosphere in a space-ship is easy. Holding back 5 kilometers of water sitting on top of you is hard.
That seems.. helpful?
You are a new startup. You are operating a closely related product to a large power player in the same business by choosing a nearly identical name. Now you are suggesting their data is so important to you that you are going to technically circumvent their block, potentially adding more legal liability, and use their service anyway? And calling them "assholes" in a public forum forum?
Does that seem at all sustainable to you?
I mean - is figuring out how to talk to a client over the phone somehow a stumbling block these days? Everyone has a phone, right? It's still an essential thing.
And if you mainly use Skype, you can just call with skype anyway... why would you go setting up some other weird phone service?
We will still need virtual machines for different operating systems, different versions of the same OS, multiple instances to span multiple VM hosts for scaling/redundancy, and so on.
Containers will cut down on the number of VMs we have to deploy within an organisation, nominally... it will be a more effective way to manage resources. VMs won't go away, or even be diminished.
Virtual Machines let us abstract away our hardware resources. They also made deploying new instances much easier than it was previously, so we started using more instances than we would ahve without it, just to provide configuration and resource separation.
The first part is still necessary - and we still need multiple instances to take advantage of multiple VM hosts when it comes to scaling and redundancy. The second part is what containers address.
I have a feeling we will end up mixing and matching the two as appropriate.
I disabled the pagefile completely, and things are as snappy as ever - I can't think of an application I use that would use up so much ram that I need to page to disk.
"Would you be comfortable with having a landlord’s management history posted on your listing?"
If we are talking about rental listings... if it's my listing, am I not the landlord?
This is potentially huge.
I suppose there is room for a service that notarizes (something like that, no offense meant to notaries!) messages before sending them in an otherwise very casual fashion, as well as records receipt in a somewhat official way could take it's place. There is still probably room for such a thing/
You don't have an API (for obvious reasons) into the poker clients, so you have software that basically reads the screen as an image and works the keyboard/mouse.... the more sophisticated ones do it in a VM to avoid detection (some poker software actively scans your machine for known bot software or other tampering)
You'll go from feeling fine to acute pain to very dangerous damage pretty much momentarily.