Skip to main content
replaced http://networkengineering.stackexchange.com/ with https://networkengineering.stackexchange.com/
Source Link

I have always maintained that we should be polite, but firm with help vampires and trollstrolls.

I have always maintained that we should be polite, but firm with help vampires and trolls.

I have always maintained that we should be polite, but firm with help vampires and trolls.

replaced http://superuser.com/ with https://superuser.com/
Source Link

Taking the example of DNS... and setting aside my other arguments against DNS on NESE, one might argue that we don't have to make this an all DNS or no DNS site... sadly, I think it's really that black and white when we have so few close voters. It's a lot of work to suck enough details out of people for us to even know whether we can help them. DNS is one of those things that's going to be labor intensive to get documented well... especially from network newbs. On top of all that, many DNS servers are not in the direct control of the person with the problem; that means we can't help much besides telling them to talk to a network admin, or to call the company which operates the DNS server. In short, it's a lot of work with very little real value beyond what Super UserSuper User already provides.

Taking the example of DNS... and setting aside my other arguments against DNS on NESE, one might argue that we don't have to make this an all DNS or no DNS site... sadly, I think it's really that black and white when we have so few close voters. It's a lot of work to suck enough details out of people for us to even know whether we can help them. DNS is one of those things that's going to be labor intensive to get documented well... especially from network newbs. On top of all that, many DNS servers are not in the direct control of the person with the problem; that means we can't help much besides telling them to talk to a network admin, or to call the company which operates the DNS server. In short, it's a lot of work with very little real value beyond what Super User already provides.

Taking the example of DNS... and setting aside my other arguments against DNS on NESE, one might argue that we don't have to make this an all DNS or no DNS site... sadly, I think it's really that black and white when we have so few close voters. It's a lot of work to suck enough details out of people for us to even know whether we can help them. DNS is one of those things that's going to be labor intensive to get documented well... especially from network newbs. On top of all that, many DNS servers are not in the direct control of the person with the problem; that means we can't help much besides telling them to talk to a network admin, or to call the company which operates the DNS server. In short, it's a lot of work with very little real value beyond what Super User already provides.

replaced http://meta.networkengineering.stackexchange.com/ with https://networkengineering.meta.stackexchange.com/
Source Link

Taking the example of DNS... and setting aside my other arguments against DNS on NESE, one might argue that we don't have to make this an all DNS or no DNS site... sadly, I think it's really that black and white when we have so few close voters. It's a lot of work to suck enough details out of peoplesuck enough details out of people for us to even know whether we can help them. DNS is one of those things that's going to be labor intensive to get documented well... especially from network newbs. On top of all that, many DNS servers are not in the direct control of the person with the problem; that means we can't help much besides telling them to talk to a network admin, or to call the company which operates the DNS server. In short, it's a lot of work with very little real value beyond what Super User already provides.

Taking the example of DNS... and setting aside my other arguments against DNS on NESE, one might argue that we don't have to make this an all DNS or no DNS site... sadly, I think it's really that black and white when we have so few close voters. It's a lot of work to suck enough details out of people for us to even know whether we can help them. DNS is one of those things that's going to be labor intensive to get documented well... especially from network newbs. On top of all that, many DNS servers are not in the direct control of the person with the problem; that means we can't help much besides telling them to talk to a network admin, or to call the company which operates the DNS server. In short, it's a lot of work with very little real value beyond what Super User already provides.

Taking the example of DNS... and setting aside my other arguments against DNS on NESE, one might argue that we don't have to make this an all DNS or no DNS site... sadly, I think it's really that black and white when we have so few close voters. It's a lot of work to suck enough details out of people for us to even know whether we can help them. DNS is one of those things that's going to be labor intensive to get documented well... especially from network newbs. On top of all that, many DNS servers are not in the direct control of the person with the problem; that means we can't help much besides telling them to talk to a network admin, or to call the company which operates the DNS server. In short, it's a lot of work with very little real value beyond what Super User already provides.

added 69 characters in body
Source Link
Loading
added 470 characters in body
Source Link
Loading
added 139 characters in body
Source Link
Loading
added 693 characters in body
Source Link
Loading
added 118 characters in body
Source Link
Loading
added 470 characters in body
Source Link
Loading
Source Link
Loading