Timeline for 3 votes to close on DNS and DNS Hijacking question?
Current License: CC BY-SA 3.0
16 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:14 | history | edited | CommunityBot |
replaced http://serverfault.com/ with https://serverfault.com/
|
|
| Mar 20, 2017 at 10:18 | history | edited | CommunityBot |
replaced http://superuser.com/ with https://superuser.com/
|
|
| Mar 17, 2017 at 10:46 | history | edited | CommunityBot |
replaced http://security.stackexchange.com/ with https://security.stackexchange.com/
|
|
| May 29, 2015 at 11:45 | comment | added | athena | I used HTTP, DNS, SMTP, OSPF, & BGP as just numbers among 65535 just as typical examples, and simply to remind the fact they are at the same position in the IP arena (IP is also a typical example :) ). | |
| May 28, 2015 at 15:07 | comment | added | YLearn Mod | If you think OSPF & BGP are all there is to networking, you have a lot to learn. Based on your comment, your assertion is that our site should now find every service that uses the network should be on topic as well. Good luck with that as answering questions about every service under the sun is not where I want to spend my limited free time. | |
| May 28, 2015 at 8:44 | comment | added | athena | If you eliminate HTTP/DNS/SMTP, what is a network working with? OSPF & BGP alone, just for the pleasure to exchanging nice routes? | |
| Mar 21, 2015 at 8:58 | history | edited | Mike Pennington | CC BY-SA 3.0 |
added 52 characters in body
|
| Mar 20, 2015 at 14:21 | comment | added | YLearn Mod | Maybe this will help clarfify the distinction. HTTP/DNS/SMTP are largely services used by client devices accessing the service on a server. They are not typically used by network devices (except for management in some cases), typically not hosted by network devices, and almost never used between network devices. They were designed to make it easier for end users to share/get information. OSPF on the other hand is a service that typically runs on network devices and is used almost exclusively by network devices. It was created to allow network devices to share information about the network. | |
| Mar 20, 2015 at 10:31 | comment | added | Eddie | That said, I acknowledge that what the Network Engineering Stack Exchange considers on or off topic is / has been decided by the community, and two prominent leaders (yourself and @MikePennington) have sufficiently confirmed where the community lands. I'm not trying to argue needlessly, or simply make a fuss out of an "emotional attachment to the subject". I just felt, as a member of this community, and in a 'community run' environment, its better for members to share there opinions on potential future directions. That is all. | |
| Mar 20, 2015 at 10:27 | comment | added | Eddie | OSPF is a service that shares routes. Yet, we consider that wholeheartedly on topic. I think the line would be drawn on what you mean to do with your answer. If your goal is to configure a HTTP/DNS/SMTP/etc server, then I would agree that is off topic. If your goal was to understand the traffic pattern, operation, maintenance and potential risks of those services, then I would look at that as a hosting/service provider question, which (at least in my opinion) falls within the "Network Engineering" realm. | |
| Mar 19, 2015 at 14:49 | comment | added | YLearn Mod | @Eddie, DNS is not a component of a network. It is a service, one that does make using a network easier, but a service for all that. In this way, it is no different from HTTP/HTTPS, SMTP, POP3, IMAP, FTP, etc. Should all of those be considered on topic as well? While many of us could probably answer any number of DNS/DHCP questions, there are more appropriate communities on the Stack Exchange network for the majoritty of these questions. | |
| Mar 19, 2015 at 2:46 | comment | added | Eddie | I see your point, but I don't think you would have needed to go into a graduate level understanding of each of those attack vectors. A simple bullet list (with a little more detail) would have been a great answer to their question. As for being on topic or not, frankly I had no idea DNS was not on topic... could you link me where that is defined? Because I would have imagined that DNS fell pretty squarely in the Network Engineering Stack Exchange. | |
| Mar 18, 2015 at 17:21 | comment | added | YLearn Mod | Aside from that, it is not on topic on this site. How would I have worded that question for it to be considered on topic? I would have asked it on the appropriate stack in the network where it is considered on topic by the community. | |
| Mar 18, 2015 at 17:18 | comment | added | YLearn Mod | The question "how does the DNS record get hijacked" is not very specific. Let's start a very brief overview of how DNS can get "hacked." The DNS server itself can be hacked. The DNS service on the server can be hacked. The resolving DNS server the client is using can be hacked. The DNS service on the resolving DNS server can be hacked. The client can be hacked. Any of a number of MitM attacks can be used. Each of the above could be accomplished in a number of different ways and each could easily be an answer unto itself making this a VERY broad question with no specific answer. | |
| Mar 18, 2015 at 7:44 | comment | added | Eddie | Had the question been "How was Lenovo hacked", I would have agreed with you. But he referred to a specific article that mentioned DNS, then asked his question specifically around how to hijack DNS records. That sounds pretty specific to me. Maybe he wasn't asking for the specific method Lenovo was hacked, but if he was, that probably also wouldn't be on topic, as that is an investigative journalist question, not a Network Engineering question. But please, indulge me... How, do you think he should (could?) have worded that question for it to be considered on topic? | |
| Mar 18, 2015 at 3:42 | history | answered | YLearnMod | CC BY-SA 3.0 |