Environment
Open Enterprise Server 2 SP2
Novell Linux DHCP Server OES2
Novell Open Enterprise Server 11 (OES 11) Linux
Novell Open Enterprise Server 11 (OES 11) Linux Support Pack 1
Novell Open Enterprise Server 11 (OES 11) Linux Support Pack 2
Situation
Setting up Dynamic DNS on an Open Enterprise Server
Resolution
Assume the following setup:
Subnet: 192.168.1.0 with Mask: 255.255.255.0
Range: 192.168.1.10-192.168.1.50
Domain Name: noname.com
Domain Server: 192.168.1.1
DHCP SETUP
The following instructions are for DHCP. Please see OES documentation for details:
- Create a service
- Create a DHCP Server object with the following two settings:
- ddns-rev-domainname in-addr.arpa
- ddns-update-style interim
- Create the following two zone objects:
- Zone Name: noname.com with DNS Server IP address of 192.168.1.1
-
Zone Name: 1.168.192.in-addr.arpa with DNS Server IP address of 192.168.1.1
-
NOTE: The zone names created here must match the zones names as they are found under DNS
-
- Create a subnet with the following settings:
- Subnet IP Address: 192.168.1.0
- Mask: 255.255.255.0
- View/Modify the newly created subnet and add noname.com for DNS Zone for Dynamic Update
- Create a Pool with the range specified at the beginning: Start of 192.168.1.10 and end of 192.168.1.50
- View/Modify the newly create Pool and change DNS Update to Always Update
DHCP configuration is complete.
DNS SETUP
The following instructions are for DNS. Please see the OES documentation for details:
- Create the following two DNS zones:
- noname.com
- An in-addr.arpa zone similar to this: 1.168.192.in-addr.arpa 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 1.168.192.in-addr.arpa zone).
- On each zone select the Control Lists tab and in the ALLOW UPDATE option. Add an entry of "any" in the filter (default is blank)
DNS Configuration is complete.
Test DDNS:- Start named (rcnovell-named start)
- Start dhcp (rcdhcpd start)
- 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="10.1.168.192.in-addr.arpa"
- For an A record: set ddns-fwd-name="workstation.noname.com"
Additional Information
If /var/log/messages doesn't show the dhcp server attempting to update the forward zone, but is working, or attempting to update the reverse zone only, then add the following flag to the settings of the DHCP Server object:
client-updates ignore;
By default this setting is set to allow, but when dns updates are set to interim, it can cause problems with forward zone updates.
The following setting, as found under windows, can also be disabled to work around this issue:
"Register this connection's addresses in DNS" checkbox found under the Microsoft network settings > Internet Protocol TCP/IP properties > Advanced > DNS tab.
dns-updates=true (default) is not needed in this situation because ddns-update-style is set to interim. In brief, setting dns-updates to false will disable DDNS withing a givin scope, but ddns-update-style=interim will allow DDNS updates to work for the configured subnet, pool, and zone. If DDNS updates occur for unconfigured zones, set ddns-updates=false and see if that resolves the issue.
Please note: Other settings with the ddns prefix should be used with care as they may cause undesired results. Setting ddns-hostname, for example, will give all ddns updates the hostname of whatever that value has been set to. When in doubt, ONLY set the settings recommended in the resolution section of this document.
