You're an idiot, who cares what you're talking about if you're trying to divert the thread?
Sorry I did not know you are that important that you can't back up(or need to) what you say. My mistake. Carry on.
Can you not be an idiot? This thread is not about the government. It's about a contract between a business and a customer of theirs. I've backed up what I said. Network Solutions stated the reason they dropped stormfront.com. I posted their position. I posted Network Solutions' Acceptable Use Policy to demonstrate where stormfront.com violated that agreement. So who knows what you think I didn't back up?
[
Can you not be an idiot? This thread is not about the government. It's about a contract between a business and a customer of theirs. I've backed up what I said. Network Solutions stated the reason they dropped stormfront.com. I posted their position. I posted Network Solutions' Acceptable Use Policy to demonstrate where stormfront.com violated that agreement. So who knows what you think I didn't back up?
Don't be so ******* stupid. Network Solutions does not have a policy of saying no to white nationalists.[
Can you not be an idiot? This thread is not about the government. It's about a contract between a business and a customer of theirs. I've backed up what I said. Network Solutions stated the reason they dropped stormfront.com. I posted their position. I posted Network Solutions' Acceptable Use Policy to demonstrate where stormfront.com violated that agreement. So who knows what you think I didn't back up?
Yes. Network solutions has a policy saying no service for white nationalists and bakers have a policy of no service for queers. Why is one ok but the other isn't.?
Repeal, Declare unconstitutional and trash the law is the same thing. If you want to get wrapped up in technicalities because of your limited brain power then go ahead.
OK so now youre claiming you invented the internet before it was invented yet your posting something as mundane as what a host file does and what the DNS protocol does.i think I'll trust my 20 plus years in the Network engineering and VoIP Collaboration field over your obvious lack of knowledge on the subject.Its obvious you dont realize that even the satellite companies have a network that connects by physical means to the internet. I didnt bother reading the rest of your post except the end because its so obvious you dont know what you are talking about. Its funny you listed how to edit a Linux/Unix host file. The IP that its pointing at is a physical piece of hardware eventually.only reachable by physical means. That little work around you listed doesnt circumvent the internet. Its used only for local resolution. It tells that computer in order to reach the URL of stormfront that it needs to point to that new IP. it cant control what routers will do with the traffic on the internet. If the organizations that own those means cuts them off they cant do anything. You cant even exist on the internet without the permission of IANA who ultimately gives out public IP addresses even though its now delegated to ARIN. Where do you think stormfront gets its IP address from? You dont just get to make up your IP address. Its assigned.
Have at you and continue to think you're smart when you're in the wrong
I've got a few years on ya pup. I built my first public network server before the internet really even existed. You're wrapped up in your little world of cables and routers at the bottom "private" tier (aka network engineering and creating private LANS), and not listening to what I'm telling you about the non-physical side being what actually directs the flow of traffic on the internet itself. Look around the internet and you'll save yourself the embarrassment. I mean seriously, you just used video phone calls as a "knowledge reference" for how the internet works son... Please. The network engineer part is slightly more impressive sounding at least. Either way, your job experience has little to nothing to do with the resolution of domain names on the internet; and if you actually have such experience under your belt you damn well know it. Still, I'll give you the benefit of the doubt because I do so enjoy geeking out with a fellow computer nerd, even if the nerd in question is attempting to bullshit a crowd.
Perhaps missed the day(s) where they taught about the function of the hosts file and it's automated replacement [for the internet] by the DNS system in the 80s. Here's a quick refresher course (relevance emphasis added):
hosts (file) - Wikipedia - "The computer file hosts is an operating system file that maps hostnames to IP addresses. It is a plain text file. Originally a file named HOSTS.TXT was manually maintained and made available via file sharing by Stanford Research Institute for the ARPANET membership, containing the hostnames and address of hosts as contributed for inclusion by member organizations. The Domain Name System, first described in 1983 and implemented in 1984, automated the publication process and provided instantaneous and dynamic hostname resolution in the rapidly growing network. In modern operating systems, the hosts file remains an alternative name resolution mechanism, configurable often as part of facilities such as the Name Service Switch as either the primary method or as a fallback method."
Hostname - Wikipedia - "In computer networking, a hostname (archaically nodename) is a label that is assigned to a device connected to a computer network and that is used to identify the device in various forms of electronic communication, such as the World Wide Web. Hostnames may be simple names consisting of a single word or phrase, or they may be structured."
IP address - Wikipedia - "An Internet Protocol address (IP address) is a numerical label assigned to each device connected to a computer network that uses the Internet Protocol for communication. An IP address serves two principal functions: host or network interface identification and location addressing."
DNS Name Resolution - "DNS name resolution is nothing but resolving host names, such as www.nixcraft.com, to their corresponding IP addresses. DNS works as the “phone book” for the Internet by translating hostname into IP address or vise versa. Most DNS server stores following information:
a) Hostname and their IP address
b) List of mail server and their IP address for given domain name
c) Anti spam configuration and much more.
Without DNS name resolution, nothing will work on the Internet. Nobody likes to remember IP address, so DNS is foundation of many Internet services such as web, proxy, email and so on."
Domain Name System (DNS) - "The DNS enables domain names to stay constant while the underlying network topology and IP addresses change. This provides stability at the application level while enabling network applications to find and communicate with each other using the Internet protocol no matter how the underlying physical network changes."
^^ And it is that last bit right there that you get fucked up on. The physical network has no impact on the routing to websites - that is the realm of DNS. It is also why Stormfront users can still access their server, despite their domain name being jacked - because the site /still/ exits on the physical web and still has an IP address that ANYONE can access simply by changing their hosts file to resolve "stormfront.com" to the relevant IP address of the site; DNS registrar Network Solutions is completely /unneeded/ in the process - they can be bypassed simply and easily. Which is exactly how one would start an internet 2.0, create new DNS registrar - just as one would do with HOSTS file and boom! new IP address to domain name resolution.
See also how this would be implemented on the "client" side - How to Bypass OpenDNS Internet Security
OK so now youre claiming you invented the internet before it was invented yet your posting something as mundane as what a host file does and what the DNS protocol does.i think I'll trust my 20 plus years in the Network engineering and VoIP Collaboration field over your obvious lack of knowledge on the subject.Its obvious you dont realize that even the satellite companies have a network that connects by physical means to the internet. I didnt bother reading the rest of your post except the end because its so obvious you dont know what you are talking about. Its funny you listed how to edit a Linux/Unix host file. The IP that its pointing at is a physical piece of hardware eventually.only reachable by physical means. That little work around you listed doesnt circumvent the internet. Its used only for local resolution. It tells that computer in order to reach the URL of stormfront that it needs to point to that new IP. it cant control what routers will do with the traffic on the internet. If the organizations that own those means cuts them off they cant do anything. You cant even exist on the internet without the permission of IANA who ultimately gives out public IP addresses even though its now delegated to ARIN. Where do you think stormfront gets its IP address from? You dont just get to make up your IP address. Its assigned.
Have at you and continue to think you're smart when you're in the wrong
I've got a few years on ya pup. I built my first public network server before the internet really even existed. You're wrapped up in your little world of cables and routers at the bottom "private" tier (aka network engineering and creating private LANS), and not listening to what I'm telling you about the non-physical side being what actually directs the flow of traffic on the internet itself. Look around the internet and you'll save yourself the embarrassment. I mean seriously, you just used video phone calls as a "knowledge reference" for how the internet works son... Please. The network engineer part is slightly more impressive sounding at least. Either way, your job experience has little to nothing to do with the resolution of domain names on the internet; and if you actually have such experience under your belt you damn well know it. Still, I'll give you the benefit of the doubt because I do so enjoy geeking out with a fellow computer nerd, even if the nerd in question is attempting to bullshit a crowd.
Perhaps missed the day(s) where they taught about the function of the hosts file and it's automated replacement [for the internet] by the DNS system in the 80s. Here's a quick refresher course (relevance emphasis added):
hosts (file) - Wikipedia - "The computer file hosts is an operating system file that maps hostnames to IP addresses. It is a plain text file. Originally a file named HOSTS.TXT was manually maintained and made available via file sharing by Stanford Research Institute for the ARPANET membership, containing the hostnames and address of hosts as contributed for inclusion by member organizations. The Domain Name System, first described in 1983 and implemented in 1984, automated the publication process and provided instantaneous and dynamic hostname resolution in the rapidly growing network. In modern operating systems, the hosts file remains an alternative name resolution mechanism, configurable often as part of facilities such as the Name Service Switch as either the primary method or as a fallback method."
Hostname - Wikipedia - "In computer networking, a hostname (archaically nodename) is a label that is assigned to a device connected to a computer network and that is used to identify the device in various forms of electronic communication, such as the World Wide Web. Hostnames may be simple names consisting of a single word or phrase, or they may be structured."
IP address - Wikipedia - "An Internet Protocol address (IP address) is a numerical label assigned to each device connected to a computer network that uses the Internet Protocol for communication. An IP address serves two principal functions: host or network interface identification and location addressing."
DNS Name Resolution - "DNS name resolution is nothing but resolving host names, such as www.nixcraft.com, to their corresponding IP addresses. DNS works as the “phone book” for the Internet by translating hostname into IP address or vise versa. Most DNS server stores following information:
a) Hostname and their IP address
b) List of mail server and their IP address for given domain name
c) Anti spam configuration and much more.
Without DNS name resolution, nothing will work on the Internet. Nobody likes to remember IP address, so DNS is foundation of many Internet services such as web, proxy, email and so on."
Domain Name System (DNS) - "The DNS enables domain names to stay constant while the underlying network topology and IP addresses change. This provides stability at the application level while enabling network applications to find and communicate with each other using the Internet protocol no matter how the underlying physical network changes."
^^ And it is that last bit right there that you get fucked up on. The physical network has no impact on the routing to websites - that is the realm of DNS. It is also why Stormfront users can still access their server, despite their domain name being jacked - because the site /still/ exits on the physical web and still has an IP address that ANYONE can access simply by changing their hosts file to resolve "stormfront.com" to the relevant IP address of the site; DNS registrar Network Solutions is completely /unneeded/ in the process - they can be bypassed simply and easily. Which is exactly how one would start an internet 2.0, create new DNS registrar - just as one would do with HOSTS file and boom! new IP address to domain name resolution.
See also how this would be implemented on the "client" side - How to Bypass OpenDNS Internet Security
Hate to break it to you but the below statement is false. If DNS didnt exist you could still have an internet. You posted the definition of DNS but you dont seem to understand it.
"Without DNS name resolution, nothing will work on the Internet. Nobody likes to remember IP address, so DNS is foundation of many Internet services such as web, proxy, email and so on."
Let me explain it laymans terms. When you type www.google.com, all DNS does is translate that to an IP address. You dont need DNS. All you have to do is type this in your browser.
http : // 74.125.199.103
Clip relevant portion [...]
OK so now youre claiming you invented the internet before it was invented yet your posting something as mundane as what a host file does and what the DNS protocol does.i think I'll trust my 20 plus years in the Network engineering and VoIP Collaboration field over your obvious lack of knowledge on the subject.Its obvious you dont realize that even the satellite companies have a network that connects by physical means to the internet. I didnt bother reading the rest of your post except the end because its so obvious you dont know what you are talking about. Its funny you listed how to edit a Linux/Unix host file. The IP that its pointing at is a physical piece of hardware eventually.only reachable by physical means. That little work around you listed doesnt circumvent the internet. Its used only for local resolution. It tells that computer in order to reach the URL of stormfront that it needs to point to that new IP. it cant control what routers will do with the traffic on the internet. If the organizations that own those means cuts them off they cant do anything. You cant even exist on the internet without the permission of IANA who ultimately gives out public IP addresses even though its now delegated to ARIN. Where do you think stormfront gets its IP address from? You dont just get to make up your IP address. Its assigned.
Have at you and continue to think you're smart when you're in the wrong
I've got a few years on ya pup. I built my first public network server before the internet really even existed. You're wrapped up in your little world of cables and routers at the bottom "private" tier (aka network engineering and creating private LANS), and not listening to what I'm telling you about the non-physical side being what actually directs the flow of traffic on the internet itself. Look around the internet and you'll save yourself the embarrassment. I mean seriously, you just used video phone calls as a "knowledge reference" for how the internet works son... Please. The network engineer part is slightly more impressive sounding at least. Either way, your job experience has little to nothing to do with the resolution of domain names on the internet; and if you actually have such experience under your belt you damn well know it. Still, I'll give you the benefit of the doubt because I do so enjoy geeking out with a fellow computer nerd, even if the nerd in question is attempting to bullshit a crowd.
Perhaps missed the day(s) where they taught about the function of the hosts file and it's automated replacement [for the internet] by the DNS system in the 80s. Here's a quick refresher course (relevance emphasis added):
hosts (file) - Wikipedia - "The computer file hosts is an operating system file that maps hostnames to IP addresses. It is a plain text file. Originally a file named HOSTS.TXT was manually maintained and made available via file sharing by Stanford Research Institute for the ARPANET membership, containing the hostnames and address of hosts as contributed for inclusion by member organizations. The Domain Name System, first described in 1983 and implemented in 1984, automated the publication process and provided instantaneous and dynamic hostname resolution in the rapidly growing network. In modern operating systems, the hosts file remains an alternative name resolution mechanism, configurable often as part of facilities such as the Name Service Switch as either the primary method or as a fallback method."
Hostname - Wikipedia - "In computer networking, a hostname (archaically nodename) is a label that is assigned to a device connected to a computer network and that is used to identify the device in various forms of electronic communication, such as the World Wide Web. Hostnames may be simple names consisting of a single word or phrase, or they may be structured."
IP address - Wikipedia - "An Internet Protocol address (IP address) is a numerical label assigned to each device connected to a computer network that uses the Internet Protocol for communication. An IP address serves two principal functions: host or network interface identification and location addressing."
DNS Name Resolution - "DNS name resolution is nothing but resolving host names, such as www.nixcraft.com, to their corresponding IP addresses. DNS works as the “phone book” for the Internet by translating hostname into IP address or vise versa. Most DNS server stores following information:
a) Hostname and their IP address
b) List of mail server and their IP address for given domain name
c) Anti spam configuration and much more.
Without DNS name resolution, nothing will work on the Internet. Nobody likes to remember IP address, so DNS is foundation of many Internet services such as web, proxy, email and so on."
Domain Name System (DNS) - "The DNS enables domain names to stay constant while the underlying network topology and IP addresses change. This provides stability at the application level while enabling network applications to find and communicate with each other using the Internet protocol no matter how the underlying physical network changes."
^^ And it is that last bit right there that you get fucked up on. The physical network has no impact on the routing to websites - that is the realm of DNS. It is also why Stormfront users can still access their server, despite their domain name being jacked - because the site /still/ exits on the physical web and still has an IP address that ANYONE can access simply by changing their hosts file to resolve "stormfront.com" to the relevant IP address of the site; DNS registrar Network Solutions is completely /unneeded/ in the process - they can be bypassed simply and easily. Which is exactly how one would start an internet 2.0, create new DNS registrar - just as one would do with HOSTS file and boom! new IP address to domain name resolution.
See also how this would be implemented on the "client" side - How to Bypass OpenDNS Internet Security
Hate to break it to you but the below statement is false. If DNS didnt exist you could still have an internet. You posted the definition of DNS but you dont seem to understand it.
"Without DNS name resolution, nothing will work on the Internet. Nobody likes to remember IP address, so DNS is foundation of many Internet services such as web, proxy, email and so on."
Let me explain it laymans terms. When you type www.google.com, all DNS does is translate that to an IP address. You dont need DNS. All you have to do is type this in your browser.
http : // 74.125.199.103
Uhm no, I never claimed to "invent the internet" dumbass I said I had a "public network server" - which you should know all about if you had any formal training in your claimed fields. Go look up BBS's, and their predecessors "mainframes," and get back to me when you're educated.
As for your note on the without DNS internet wouldn't work quote, that's actually not my statement it's cyberciti.biz as denoted by the link to them - but you're right to call it out - just as I did, and have been for days. DNS just controls the redirection of domain names (www.blahblahblah.com) to computer/server locations (their individual IPs) on the internet. That's exactly what /you/ have been arguing /AGAINST/ this entire time. Christ...
Moving on though, thank you for finally admitting I was right so we can tell the posters who might be still reading this the truth about "pathways" on the internet being little more than DNS text entries on a database server.
So from the top when you apparently had a brain fart and exposed yourself as either an idiot, a liar, a troll, or most likely all three.
Clip relevant portion [...]
To reiterate - Internet 2.0 could be created rather easily making new DNS servers to query - no new "cables" or "physical" thing really needs to be laid/installed to do it. A server for the new DNS database, but anyone can hook one of those up to the internet, maybe a browser that sends the clients to the new DNS server (instead of internet 1.0s) but that'd just be a convenience thing so folks didn't have to mess with their computer configuration files.
OK so now youre claiming you invented the internet before it was invented yet your posting something as mundane as what a host file does and what the DNS protocol does.i think I'll trust my 20 plus years in the Network engineering and VoIP Collaboration field over your obvious lack of knowledge on the subject.Have at you and continue to think you're smart when you're in the wrong
I've got a few years on ya pup. I built my first public network server before the internet really even existed. You're wrapped up in your little world of cables and routers at the bottom "private" tier (aka network engineering and creating private LANS), and not listening to what I'm telling you about the non-physical side being what actually directs the flow of traffic on the internet itself. Look around the internet and you'll save yourself the embarrassment. I mean seriously, you just used video phone calls as a "knowledge reference" for how the internet works son... Please. The network engineer part is slightly more impressive sounding at least. Either way, your job experience has little to nothing to do with the resolution of domain names on the internet; and if you actually have such experience under your belt you damn well know it. Still, I'll give you the benefit of the doubt because I do so enjoy geeking out with a fellow computer nerd, even if the nerd in question is attempting to bullshit a crowd.
Perhaps missed the day(s) where they taught about the function of the hosts file and it's automated replacement [for the internet] by the DNS system in the 80s. Here's a quick refresher course (relevance emphasis added):
hosts (file) - Wikipedia - "The computer file hosts is an operating system file that maps hostnames to IP addresses. It is a plain text file. Originally a file named HOSTS.TXT was manually maintained and made available via file sharing by Stanford Research Institute for the ARPANET membership, containing the hostnames and address of hosts as contributed for inclusion by member organizations. The Domain Name System, first described in 1983 and implemented in 1984, automated the publication process and provided instantaneous and dynamic hostname resolution in the rapidly growing network. In modern operating systems, the hosts file remains an alternative name resolution mechanism, configurable often as part of facilities such as the Name Service Switch as either the primary method or as a fallback method."
Hostname - Wikipedia - "In computer networking, a hostname (archaically nodename) is a label that is assigned to a device connected to a computer network and that is used to identify the device in various forms of electronic communication, such as the World Wide Web. Hostnames may be simple names consisting of a single word or phrase, or they may be structured."
IP address - Wikipedia - "An Internet Protocol address (IP address) is a numerical label assigned to each device connected to a computer network that uses the Internet Protocol for communication. An IP address serves two principal functions: host or network interface identification and location addressing."
DNS Name Resolution - "DNS name resolution is nothing but resolving host names, such as www.nixcraft.com, to their corresponding IP addresses. DNS works as the “phone book” for the Internet by translating hostname into IP address or vise versa. Most DNS server stores following information:
a) Hostname and their IP address
b) List of mail server and their IP address for given domain name
c) Anti spam configuration and much more.
Without DNS name resolution, nothing will work on the Internet. Nobody likes to remember IP address, so DNS is foundation of many Internet services such as web, proxy, email and so on."
Domain Name System (DNS) - "The DNS enables domain names to stay constant while the underlying network topology and IP addresses change. This provides stability at the application level while enabling network applications to find and communicate with each other using the Internet protocol no matter how the underlying physical network changes."
^^ And it is that last bit right there that you get fucked up on. The physical network has no impact on the routing to websites - that is the realm of DNS. It is also why Stormfront users can still access their server, despite their domain name being jacked - because the site /still/ exits on the physical web and still has an IP address that ANYONE can access simply by changing their hosts file to resolve "stormfront.com" to the relevant IP address of the site; DNS registrar Network Solutions is completely /unneeded/ in the process - they can be bypassed simply and easily. Which is exactly how one would start an internet 2.0, create new DNS registrar - just as one would do with HOSTS file and boom! new IP address to domain name resolution.
See also how this would be implemented on the "client" side - How to Bypass OpenDNS Internet Security
Hate to break it to you but the below statement is false. If DNS didnt exist you could still have an internet. You posted the definition of DNS but you dont seem to understand it.
"Without DNS name resolution, nothing will work on the Internet. Nobody likes to remember IP address, so DNS is foundation of many Internet services such as web, proxy, email and so on."
Let me explain it laymans terms. When you type www.google.com, all DNS does is translate that to an IP address. You dont need DNS. All you have to do is type this in your browser.
http : // 74.125.199.103
Uhm no, I never claimed to "invent the internet" dumbass I said I had a "public network server" - which you should know all about if you had any formal training in your claimed fields. Go look up BBS's, and their predecessors "mainframes," and get back to me when you're educated.
As for your note on the without DNS internet wouldn't work quote, that's actually not my statement it's cyberciti.biz as denoted by the link to them - but you're right to call it out - just as I did, and have been for days. DNS just controls the redirection of domain names (www.blahblahblah.com) to computer/server locations (their individual IPs) on the internet. That's exactly what /you/ have been arguing /AGAINST/ this entire time. Christ...
Moving on though, thank you for finally admitting I was right so we can tell the posters who might be still reading this the truth about "pathways" on the internet being little more than DNS text entries on a database server.
So from the top when you apparently had a brain fart and exposed yourself as either an idiot, a liar, a troll, or most likely all three.
Clip relevant portion [...]
To reiterate - Internet 2.0 could be created rather easily making new DNS servers to query - no new "cables" or "physical" thing really needs to be laid/installed to do it. A server for the new DNS database, but anyone can hook one of those up to the internet, maybe a browser that sends the clients to the new DNS server (instead of internet 1.0s) but that'd just be a convenience thing so folks didn't have to mess with their computer configuration files.
I didnt say you were right. I said you didnt know what you were talking about. How did people access your public network server?
I think youre confused. I can have a million DNS servers in my home. If I dont have an internet connection no one in the world can connect to me except me. In your theoretical world how do other computers link to my DNS servers without crossing public domain boundaries? In your brainfart you still havent explained that feat.
I already pointed out that was pipe dream. Only someone illiterate or someone that had no clue what they were talking about would suggest such an asinine thing. You do realize that "wireless" has a limited range (not to mention the bandwidth issues) and it still has to go through a physical infrastructure to be passed on right? Your internet 2.0 would be a gigantic bottle neck using wireless as its primary medium even if you used a physical backbone. Now lets the address the real obvious flaw. Who is transmitting the wireless signals?OK so now youre claiming you invented the internet before it was invented yet your posting something as mundane as what a host file does and what the DNS protocol does.i think I'll trust my 20 plus years in the Network engineering and VoIP Collaboration field over your obvious lack of knowledge on the subject.
I've got a few years on ya pup. I built my first public network server before the internet really even existed. You're wrapped up in your little world of cables and routers at the bottom "private" tier (aka network engineering and creating private LANS), and not listening to what I'm telling you about the non-physical side being what actually directs the flow of traffic on the internet itself. Look around the internet and you'll save yourself the embarrassment. I mean seriously, you just used video phone calls as a "knowledge reference" for how the internet works son... Please. The network engineer part is slightly more impressive sounding at least. Either way, your job experience has little to nothing to do with the resolution of domain names on the internet; and if you actually have such experience under your belt you damn well know it. Still, I'll give you the benefit of the doubt because I do so enjoy geeking out with a fellow computer nerd, even if the nerd in question is attempting to bullshit a crowd.
Perhaps missed the day(s) where they taught about the function of the hosts file and it's automated replacement [for the internet] by the DNS system in the 80s. Here's a quick refresher course (relevance emphasis added):
hosts (file) - Wikipedia - "The computer file hosts is an operating system file that maps hostnames to IP addresses. It is a plain text file. Originally a file named HOSTS.TXT was manually maintained and made available via file sharing by Stanford Research Institute for the ARPANET membership, containing the hostnames and address of hosts as contributed for inclusion by member organizations. The Domain Name System, first described in 1983 and implemented in 1984, automated the publication process and provided instantaneous and dynamic hostname resolution in the rapidly growing network. In modern operating systems, the hosts file remains an alternative name resolution mechanism, configurable often as part of facilities such as the Name Service Switch as either the primary method or as a fallback method."
Hostname - Wikipedia - "In computer networking, a hostname (archaically nodename) is a label that is assigned to a device connected to a computer network and that is used to identify the device in various forms of electronic communication, such as the World Wide Web. Hostnames may be simple names consisting of a single word or phrase, or they may be structured."
IP address - Wikipedia - "An Internet Protocol address (IP address) is a numerical label assigned to each device connected to a computer network that uses the Internet Protocol for communication. An IP address serves two principal functions: host or network interface identification and location addressing."
DNS Name Resolution - "DNS name resolution is nothing but resolving host names, such as www.nixcraft.com, to their corresponding IP addresses. DNS works as the “phone book” for the Internet by translating hostname into IP address or vise versa. Most DNS server stores following information:
a) Hostname and their IP address
b) List of mail server and their IP address for given domain name
c) Anti spam configuration and much more.
Without DNS name resolution, nothing will work on the Internet. Nobody likes to remember IP address, so DNS is foundation of many Internet services such as web, proxy, email and so on."
Domain Name System (DNS) - "The DNS enables domain names to stay constant while the underlying network topology and IP addresses change. This provides stability at the application level while enabling network applications to find and communicate with each other using the Internet protocol no matter how the underlying physical network changes."
^^ And it is that last bit right there that you get fucked up on. The physical network has no impact on the routing to websites - that is the realm of DNS. It is also why Stormfront users can still access their server, despite their domain name being jacked - because the site /still/ exits on the physical web and still has an IP address that ANYONE can access simply by changing their hosts file to resolve "stormfront.com" to the relevant IP address of the site; DNS registrar Network Solutions is completely /unneeded/ in the process - they can be bypassed simply and easily. Which is exactly how one would start an internet 2.0, create new DNS registrar - just as one would do with HOSTS file and boom! new IP address to domain name resolution.
See also how this would be implemented on the "client" side - How to Bypass OpenDNS Internet Security
Hate to break it to you but the below statement is false. If DNS didnt exist you could still have an internet. You posted the definition of DNS but you dont seem to understand it.
"Without DNS name resolution, nothing will work on the Internet. Nobody likes to remember IP address, so DNS is foundation of many Internet services such as web, proxy, email and so on."
Let me explain it laymans terms. When you type www.google.com, all DNS does is translate that to an IP address. You dont need DNS. All you have to do is type this in your browser.
http : // 74.125.199.103
Uhm no, I never claimed to "invent the internet" dumbass I said I had a "public network server" - which you should know all about if you had any formal training in your claimed fields. Go look up BBS's, and their predecessors "mainframes," and get back to me when you're educated.
As for your note on the without DNS internet wouldn't work quote, that's actually not my statement it's cyberciti.biz as denoted by the link to them - but you're right to call it out - just as I did, and have been for days. DNS just controls the redirection of domain names (www.blahblahblah.com) to computer/server locations (their individual IPs) on the internet. That's exactly what /you/ have been arguing /AGAINST/ this entire time. Christ...
Moving on though, thank you for finally admitting I was right so we can tell the posters who might be still reading this the truth about "pathways" on the internet being little more than DNS text entries on a database server.
So from the top when you apparently had a brain fart and exposed yourself as either an idiot, a liar, a troll, or most likely all three.
Clip relevant portion [...]
To reiterate - Internet 2.0 could be created rather easily making new DNS servers to query - no new "cables" or "physical" thing really needs to be laid/installed to do it. A server for the new DNS database, but anyone can hook one of those up to the internet, maybe a browser that sends the clients to the new DNS server (instead of internet 1.0s) but that'd just be a convenience thing so folks didn't have to mess with their computer configuration files.
I didnt say you were right. I said you didnt know what you were talking about. How did people access your public network server?
I think youre confused. I can have a million DNS servers in my home. If I dont have an internet connection no one in the world can connect to me except me. In your theoretical world how do other computers link to my DNS servers without crossing public domain boundaries? In your brainfart you still havent explained that feat.
Yes it did dear, you're apparently too stupid to read it. For the third time:
[
Can you not be an idiot? This thread is not about the government. It's about a contract between a business and a customer of theirs. I've backed up what I said. Network Solutions stated the reason they dropped stormfront.com. I posted their position. I posted Network Solutions' Acceptable Use Policy to demonstrate where stormfront.com violated that agreement. So who knows what you think I didn't back up?
Yes. Network solutions has a policy saying no service for white nationalists and bakers have a policy of no service for queers. Why is one ok but the other isn't.?
Show the website where BLM threatened to kill cops...
