Clayton's Tech Bits

Home

Contact

Resumé / C.V.

Links

Search this site:
Custom Search

Categories:

/ (224)
  Admin/ (86)
    Apache/ (7)
      HTTPS-SSL/ (4)
    Cherokee/ (1)
    LAN/ (4)
    LVM/ (3)
    Monitoring/ (2)
      munin/ (2)
    OpenVPN/ (1)
    SSH-Proxy/ (3)
    SSH-SSL/ (6)
    backups/ (16)
      SpiderOak/ (1)
      backuppc/ (5)
      dirvish/ (1)
      misc/ (6)
      rdiff-backup/ (1)
      rsync/ (1)
      unison/ (1)
    commandLine/ (11)
    crontab/ (1)
    databases/ (8)
      MSSQL/ (2)
      MySQL/ (5)
      PostgreSQL/ (1)
    dynamicDNS/ (2)
    email/ (9)
      Dovecot/ (1)
      deliverability/ (1)
      misc/ (1)
      postfix/ (6)
    iptables/ (2)
    virtualization/ (8)
      VMware/ (1)
      virtualBox/ (7)
  Coding/ (11)
    bash/ (1)
    gdb/ (1)
    git/ (2)
    php/ (4)
    python/ (3)
      Django/ (1)
  Education/ (1)
  Hosting/ (23)
    Amazon/ (14)
      EBS/ (3)
      EC2/ (11)
    Godaddy/ (2)
    NearlyFreeSpeech/ (3)
    Rackspace/ (1)
    vpslink/ (3)
  Linux/ (20)
    Awesome/ (3)
    CPUfreq/ (1)
    Chinese/ (1)
    Debian/ (5)
      WPA/ (1)
    audio/ (1)
    encryption/ (2)
    fonts/ (1)
    misc/ (4)
    router-bridge/ (2)
  SW/ (39)
    browser/ (2)
      Chrome/ (1)
      Firefox/ (1)
    business/ (25)
      Drupal/ (8)
      KnowledgeTree/ (6)
      Redmine/ (2)
      SugarCRM/ (6)
      WebERP/ (2)
      eGroupware/ (1)
    email/ (1)
    fileSharing/ (1)
      mldonkey/ (1)
    graphics/ (2)
    research/ (2)
    website/ (6)
      blog/ (6)
        blosxom/ (3)
        rss2email/ (1)
        webgen/ (1)
  Security/ (12)
    IMchat/ (1)
    circumvention/ (2)
    e-mail/ (4)
    greatFirewall/ (1)
    hacking/ (1)
    password/ (1)
    privacy/ (1)
    skype/ (1)
  Services/ (1)
    fileSharing/ (1)
  TechWriting/ (1)
  xHW/ (13)
    Lenovo/ (1)
    Motorola_A1200/ (2)
    Thinkpad_600e/ (1)
    Thinkpad_a21m/ (3)
    Thinkpad_i1300/ (1)
    Thinkpad_x24/ (1)
    USB_audio/ (1)
    scanner/ (1)
    wirelessCards/ (2)
  xLife/ (17)
    China/ (9)
      Beijing/ (5)
        OpenSource/ (3)
    Expatriation/ (1)
    Vietnam/ (7)

Archives:

  • 2012/03
  • 2012/01
  • 2011/12
  • 2011/11
  • 2011/10
  • 2011/09
  • 2011/08
  • 2011/07
  • 2011/06
  • 2011/05
  • 2011/04
  • 2011/02
  • 2010/12
  • 2010/11
  • 2010/10
  • 2010/09
  • 2010/08
  • 2010/07
  • 2010/06
  • 2010/05
  • 2010/04
  • 2010/03
  • 2010/02
  • 2010/01
  • 2009/12
  • 2009/11
  • 2009/10
  • 2009/09
  • 2009/08
  • 2009/07
  • 2009/06
  • 2009/05
  • 2009/04
  • 2009/03
  • 2009/02
  • 2009/01
  • 2008/12
  • 2008/11
  • 2008/10
  • 2008/09
  • Subscribe XML RSS Feed

    Tue, 21 Oct 2008


    /Admin/dynamicDNS: Dynamic DNS Basics

    You already have a broadband internet account at home, you have some unused hardware laying around, you know how to setup and configure a server, so why not save a few bucks and run your server at home?:

    So if you are not intending on using an e-mail server on your server at home, and whatever service(s) you were planning on providing (website?) can absorb a little downtime from power and ISP outages, it is a go. Especially if you want to run some very particular software that is not commonly available from cheap hosting services, leaving you with the relatively more expensive option of renting your own server.

    Dynamic DNS is really very simple. Computers understand numeric IP[4] ("Internet Protocol") addresses of the form 111.222.333.444. Humans understand alphanumeric internet addresses of the form www.myname.com. When you type www.myname.com into your web browser (or any other network application) www.myname.com must be pointing at the correct 111.222.333.444 for it to work. That is all DNS ("Domain Name Service") really is. "Dynamic DNS" just refers to the situation where the numeric IP address changes frequently, and the slightly specialized methods used to keep www.myname.com and 111.222.333.444 in sync when this is the case.

    In your home, you will be faced with two general options:

    Why would you want the added complication of the second option? Because somewhere on your network you must run a piece of software that will update www.myname.com with the new 111.222.333.444 whenever the latter changes. That piece of information is a property of the network interface that is directly connected to the internet, located on your router. If you are using a commercial off-the-shelf router, that information can be hard or impossible to extract from it. Some routers are pre-configured to talk to certain Dynamic DNS providers, and maybe some of them actually work in this role. I have so far not been so lucky as to find one that does. If the router is your own machine, whose hardware and software you have complete control of, everything tends to be a bit easier.

    That said, if you are sharing an internet connection, you might not have a choice in the router department.....

    Just to be clear, while probably achieving the opposite, the usual way to tell your Dynamic DNS service that you have a new numeric IP address is to send it a very simple message using http, and that message AUTOMATICALLY must contain your current public IP address (your new numeric address). The Dynamic DNS service then just strips this new IP out of the message. The complication is, most Dynamic DNS services do not want you to waste their resources by sending them this http message every two minutes. Most will freeze your account if you do. They want to hear from you only when the address really has changed, which is why the Dynamic DNS software client running on your network must know when your IP address changes, so that it then will know it is time to tickle the Dynamic DNS service provider.

    [1] http://en.wikipedia.org/wiki/Dynamic_ip
    [2] http://en.wikipedia.org/wiki/Dynamic_DNS
    [3] http://blog.langex.net/index.cgi/Admin/LAN/build-your-own-router.html
    [4] http://en.wikipedia.org/wiki/Ip_address

    posted at: 11:30 | path: /Admin/dynamicDNS | permanent link to this entry