NC DNS Updater Changelog

Read about the project here.

NC DNS Updater Install Package

Use NC DNS Updater Install Package to setup NC DNS Updater on you Mac OS X and start updating your Namecheap dynamic domains automatically.


NC DNS Updater v2.2 – Released 2015-05-29

Minor update. Just some network code optimization.

NC DNS Updater v2.1 – Released 2015-01-28

This is a major milestone for NC DNS Updater, because it includes two of the most requested features: install package and execution as a daemon.

This is probably the last major release before NC DNS Updater goes to the Mac App Store. Enjoy!

IMPORTANT NOTE: It’s advised that any previous versions of the app are deleted prior to installing this release.

  • New Feature: Now the app is distributed via Installation Package.
  • New Feature: Runs as a daemon. This is a major improvement, because now IP updates are executed without the need of a logged in user. Also, the app doesn’t have to be running all the time, it just serves as a settings window for configuring the hosts and parameters.
  • New Feature: Improved activity logging.
  • Bug Fix: Fixed a bug in updating “@” hosts.
  • Bug Fix: Fixed a bug where the current IP wasn’t correctly shown after an update request was issued.

NC DNS Updater v1.9 – Released 2015-01-21

  • New Feature: Updates are no longer interval based. Now the updates occur on-demand when an IP change is detected.
  • New Feature: UI refinements for better user experience.
  • New Feature: Detailed information about host update status.
  • Bug Fix (Thanks to all the users that helped track these bugs down!): Fixed some app crashing bugs introduced in previous releases. This release is significantly more stable.

NC DNS Updater v1.8 – Released 2015-01-19

  • New Feature: Better error handling and logging.
  • New Feature: Handle Namecheap’s response to update request.
  • Bug Fix: Fixed some app crashing bugs.

NC DNS Updater v1.7 – Released 2015-01-12

IMPORTANT NOTE: If upgrading from v1.4, it may be necessary to delete the contents of folder ~\Library\Application Support\com.laratech.NC_DNS_Updater. To do so, run the following command in terminal:

rm -d -r ~/Library/Application\ Support/com.laratech.NC_DNS_Updater/

This update contains a lot of user requested features. I would like to thank Raymond Othenin-Girard and Brandon Jones for the feedback they have provided and the attention they have given to the app.

  • New Feature (user requested – Thanks Raymond): The host’s status indicator now shows if the IP update has propagated:
    • RED = host is disabled and won’t be updated;
    • ORANGE = host update is enabled, but the update hasn’t taken effect yet;
    • GREEN = The IP update has propagated.
  • New Feature (user requested – Thanks Raymond): App launches silently and no window opens if it has a valid configuration. At first launch or if there’s no valid configuration, the app opens the settings window.
  • Feature Improvement (user requested – Thanks Raymond): Overall UI improvements. The switches are now clearer as to their current state (ON/OFF).
  • Bug Fix (Thanks Brandon): Overall typo correction in app and website.

NC DNS Updater v1.6 – Released 2015-01-05

  • Bug Fix: Fixed issue with saving/deleting domains.

NC DNS Updater v1.5 – Released 2014-12-12

  • New Feature (user requested – Thanks Raymond): Allow updating the domain with external (internet) or internal (network) IP address.
  • Bug Fix: Minor bug fixes.

15 comments

  1. Eric says:

    Love your DNS updater, have been using it on my MacBook Pro and it works great.

    Is there any way you could compile this so it runs on OS X 10.7.5 Lion, or does it rely on some stuff only available in Mountain Lion on up? I have a Mac mini I’m using as a server that I would like to use this on instead of my MBP, and the latest OS X the mini will run is 10.7.5. It would be great if it could work on Lion too.

    Thanks.

  2. JSmythe says:

    Hi Spencer,
    Just had to reboot my computer and ended up having to replace my settings in your DNS client and in the name cheap domain A records. Name cheap has a new web interface, launched recently which is hard to negotiate. When I got a new password and placed it into your DNS client, it kept returning an error message that “password does not match”. I have changed passwords and repeated a number of times without success. I am clipping and pasting the password. Any thoughts???? Thanks in advance for your help!

    • spencerdiniz says:

      Hi… Please, make sure you are using the dynamic dns password (secret) and NOT the namecheap account password. Second, try typing the password instead of copy/paste. Some people have told me that copy/paste didn’t work, but typing did.

      Let me know how it goes.

      • JSmythe says:

        Yes. I have been using the secret password and refreshing and trying new ones to no avail. I also tried with writing the passwords in but it continues to state mismatches passwords.

        I tried to remove the past programs. Is it possible i need to delete some part more?

  3. Sterling says:

    Thanks so much for this, it saved me a ton of headache!

  4. Pam says:

    This looks like what I need. It looks very clean and easy to use… if you know what information goes in which blanks. The terminology used on namecheap does not seem to match up with Name, Host, Domain…. So I have it only partly working.
    on namecheap:
    subdomain: mycomputer… is this Host?
    title on page domain: mydomain.com…. is this Name?
    This is all really baffeling but somehow the external IP seems to be propagated back to the right place. I am showing the orange status light so here is the last minutes of the log:
    [12:00:59.81] Processing mycomputer.colemantax.com.
    [12:00:59.81] Determining external IP address.
    [12:01:00.00] External IP address is 70.138.137.95.
    [12:01:00.00] Requesting IP address update for mycomputer.colemantax.com to 70.138.137.95.
    [12:01:00.00] Current IP for mycomputer.colemantax.com is 127.0.0.1.
    [12:01:00.36] Successfully updated mycomputer.colemantax.com to 70.138.137.95.
    [12:01:00.36] Update request issued successfully. Please wait for update to propagate.
    [12:02:14.54] Loading domain configuration.
    [12:02:14.54] Domain configuration loaded successfully.
    [12:02:14.54] Master Switch enabled. Processing domains.
    [12:02:15.00] mycomputer.colemantax.com IP is outdated. Update request will be issued.
    [12:02:15.00] Processing mycomputer.colemantax.com.
    [12:02:15.00] Determining external IP address.
    [12:02:15.17] External IP address is 70.138.137.95.
    [12:02:15.17] Requesting IP address update for mycomputer.colemantax.com to 70.138.137.95.
    [12:02:15.18] Current IP for mycomputer.colemantax.com is 127.0.0.1.
    [12:02:15.55] Successfully updated mycomputer.colemantax.com to 70.138.137.95.
    [12:02:15.55] Update request issued successfully. Please wait for update to propagate.
    [12:03:29.59] Loading domain configuration.
    [12:03:29.59] Domain configuration loaded successfully.
    [12:03:29.59] Master Switch enabled. Processing domains.
    [12:03:30.10] mycomputer.colemantax.com IP is outdated. Update request will be issued.
    [12:03:30.10] Processing mycomputer.colemantax.com.
    [12:03:30.10] Determining external IP address.
    [12:03:30.26] External IP address is 70.138.137.95.
    [12:03:30.26] Requesting IP address update for mycomputer.colemantax.com to 70.138.137.95.
    [12:03:30.27] Current IP for mycomputer.colemantax.com is 127.0.0.1.
    [12:03:30.63] Successfully updated mycomputer.colemantax.com to 70.138.137.95.
    [12:03:30.63] Update request issued successfully. Please wait for update to propagate.

    • spencerdiniz says:

      Hi,

      I agree, the terminology used in the app should better match Namecheap’s. I’ll consider it for a future upgrade. Meanwhile, this might help:

      NAME: Put here a descriptive name. This has no effect on the update process. It’s just a way for you to easily identify it.
      HOST: Put here the subdomain. For example, in mail.someserver.com, “mail” is the HOST.
      DOMAIN: Put here the domain name. For example, in mail.someserver.com, “some server.com” is the DOMAIN.
      PASSWORD: Put here the password generated by Namecheap in the Dynamic DNS section of the domain configuration page.
      IP SOURCE: Choose whether you want to update the host with the internal (network) IP or external (internet) IP.
      ENABLE: Choose whether automatic updates are enabled (checked) or disabled (unchecked).

      MASTER SWITCH: Choose whether automatic updates are ON or OFF. Essentially, if the App is ON or OFF. Think of it as a global ON/OFF switch.

      As for how the status lights work:

      RED: Updates are turned off.
      ORANGE: Updates are turned on, but domain’s IP doesn’t match the detected IP yet. Essentially, an update request was issued and it should be a matter of time for it to propagate.
      GREEN: Updates are turned on and the domain’s current IP matches the detected IP. Essentially, IP update has propagated.

      Each domain is checked once every minute. If the domain’s IP is the same as the detected IP, no update request is issued. If it’s different than the detected IP, an update request is issued. The time the update takes to effectively propagate dependes on the TTL value you set for the host in Namecheap’s host records configuration page.

      I hope this helps clear thinks up a bit. Let me know if you’re still having issues.

  5. Kelly Bell says:

    Here’s the log (but it’s not very revealing – just “passwords don’t match” over and over again:
    [15:27:01.50] Current IP for books.yarnspotting.com is 216.161.93.98.
    [15:27:05.75] ERROR OCCURRED WHEN UPDATING books.yarnspotting.com to 192.168.0.110: Passwords do not match
    [15:27:05.75] Passwords do not match
    [15:28:15.88] Loading domain configuration.
    [15:28:15.88] Domain configuration loaded successfully.
    [15:28:15.88] Master Switch enabled. Processing domains.
    [15:28:16.72] books.yarnspotting.com IP is outdated. Update request will be issued.
    [15:28:16.72] Processing books.yarnspotting.com.
    [15:28:16.72] Determining internal IP address.
    [15:28:16.72] Internal IP address is 192.168.0.110.
    [15:28:16.72] Requesting IP address update for books.yarnspotting.com to 192.168.0.110.
    [15:28:16.72] Current IP for books.yarnspotting.com is 216.161.93.98.
    [15:28:19.35] ERROR OCCURRED WHEN UPDATING books.yarnspotting.com to 192.168.0.110: Passwords do not match
    [15:28:19.35] Passwords do not match

    • spencerdiniz says:

      Hi, Kelly.

      I’m sorry I took so long to write back. Somehow you’re comment was flagged as SPAM. Anyway…
      The PASSWORD should be the one that Namecheap generates in the “Dynamic DNS” section (under Miscellaneous) in the domain configuration page. It’s 32 characters long.
      Let me know if you’re having trouble finding it so I can help you out.

      Thanks for the feedback!

  6. Kelly Bell says:

    I used the old version with no trouble. Just upgraded to new version, but am using on DIFFERENT machine (I’ve transferred the server content I’m hosting to the new machine). I deactivated the old app on my old machine.

    I am getting an error that says the passwords don’t match, but I know FOR A FACT that they DO (assuming the password you’re asking for is my namecheap password – but even if it isn’t, I tried every OTHER logical option as well, and none work). What’s going on? I never had any trouble with the old version, either in setup or in execution, but I can’t get the new one to work at all. Please help?

    PS I LOVE LOVE LOVE your app – thank you for the great work!!

    Thanks,
    Kelly

  7. JSmythe says:

    Love Love Love your NC DNS Updater! Looked high and low for something like this as NC did not provide it.

    Question on your latest version 2.1 which I installed recently. Why is my host status indicator always on orange (just like your example with the external ip)???? Is it working and updating my ip? do I need it to be green? How do I make it green? Thanks for your answer and please keep up the great work!

    • spencerdiniz says:

      Hi!

      Thanks for taking the time to write!

      The status indicator should go green once the host’s IP matches what the app detects as the internal or external IP.

      The time it takes to go green depends mainly on the a TTL time you have setup for the host.

      If it doesn’t go green after a while, enable logging and let the app run for about 3 min, then send me the log so I can check if everything is OK.

Leave a Reply

Your email address will not be published. Required fields are marked *