Reputation
347
Top tag
Next privilege 500 Rep.
Access review queues
Badges
2 10
Impact
~32k people reached

  • 0 posts edited
  • 0 helpful flags
  • 2 votes cast
Jan
30
revised Windows 2008 R2 Shares Disappear on Reboot
added 355 characters in body
Jan
30
answered Windows 2008 R2 Shares Disappear on Reboot
Jan
30
comment Windows 2008 R2 Shares Disappear on Reboot
I've already made my life a LITTLE easier by figuring out that yes, I can simply restart the Server service rather than re-share all the folders. Now I still need to figure out what service the Server service can depend on to avoid even having to do that.
Jan
30
comment Windows 2008 R2 Shares Disappear on Reboot
If the issue WERE iSCSI related, the fix would be to have the Server service depend upon the iSCSI initiator service. So is there a service that is responsible for the FireWire connection, on which I could make the Server service depend?
Jan
30
asked Windows 2008 R2 Shares Disappear on Reboot
Dec
11
comment problems with opendkim and postfix centos
Holy Necropost, Batman! :) What have I still not done that's not good? If it's "Creating the Reader's Digest" version of the instructions... first, I said I'd do that "moving forward." Second, there are no condensed version of THOSE instructions, as that process requires a lot of steps. Also, DomainKeys is outdated, and shouldn't be used. The NEW condensed version is simply "yum install opendkim" The updated package (I'm the Fedora packager) has made a lot of progress since 2011. :)
Aug
11
awarded  Popular Question
May
24
awarded  Yearling
Apr
23
awarded  Popular Question
Jul
11
awarded  Notable Question
Jun
26
awarded  Popular Question
Jul
5
awarded  Popular Question
Jun
5
awarded  Commentator
Jun
5
comment Why don't my server query the 2nd entry in my resolv.conf?
Our local resolver does work, does perform recursive lookups, and does cache the results. However, when I run namebench to compare the speed of a large number of lookups, the public DNS server outperforms it every time, as it already has a number of queries cached. The catch is, as you say, "lower latency responses after resolved domain names are cached." It's the "after they're cached" part that is causing the issue. Most of the domain lookups from our servers are first time lookups. That's why I'm (still) looking for a way to autoquery a 2nd DNS server after failing to resolve on the 1st.
Jun
5
accepted Why don't my server query the 2nd entry in my resolv.conf?
Jun
5
comment Why don't my server query the 2nd entry in my resolv.conf?
Thanks, Daniel. This answers the question (and I will mark it as such). Do you know of a way to get the functionality I'm looking for? If nameserver #1 doesn't time out, but doesn't resolve, to query a subsequent nameserver?
Jun
5
comment Why don't my server query the 2nd entry in my resolv.conf?
It's not that the local DNS server is "too slow," it's that it's slower than the remote one based on a namebench test. It works, but I want things to work faster. :)
Jun
4
asked Why don't my server query the 2nd entry in my resolv.conf?
Dec
24
comment How do I configure iptables in DD-WRT to block Skype on br1 only?
Great, Michael. That makes sense... AND works. :) Thanks and Merry Christmas!
Dec
24
accepted How do I configure iptables in DD-WRT to block Skype on br1 only?