VeriSign Shutting Down Site Finder
00420 writes "VeriSign, the administrator of the .com and .net domains, made plans to shut down its new Site Finder service Friday, after the Internet Corporation for Assigned Names and Numbers ordered the company to undo controversial changes. Of course they're not taking it down because it affected the internet, they're just doing it to keep good relations with the technical community. (Seems a little late for that doesn't it?)" The shutdown is not complete yet, though: VeriSign hasn't changed their wildcard DNS entry (64.94.110.11).
Sir,
The Reynolds people called your shipment of hats is in.
Slashdot, where armchair scientists get shouted down and armchair theologians get modded up.
Odd though considering when some hardcore networking stuff needs to be assessed you will often see many *NOT* configure it then bitch about it somewhere down the line. I take many of those post and /dev/null them since there are a lot of whiners there, but I do enjoy reading the hardcore technical stuff when they're not trolling around about something trivial.
Hrmm now I know this post is not related to the story in general, and more than likely will be troll -1'd or something... But had to speak my mind about trusting information from anyone other source than RTFM for yourself.
They've also got a huge antiWindows theme going at times, which is funny because when I wrote brat.c the same people who were bitching about Windows were going to read the write up and program in ... Windows... Talk about 'Egos Gone Wild"
MoFscker
Sorry, but we already knew it - we have seen how George W. Bush was non-elected.
Not true. He was elected by a majority. Of 9.
Heh, try being a systems admin or a network admin for a while, then you'll realize where that attitude comes from.
Basically, we're doing maintenance jobs, with an occasional upgrade. If we're doing our jobs right, the maintenance will be very minimal - and we'll look like we're lazy. If we have to work on something, it's either for a good reason (security patch), or because we got *too* lazy before and didn't do the maintenance right.
apparently you must think you're the only sysadmin. FYI I've done Sr Sys Admin'ing/Network Engineering, Network Adminstration, Security Engineering, Sec. Administration. What do you call a massive patch update? I've seen people rant on about that. Configuring SNMP when it was broken? Oh my god the crying that went on. Listen, currently I work at a mid sized ISP, throw up a new router, welp there goes who knows how many clec updates throughout the lata's. Domain changes, welp there go some named changes, oh man user wants Apache to do what? There goes some module configurations. Fuck vuln in $MISCBINARY fuck gotta go update 600+ machines... Spare me the pseudo justification of the lazy admins.
FYI when I need to do something host specific that's going to take 16+ hours, I don't whine because it's my job. I spend a little time writing expect +python scripts to fix shit. Sol admin? jumpstart shit left and right... It's what I get paid for not to whine like some eleventeen YO juvenile.
MoFscker
Heh, guess we live in different worlds. I do what I can (preventative maint, pre-built update packages, etc.) to make sure I don't have to do very many 16+ hour days, regardless of how many 600 machines we have (yep, us too). Then again I've always been salaried, I might work different if I got overtime for it. :-) :-)
Right - and managed to get 100% of the African American Vote.
"It is our blasphemy which has made us great, and will sustain us, and which the gods secretly admire in us." - Zelazny