Novell Cool Solutions

Setting up Dynamic DNS with OES2 SP2


April 30, 2010 2:55 pm





Settng up Dynamic DNS with OES2 SP2

Assume the following setup:

Subnet: with Mask: Name:

Reminder: TSIG Key is not supported at this time in OES 2 Novell-DNS.

The basic concept is that you are going to mirror your DNS Configuration to your DHCP Config and add a couple of settings that each service needs in order to function correctly. Once this is complete, all zones will update properly and your services will work flawlessly. Especially services like ZENworks Configuration Management.

I have attached two screen shots from the Management Console so you can see what I am talking about. Also, this document is updated in a frame of mind that you already have DNS/DHCP Configured, you are just trying to get Dynamic DNS working.


The following instructions are for DNS in iManager. Please see OES 2 documentation for details:

  1. Create a new zone OR Modify your existing Zones:
  2. An zone similar to this: zone (Type in the address normally in the boxes (192.168.1) leaving the last box blank. The application will complete the process to give you a zone). This
  3. Make sure your Root Zone is alive and well. This was created when you installed OES2 into the tree -RootServerInfo
  4. View/Modify each of the zones and click on NEXT until you see UPDATE FILTER. Add an entry of “any” in the filter (default is blank) – This is CRITICAL and a Show Stopper – ALL ZONES must have this setting applied.


The following instructions are for DHCP in iManager. However you can use the new DNS/DHCP Management Console. NOTE – Modify the properties of your DNS/DHCP Management Console Shortcut & add a -c o=org after the paren in the shortcut path. i.e. – “C:\Program Files\Novell\DNSDHCP\star.exe” -c o=org – This is telling the Management Console where your locator objects are in eDirectory.

  1. Modify your Existing DHCP Server object and add the following two settings: This probably already exists. Just add the settings.
    1. ddns-rev-domainname
    2. ddns-update-style interim
  2. Create the following two zone objects: Note – Your Zones will basically mirror the zones in your DNS Config – Configured below:
    1. Zone Name: with DNS Server IP address of

    2. Zone Name: with DNS Server IP address of – Remember, it matches your zone in DNS
  3. Create a subnet with the following settings:
    Subnet IP Address:

  4. View/Modify the newly created subnet and add for DNS Zone for Dynamic Update
  5. Create a Pool with the range specified at the beginning: Start of and end of – Your Pool is probably already there….
  6. View/Modify the newly create Pool and change DNS Update to Always Update
    DHCP configuration is complete.

Remember, you will need a zone in DHCP for each zone in DNS. Please see the screen shots below:

DNS Configuration is complete.

NOTE: If using XP, in the advance DNS configuration (on XP) uncheck the “Register this connection’s addresses in DNS” box

Test DDNS:

  1. Start named (rcnovell-named start)
  2. Start dhcp (rcdhcpd start)
  3. Release and renew dhcp leases from the workstation

If the setup is not working, check the following files:

  • /var/log/messages for error messages
  • /var/lib/dhcp/db/dhcpd.leases. Along with the lease information you should see:

    For a PTR record: set ddns-rev-name=””

    For an A record: set ddns-fwd-name=””
  • OR use your DNS/DHCP Management Console and watch the Zone Updates. You may beed to use the “Refresh Tree” button when you restart your services.

BTW this is an update to an existing Novell TID that is somewhat confusing to me. I hope this helps.


Norm O’Neal
2010 Novell Knowledge Partner

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.

Categories: Uncategorized


Disclaimer: This content is not supported by Novell. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.