Project

General

Profile

Bug #1426

Foreman should not fail if dns domain has no SOA or NS records

Added by Ohad Levy about 11 years ago. Updated about 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Ohad Levy
Category:
DNS
Target version:
1.0
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

currently foreman tries to search the domain for its SOA or NS servers.
This is done in order to ask the relevant dns server (and not cached result).
if SOA or NS is not defined (or used via $ORIGIN for example) then foreman should not fail.

Related issues

Has duplicate Foreman - Bug #1430: Adding a new host in a subdomain that has no SOA or NS record failsDuplicate2012-01-05

Associated revisions

Revision 3c4db812 (diff)
Added by Ohad Levy about 11 years ago

fixes #1426 - Foreman should not fail if dns domain has no SOA or NS records

History

#1 Updated by Ohad Levy about 11 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF