Project

General

Profile

Bug #67

no route to host error

Added by Matt Moran over 13 years ago. Updated over 13 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
External Nodes
Target version:
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

This occurs when the fqdn hostname has a '-' before the first '.'

So test01.company.local works, but test-01.company.local does not.

Fix is to replace the regex in config/routes.rb with :name => /(.+\.)+\w+/

Associated revisions

Revision 757a21ad (diff)
Added by Ohad Levy over 13 years ago

fixes #67 - no route to host error in external nodes

Revision d29e6b52 (diff)
Added by David Moreau-Simard over 6 years ago

Do not configure listen-on-v6 parameter if it's not set

The listen-on-v6 parameter would always be configured in
options.conf. This makes it unflexible with the use case of making
BIND listen on another port than 53.
Make it so the configuration is added only when the parameter is set
so that, if required, a user can set listen_on_v6 to false and add
his own configuration in additional_options.

Closes: #67

History

#1 Updated by Ohad Levy over 13 years ago

  • Target version set to 0.1-3

#2 Updated by Ohad Levy over 13 years ago

  • Status changed from New to Ready For Testing
  • % Done changed from 0 to 100

#3 Updated by Ohad Levy over 13 years ago

  • Status changed from Ready For Testing to Closed
  • Assignee changed from Matt Moran to Ohad Levy

Also available in: Atom PDF