Project

General

Profile

Actions

Bug #12779

open

Bogus domain generated for reverse DDNS when network mask is custom (not 24 16 or 8)

Added by Vyacheslav Kononenko 8 months ago. Updated about 2 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
DHCP (IPv4)
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
Affected Architecture:

Description

I have network with 192.168.100.0/23 which would include hosts from 192.168.100 and 192.168.101. In such configuration for DHCPv4 server DNS update reverse domain is generated as:

zone 100-101.168.192.in-addr.arpa. {
primary 192.168.100.4;
key "ddns-key";
}

This 100-101 domain is completely bogus and not used by DHCP daemon at all (with the same effect you could put string blahblah there), so it tries to push changes to reverse domains without key which leads to rejection and fail. It could be easily fixed manually if DHCP server config would support custom config section but there is somebody way to smart decided that nobody needs that for DHCP server. So current solution either make DNS server wide open to updates on reverse zone or manual modification of source code which generates config.


Related issues

Is duplicate of Bug #8179: Incorrect reverse DNS zone in DHCP server config for non-octet-aligned subnet maskResolvedRenato Botelho12/10/2017

Actions
Actions #1

Updated by Jim Pingle 8 months ago

  • Status changed from New to Duplicate

Duplicate of #8179

Actions #2

Updated by Jim Pingle 8 months ago

  • Is duplicate of Bug #8179: Incorrect reverse DNS zone in DHCP server config for non-octet-aligned subnet mask added
Actions #4

Updated by Azamat Khakimyanov about 2 months ago

  • Private changed from Yes to No
Actions #5

Updated by Jim Pingle about 2 months ago

  • Status changed from Assigned to New
  • Assignee deleted (Jim Pingle)
Actions

Also available in: Atom PDF