DHCP client fails to resolve an IP address from a reverse zone due to a wrongly created dynamic PTR Resource Record

  • 7012548
  • 04-Jun-2013
  • 04-Jun-2013

Environment

Novell Open Enterprise Server 11 (OES 11) Linux Support Pack 1

Situation

Cannot resolve IP address to host name of DHCP Clients
 
dhcpd creates invalid PTR Resource Records in reverse zone
 

Resolution

A temporary workaround to the problem is to explicitly configure the statement 'ddns-rev-domainname "in-addr.arpa"', which makes dhcpd update the PTR Resource Records in the reverse zone correctly.
 
The statement can be configured using the DNS/DHCP java console by selecting the DHCP server object at the bottom and editing the option under the Settings tab.
 
Please restart dhcpd after having saved the change.

Cause

Investigation reveals that the dhcp server appends all bytes in front of "in-addr.arpa" of a configured reverse zone declaration to the reversed IP address of a dynamic allocation that matches the configured reverse zone declaration with dynamic updates of the PTR Resource Record.

For example, when the IP address of a dynamic allocation is 10.1.111.222 and the configured reverse zone is "10.in-addr.arpa", then dhcpd will make a dynamic update to add PTR Resource Record "222.111.1.10.10.in-addr.arpa." instead of "222.111.1.10.in-addr.arpa.".

Feedback service temporarily unavailable. For content questions or problems, please contact Support.