Project

General

Profile

Bug #1544

Updating a host fails if you cannot reach the SOA nameservers

Added by Ashley Penney over 7 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
DNS
Target version:
Difficulty:
easy
Triaged:
No
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

We encountered an issue with updating and changing hosts through foreman and after a lengthy debugging session with Ohad we tracked it down to an issue where the foreman server cannot reach the SOA servers for a domain to check DNS.

This is similar to #1426 but in our use case the SOA records do exist but are blocked off, network wise, from the foreman server. We have temporarily fixed this by removing code from def resolver in app/models/domain.rb

For now we're using:

def resolver
ns = nameservers
Resolv::DNS.new
end

But we'd like a setting of some kind to toggle between reaching out to the SOAs and just relying on the system configured resolvers. We also discussed perhaps having a timeout value that falls back on using local resolvers (but should ideally display some kind of error in the UI so people are aware of what happened - otherwise they will just think 1 minute updates are normal).

Associated revisions

Revision 1f03a563 (diff)
Added by Ohad Levy about 7 years ago

fixes #1544 - Updating a host fails if you cannot reach the SOA nameservers

History

#1 Updated by Ashley Penney over 7 years ago

I just want to confirm this is still an issue in 0.5.

#2 Updated by Ohad Levy over 7 years ago

  • Target version set to 1.0

#3 Updated by Ohad Levy over 7 years ago

this should be extracted to a new setting

#4 Updated by Ohad Levy over 7 years ago

  • Difficulty set to easy

#5 Updated by Ohad Levy about 7 years ago

  • Category set to DNS
  • Assignee set to Ohad Levy

#6 Updated by Ohad Levy about 7 years ago

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

Also available in: Atom PDF