Project

General

Profile

Actions
Copy link

Bug #3850

closed

Reverse dns zone not created for the entire subnet, if larger than /24

Added by Dominic Cleal almost 11 years ago. Updated almost 7 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Foreman modules
Target version:
-
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Description of problem:
Foreman only creates reverse zone file for first set of prefixes in a multi-prefixed subnet.

How reproducible:
Everytime

Steps to Reproduce:
1. Install Foreman in a provisioning configuration using a subnet that has multiple prefixes such as 10.1.0.0/23
2. Add a host to foreman with an ip address prefixed with 10.1.1.

Actual results:
Foreman errors with:
Create Reverse DNS record for INSERT_HOSTNAME_HERE task failed with the following error: 400 Bad Request

Additional info:
Adding a host using an address prefixed with 10.1.0 works fine.

After manually adding a reverse zone in the named configuration, adding a host to the higher prefixed addresses works.

Related issues 1 (0 open — 1 closed)

Has duplicate Installer - Feature #12066: Create all neccessary Reverse DNS FilesDuplicate10/06/2015Actions
Actions
Copy link

Also available in: Atom PDF