Announcement

Collapse
No announcement yet.

DNS Down? Not anymore!

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • DNS Down? Not anymore!

    Check it out! Very cool way to still access your favorite sites (Like Itulip) in the event of a DNS (Domain Name Server) Failure. (For what ever reason that may occur).

    http://dnsdown.com/doit.htm

    "
    Welcome to DNS Down


    Some History & Etcetera
    Most people don't know how The Net works, they just click on links or use their email, with no regard as to how it works, and that is as it should be, most folks don't know how a car works, but they can still drive one.

    In 1969, when Bolt, Beranek and Newman, got the first IP packetizing and routing programs working on old minicomputers, the ARPANet as we called it back then was born. It was designed to bypass cities that had been hit by a nuclear weapon! In other words, the Internet as we know it today, was originally a Pentagon project for designing a communications system that could automatically route data around destroyed cities. Back then, all we had were 'circuit switched' networks, when you made a phone call, you owned the 'copper' from one end to the other, for the duration of the call. It doesn't work that way anymore, everything is digital, everything is packetized data, and everything, phone, cell phone, radio, and some TV, depends on the internet, there is NO WAY for any entity, government or otherwise, to TAKE DOWN THE INTERNET without taking down everything!. Oh, they can take down pieces and parts, but not the whole thing. Its like a spiderweb that covers the planet. They would then lose the utility of it for themselves, so, is that even realistic? No, much easier to just 'block' those sites that are politically 'unnecessary' or have 'hate' speech on them, or, pick your reason. There is only one convenient way, and that's the DNS system, the Internet's Phone Book.

    The Internet, in the old days, did not have a mechanism for 'discovery'. Today, you can type the name of a web site into your browser, or click on a link, and it just goes there, your computer 'discovers' the destination for the connection. In the old days it didn't work like this. We had to program in what is known as the IP Address of the computer we wanted to 'talk' to, it was extremely cumbersome, thus the DNS system was born. (We didn't have a WWW either, just file transfer and primitive email.) Connections from your computer to websites or emails, are made to the other computers IP Address, IP stands for Internet Protocol, think of this as the Internet Phone number. You must know this number in order to connect to it, so, how do you 'discover' that IP? In order for this new system to work transparently, they invented something called the DNS system, the Domain Name System. All web sites, must be registered in a DNS server, somewhere. All DNS servers are tied to 'root' servers, these root servers are few, and vulnerable. This, DNS network, became, the Internet Phone Book. It really is that simple.

    When you type a website name into your browser, your browser, asks the DNS system "what's the number for this name?", your local DNS server defers to the root servers, and it may bounce around the world searching, but eventually, it comes back and provides the browser with the IP address of the website. Then, the browser connects to the web server, and there you are, the web page you asked for. Simple, fast, transparent. Some people, will tell you that you can find out the IP address of a web site, and just plug that into the browser, and it will bypass the DNS system, and they are right, to a point. In the last few years, IP addresses started become short, so system software engineers, figured out a way to share IP addresses on one server, and run multiple web sites on one computer, this is known as "virtual" servers. Plugging in the IP for these type servers, (like the one you're reading now), will not work, since there are multiple web sites running on that IP address. This is overcome in new browsers, that send the connection request with a Header, the header contains the name of the site, and the web server figures out which virtual server to connect you to. So why is any of this important?

    If the UN, or a terrorist, or just plain old system failure, of the DNS server that you depend on, goes down, or a site is blocked, it will be done through the DNS system. It would be an almost impossible task to take down all sites by IP address, if they block one IP, it will take down everything on that server, and its not necessary when all they have to do, is change a few servers, the previously mentioned Root Servers. The Internet Phone Book will simply be shorted out. Taking out all but the sites they want to run. Simple, instant, effective. The Net, as far as most people are concerned, would be down, except for the 'approved' sites. How many of your favorite sites, do you think, would be left alive under an 'emergency information lockdown'?

    DNSDown, was specifically designed to install an internet bypass. It builds a mini phone book, a DNS cache server, in your machine, based on our publicized 'Well Known Links' plus your own bookmarks...taking advantage of the 'Old Way'... This software, is being offered for free to the community, it is new, it is still undergoing testing, ..we can't unblock IP blocks, but we can fight the fight against free speech. We don't think this can be the only tool in the box. This is only the beginning, if this idea takes off, we hope to help build an UnderNet. This would be an alternate set of privately controlled DNS servers, setup outside of the current 'chain of command'... The first step, is a way to build our own private internet phone books...the next steps should be; alternate registrar software and alternate root server setup, we cannot predict when we can get this done, since we have to make a living somehow. Hopefully, we will gain some motivated assistance...we are even looking at ties to Freenet, and Tor networks. (so called anonymizer networks)

    On the home page of this site, you notice the Well Known links, which have an IP based clickable link, as well as the IP address / Real or Virt. The real addresses are directly clickable, the Virt addresses MAY be virtual, and may only be accessible by downloading the file and following the directions to install it. The way this status is determined is not reliable as it depends on a reverse look up, not all hosts maintain proper reverse lookups, as it is not required. (Reverse lookup is simply the reverse of a name lookup...'give me the name from this number'. ) The only reliable way to use the well known links, is through the downloadable file. They are there for reference, and provide a point of sharing for everybody. Stay tuned for future developments"

  • #2
    Re: DNS Down? Not anymore!

    oh, yeh? well... i'm getting one of these...

    Comment


    • #3
      Re: DNS Down? Not anymore!

      Originally posted by jtabeb View Post
      Check it out! Very cool way to still access your favorite sites (Like Itulip) in the event of a DNS (Domain Name Server) Failure. (For what ever reason that may occur).

      http://dnsdown.com/doit.htm

      "
      Welcome to DNS Down


      Some History & Etcetera
      Most people don't know how The Net works, they just click on links or use their email, with no regard as to how it works, and that is as it should be, most folks don't know how a car works, but they can still drive one.

      In 1969, when Bolt, Beranek and Newman, got the first IP packetizing and routing programs working on old minicomputers, the ARPANet as we called it back then was born. It was designed to bypass cities that had been hit by a nuclear weapon! In other words, the Internet as we know it today, was originally a Pentagon project for designing a communications system that could automatically route data around destroyed cities. Back then, all we had were 'circuit switched' networks, when you made a phone call, you owned the 'copper' from one end to the other, for the duration of the call. It doesn't work that way anymore, everything is digital, everything is packetized data, and everything, phone, cell phone, radio, and some TV, depends on the internet, there is NO WAY for any entity, government or otherwise, to TAKE DOWN THE INTERNET without taking down everything!. Oh, they can take down pieces and parts, but not the whole thing. Its like a spiderweb that covers the planet. They would then lose the utility of it for themselves, so, is that even realistic? No, much easier to just 'block' those sites that are politically 'unnecessary' or have 'hate' speech on them, or, pick your reason. There is only one convenient way, and that's the DNS system, the Internet's Phone Book.

      The Internet, in the old days, did not have a mechanism for 'discovery'. Today, you can type the name of a web site into your browser, or click on a link, and it just goes there, your computer 'discovers' the destination for the connection. In the old days it didn't work like this. We had to program in what is known as the IP Address of the computer we wanted to 'talk' to, it was extremely cumbersome, thus the DNS system was born. (We didn't have a WWW either, just file transfer and primitive email.) Connections from your computer to websites or emails, are made to the other computers IP Address, IP stands for Internet Protocol, think of this as the Internet Phone number. You must know this number in order to connect to it, so, how do you 'discover' that IP? In order for this new system to work transparently, they invented something called the DNS system, the Domain Name System. All web sites, must be registered in a DNS server, somewhere. All DNS servers are tied to 'root' servers, these root servers are few, and vulnerable. This, DNS network, became, the Internet Phone Book. It really is that simple.

      When you type a website name into your browser, your browser, asks the DNS system "what's the number for this name?", your local DNS server defers to the root servers, and it may bounce around the world searching, but eventually, it comes back and provides the browser with the IP address of the website. Then, the browser connects to the web server, and there you are, the web page you asked for. Simple, fast, transparent. Some people, will tell you that you can find out the IP address of a web site, and just plug that into the browser, and it will bypass the DNS system, and they are right, to a point. In the last few years, IP addresses started become short, so system software engineers, figured out a way to share IP addresses on one server, and run multiple web sites on one computer, this is known as "virtual" servers. Plugging in the IP for these type servers, (like the one you're reading now), will not work, since there are multiple web sites running on that IP address. This is overcome in new browsers, that send the connection request with a Header, the header contains the name of the site, and the web server figures out which virtual server to connect you to. So why is any of this important?

      If the UN, or a terrorist, or just plain old system failure, of the DNS server that you depend on, goes down, or a site is blocked, it will be done through the DNS system. It would be an almost impossible task to take down all sites by IP address, if they block one IP, it will take down everything on that server, and its not necessary when all they have to do, is change a few servers, the previously mentioned Root Servers. The Internet Phone Book will simply be shorted out. Taking out all but the sites they want to run. Simple, instant, effective. The Net, as far as most people are concerned, would be down, except for the 'approved' sites. How many of your favorite sites, do you think, would be left alive under an 'emergency information lockdown'?

      DNSDown, was specifically designed to install an internet bypass. It builds a mini phone book, a DNS cache server, in your machine, based on our publicized 'Well Known Links' plus your own bookmarks...taking advantage of the 'Old Way'... This software, is being offered for free to the community, it is new, it is still undergoing testing, ..we can't unblock IP blocks, but we can fight the fight against free speech. We don't think this can be the only tool in the box. This is only the beginning, if this idea takes off, we hope to help build an UnderNet. This would be an alternate set of privately controlled DNS servers, setup outside of the current 'chain of command'... The first step, is a way to build our own private internet phone books...the next steps should be; alternate registrar software and alternate root server setup, we cannot predict when we can get this done, since we have to make a living somehow. Hopefully, we will gain some motivated assistance...we are even looking at ties to Freenet, and Tor networks. (so called anonymizer networks)

      On the home page of this site, you notice the Well Known links, which have an IP based clickable link, as well as the IP address / Real or Virt. The real addresses are directly clickable, the Virt addresses MAY be virtual, and may only be accessible by downloading the file and following the directions to install it. The way this status is determined is not reliable as it depends on a reverse look up, not all hosts maintain proper reverse lookups, as it is not required. (Reverse lookup is simply the reverse of a name lookup...'give me the name from this number'. ) The only reliable way to use the well known links, is through the downloadable file. They are there for reference, and provide a point of sharing for everybody. Stay tuned for future developments"
      I work in a place where about half the staff doesn't believe in DNS ( the legacy of a former sysadmin staff that was noted for being somewhat less than customer service oriented) . On a daily basis I get a call that goes something like this:
      "the new portal for [Very Big Customer] is down! Fix it right now!"
      after some troubleshooting I discover that the developer or QA staff has modified their hosts file to point to their own machine or frequently the machine they used to sit at, or some random machine... you get the picture.

      Do not fear the DNS the DNS is your friend.

      Comment


      • #4
        Re: DNS Down? Not anymore!

        Originally posted by jtabeb View Post
        Check it out! Very cool way to still access your favorite sites (Like Itulip) in the event of a DNS (Domain Name Server) Failure. (For what ever reason that may occur).
        I don't think so.

        IP addresses change over time, as servers get moved about the net. If you hardcode them like this, you'll give yourself all sorts of grief, unobvious grief long after you've forgotten you made this change grief. You don't want that.

        The proper way to handle this is to list backup DNS servers. Those of you (most of you) using DHCP to setup your network relay and DNS hosts can't do this; you're stuck relying on the services your ISP provides. Those setting static relay and DNS host addresses can add an automatic fallback DNS server in case your ISP's DNS server is out to lunch. If you can only have one backup (that is, if you're on Windows), I recommend 4.2.2.1, which is Level 3 out of Broomfield, Colorado. They do some serious, heavy duty, internet backbone infrastructure and provide very fast lookups (under 50 msec or so anywhere I've tested in the U.S.) I've commited "4.2.2.1" to memory long ago, for whenever I need to type in a DNS server IP address. Those on most any Unix, BSD or Linux (or Mac OSX?) can add several DNS server backups to your /etc/resolv.conf file. Another DNS server I am fond of is OpenDNS.com. They are making a business out of DNS services. Google just added two DNS servers for public use at 8.8.8.8 and 8.8.4.4, but so far they are running slower (at least to here in North Texas) than the guys who've been doing this a while.

        Here's my /etc/resolv.conf file:
        # Average 208.67.222.222 (OpenDNS) speed: 56 msec
        nameserver 208.67.222.222

        # Average 4.2.2.1 (Level 3, Broomfield CO) speed: 47 msec
        nameserver 4.2.2.1

        # Average 8.8.4.4 (Google DNS) speed: 61 msec
        nameserver 8.8.4.4

        # Average 8.8.8.8 (Google DNS) speed: 83 msec
        nameserver 8.8.8.8
        Well, part of my resolv.conf. I run my own DNS server which appears first in this file, but that's of no use to anyone else (it's inside my firewall.)

        Back to reality for most users: you're using DHCP to automatically set your PC to use your ISP's DNS server. If that server is down, you're as good as off the internet until it comes back up; deal with it.
        Most folks are good; a few aren't.

        Comment


        • #5
          Re: DNS Down? Not anymore!

          Cool ... but do you crash if you have to scratch your ass?

          Comment


          • #6
            Re: DNS Down? Not anymore!

            Originally posted by ThePythonicCow View Post
            I don't think so.

            IP addresses change over time, as servers get moved about the net. If you hardcode them like this, you'll give yourself all sorts of grief, unobvious grief long after you've forgotten you made this change grief. You don't want that.

            The proper way to handle this is to list backup DNS servers. Those of you (most of you) using DHCP to setup your network relay and DNS hosts can't do this; you're stuck relying on the services your ISP provides. Those setting static relay and DNS host addresses can add an automatic fallback DNS server in case your ISP's DNS server is out to lunch. If you can only have one backup (that is, if you're on Windows), I recommend 4.2.2.1, which is Level 3 out of Broomfield, Colorado. They do some serious, heavy duty, internet backbone infrastructure and provide very fast lookups (under 50 msec or so anywhere I've tested in the U.S.) I've commited "4.2.2.1" to memory long ago, for whenever I need to type in a DNS server IP address. Those on most any Unix, BSD or Linux (or Mac OSX?) can add several DNS server backups to your /etc/resolv.conf file. Another DNS server I am fond of is OpenDNS.com. They are making a business out of DNS services. Google just added two DNS servers for public use at 8.8.8.8 and 8.8.4.4, but so far they are running slower (at least to here in North Texas) than the guys who've been doing this a while.

            Here's my /etc/resolv.conf file:
            Well, part of my resolv.conf. I run my own DNS server which appears first in this file, but that's of no use to anyone else (it's inside my firewall.)

            Back to reality for most users: you're using DHCP to automatically set your PC to use your ISP's DNS server. If that server is down, you're as good as off the internet until it comes back up; deal with it.
            In addition I would add in Ireland we already have censorship to some sites - www.piratebay.org being one - there are ways around the filter, however the filter is at the ip address level not the dns name, therefore modifying the host file will not circumvent the filter and bring up many of the problems alluded to already. Using an internet proxy server for browsing for circumventing filtering is a better option but has draw backs also - performance being one.


            ACCESS TO THIS IP ADDRESS RELATING TO THE PIRATE BAY WEBSITE HAS BEEN BLOCKED


            WHY?

            On the 24 July 2009, an Order was made by the High Court requiring eircom to block or otherwise disable access by its subscribers to the website thePirateBay.org, its related domain names, IP addresses and URLs. The Court was satisfied that on the basis of the evidence presented by the record companies that the PirateBay website is a website that facilitates the exchange of copyrighted sound recordings without the consent of the copyright owners.

            eircom recognises the legitimate rights of the owners of copyrighted material and believes that individuals who share or download copyrighted material without the authorisation or the permission of the copyright owner are acting illegally.

            The Order further provides that should the PirateBay website content be legitimatised in the future, then eircom has liberty to apply to the Court to have the Order vacated and access to the PirateBay website enabled.

            eircom in compliance with the Order has agreed that access to the website the PirateBay.org, its related domain names, IP addresses and URLs from the eircom network will be blocked indefinitely from the 1st September 2009.
            "that each simple substance has relations which express all the others"

            Comment


            • #7
              Re: DNS Down? Not anymore!

              Originally posted by ThePythonicCow View Post
              I don't think so.

              IP addresses change over time, as servers get moved about the net. If you hardcode them like this, you'll give yourself all sorts of grief, unobvious grief long after you've forgotten you made this change grief. You don't want that.

              The proper way to handle this is to list backup DNS servers. Those of you (most of you) using DHCP to setup your network relay and DNS hosts can't do this; you're stuck relying on the services your ISP provides. Those setting static relay and DNS host addresses can add an automatic fallback DNS server in case your ISP's DNS server is out to lunch. If you can only have one backup (that is, if you're on Windows), I recommend 4.2.2.1, which is Level 3 out of Broomfield, Colorado. They do some serious, heavy duty, internet backbone infrastructure and provide very fast lookups (under 50 msec or so anywhere I've tested in the U.S.) I've commited "4.2.2.1" to memory long ago, for whenever I need to type in a DNS server IP address. Those on most any Unix, BSD or Linux (or Mac OSX?) can add several DNS server backups to your /etc/resolv.conf file. Another DNS server I am fond of is OpenDNS.com. They are making a business out of DNS services. Google just added two DNS servers for public use at 8.8.8.8 and 8.8.4.4, but so far they are running slower (at least to here in North Texas) than the guys who've been doing this a while.

              Here's my /etc/resolv.conf file:
              Well, part of my resolv.conf. I run my own DNS server which appears first in this file, but that's of no use to anyone else (it's inside my firewall.)

              Back to reality for most users: you're using DHCP to automatically set your PC to use your ISP's DNS server. If that server is down, you're as good as off the internet until it comes back up; deal with it.

              Disagree, it may not work for some sites, but it DOES work.

              Here's proof:

              Domain Name news.bbc.co.uk :: IP Address 212.58.226.79




              Try just typing in the IP address into your browser's address bar.


              You'll get to BBC news UK site. I just tried it.

              Comment


              • #8
                Re: DNS Down? Not anymore!

                Originally posted by jtabeb View Post
                Disagree, it may not work for some sites, but it DOES work.

                .
                JTABEB, if this is really a concern; If I may be so bold as to make a suggestion to you, below is a link to an open source dns server software for WIN32 systems; it has dynamic caching as a feature, rather then trying to maintain a host file, as cow said ip addresses can change and the more sites you wish to maintain, the more difficulty you will have, if trying to do it manually via a host file.



                http://dhcp-dns-server.sourceforge.net/

                DNS Features
                Supports upto 8 forwarding servers
                Supports Dynamic Caching
                Supports Zone Transfers
                Supports Aliases
                Support MX Servers
                Support Wildcard Hosts
                Supports Primary and Secondary Mode of Operations
                Supports Child Zones
                Supports DNS Proxy
                Last edited by Diarmuid; January 27, 2010, 02:24 PM.
                "that each simple substance has relations which express all the others"

                Comment


                • #9
                  Re: DNS Down? Not anymore!

                  Originally posted by sunskyfan View Post
                  Cool ... but do you crash if you have to scratch your ass?
                  Easy enough to test for yourself.

                  "...the western financial system has already failed. The failure has just not yet been realized, while the system remains confident that it is still alive." Jesse

                  Comment


                  • #10
                    Re: DNS Down? Not anymore!

                    Originally posted by jtabeb View Post
                    Disagree, it may not work for some sites, but it DOES work.

                    Here's proof:

                    Domain Name news.bbc.co.uk :: IP Address 212.58.226.79




                    Try just typing in the IP address into your browser's address bar.


                    You'll get to BBC news UK site. I just tried it.
                    Jtabeb, ThePythonicCow was not saying it would not work. All domain names translate into a IP address as you show above. He was saying the IP address can change over time as things get moved. That is one reason for the DNS. If you hard code in the current IP address and the server is moved about the net for some reason, the hard coded IP address may point to somewhere you don't want to go.
                    jim

                    Comment


                    • #11
                      Re: DNS Down? Not anymore!

                      Originally posted by jtabeb View Post
                      Disagree, it may not work for some sites, but it DOES work.
                      Of course, it works for --all-- sites.

                      ... until sometime in the unknown future when that site changes its IP addr.
                      Most folks are good; a few aren't.

                      Comment


                      • #12
                        Re: DNS Down? Not anymore!

                        Originally posted by Diarmuid View Post
                        JTABEB, if this is really a concern; If I may be so bold as to make a suggestion to you, below is a link to an open source dns server software for WIN32 systems; it has dynamic caching as a feature, rather then trying to maintain a host file, as cow said ip addresses can change and the more sites you wish to maintain, the more difficulty you will have, if trying to do it manually via a host file.



                        http://dhcp-dns-server.sourceforge.net/

                        DNS Features
                        Supports upto 8 forwarding servers
                        Supports Dynamic Caching
                        Supports Zone Transfers
                        Supports Aliases
                        Support MX Servers
                        Support Wildcard Hosts
                        Supports Primary and Secondary Mode of Operations
                        Supports Child Zones
                        Supports DNS Proxy

                        Thanks (and I'll take BOLD and USEFUL any day!)

                        Comment


                        • #13
                          Re: DNS Down? Not anymore!

                          Originally posted by jtabeb View Post
                          Thanks (and I'll take BOLD and USEFUL any day!)
                          A pleasure
                          "that each simple substance has relations which express all the others"

                          Comment


                          • #14
                            Re: DNS Down? Not anymore!

                            Originally posted by Diarmuid View Post
                            below is a link to an open source dns server software for WIN32 systems; ...

                            http://dhcp-dns-server.sourceforge.net/
                            Interesting -- DNS servers for your Windows PC. I didn't realize such existed. Cool.

                            Looking around I see some other Windows PC DNS servers:

                            Simple DNS costs money, but claims to have a friendly GUI interface. A good interface could be worth the money, as DNS servers are not all that easy to administer.

                            I predict anyone who switches over to their own DNS server will have more downtime, not less, for a while until they get the hang of it. That GUI might be worth it.

                            Unbound is open source and looks to be a substantial effort by Verisign (one of the big guys in the Internet security business) to provide a serious alternative to the venerable DNS server "bind" (aka named.) I might have to check Unbound out. Currently I run bind, but that's for Unix/Linux boxes, not Windows. I see mention of a bind port to Windows called "ntbind", but I don't see much else about this port, so would be hesitant to suggest using it.
                            Most folks are good; a few aren't.

                            Comment


                            • #15
                              Re: DNS Down? Not anymore!

                              Originally posted by ThePythonicCow View Post
                              Of course, it works for --all-- sites.

                              ... until sometime in the unknown future when that site changes its IP addr.
                              Not necessarily -- Web pages have links, deep links etc. in them that are linked by domain name links, and not by IP address, or relative file structures. If you don't have DNS access, those links are as good as dead.

                              The best solution was the one suggested by you. Maintain a list of Public DNS servers located in different geographical areas.

                              Comment

                              Working...
                              X