Project

General

Profile

Bug #71083

Plugin installation fails with DNS error when FreeNAS is configured as Active Directory DC

Added by Ben Smith 30 days ago. Updated 8 days ago.

Status:
Done
Priority:
No priority
Assignee:
Brandon Schneider
Category:
Middleware
Seen in:
Severity:
Medium
Reason for Closing:
Reason for Blocked:
Needs QA:
No
Needs Doc:
No
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

My FreeNAS server is configured as an Active Directory DC.

When I try to install any plugins the install fails at the DNS check with the message:

Install
[EFAULT] Exception: CallError:[EFAULT] pkg.cdn.trueos.org could not be reached via DNS, check your network occured, destroyed emby.

The underlying cause is resolv.conf on the server is pointing to 127.0.0.1, which I believe is correct for AD DC, but when this is copied into the jail obviously it cannot resolve anything.

There is an option to override the resolv.conf when creating a jail, but cannot see the same for plugins.

Workaround is to connect into the iocage jail and edit resolv.conf before the UI gets to checking access.


Related issues

Copied to FreeNAS - Bug #72057: Plugin installation fails with DNS error when FreeNAS is configured as Active Directory DCIn Progress

Associated revisions

Revision 7ef5b655 (diff)
Added by Brandon Schneider 26 days ago

fix(jail/create): If domaincontroller is enabled, use the forwarder

This only applies if they did not already specify their own resolver. If DC is not enabled, it will fall back to the default that is configured in iocage defaults (copy hosts by default, unless the user changed it.)

Ticket: #71083

Revision c4d10667 (diff)
Added by Brandon Schneider 26 days ago

tkt-71083: fix(jail/create): If domaincontroller is enabled, use the forwarder (#2472)

  • fix(jail/create): If domaincontroller is enabled, use the forwarder

This only applies if they did not already specify their own resolver. If DC is not enabled, it will fall back to the default that is configured in iocage defaults (copy hosts by default, unless the user changed it.)

Ticket: #71083

  • Address review

Revision 94f3a445 (diff)
Added by Brandon Schneider 26 days ago

fix(jail/create): If domaincontroller is enabled, use the forwarder

This only applies if they did not already specify their own resolver. If DC is not enabled, it will fall back to the default that is configured in iocage defaults (copy hosts by default, unless the user changed it.)

Ticket: #71083
(cherry picked from commit 7ef5b6557075295473ed978068c779073412fbf0)

History

#1 Updated by Dru Lavigne 30 days ago

  • Category changed from Plugins to Middleware
  • Assignee changed from Release Council to William Grzybowski

#3 Updated by William Grzybowski 29 days ago

  • Assignee changed from William Grzybowski to Brandon Schneider

#4 Updated by Brandon Schneider 26 days ago

  • Status changed from Unscreened to Closed
  • Target version changed from Backlog to N/A
  • Reason for Closing set to User Configuration Error
  • Needs QA changed from Yes to No
  • Needs Doc changed from Yes to No
  • Needs Merging changed from Yes to No

Ben: It's under Advanced -> Network, you can change the resolver there. It's delimited by ; which are translated to newlines when it's parsed, so you can treat it like a normal resolv.conf file in that regard.

Example: nameserver 8.8.8.8;nameserver 8.8.4.4

#5 Updated by Brandon Schneider 26 days ago

  • Status changed from Closed to In Progress
  • Target version changed from N/A to 11.2-U3
  • Severity changed from New to Medium
  • Reason for Closing deleted (User Configuration Error)
  • Needs QA changed from No to Yes
  • Needs Merging changed from No to Yes

Setting this open again as the jail plugin will try to be smarter about this as well.

#6 Updated by Bug Clerk 26 days ago

  • Status changed from In Progress to Ready for Testing

#7 Updated by Bug Clerk 26 days ago

  • Target version changed from 11.2-U3 to 11.3

#8 Updated by Bug Clerk 26 days ago

  • Copied to Bug #72057: Plugin installation fails with DNS error when FreeNAS is configured as Active Directory DC added

#9 Updated by Dru Lavigne 25 days ago

  • Target version changed from 11.3 to 11.3-BETA1
  • Needs Merging changed from Yes to No

#10 Updated by Dru Lavigne 8 days ago

  • Status changed from Ready for Testing to Done
  • Target version changed from 11.3-BETA1 to Master - FreeNAS Nightlies
  • Needs QA changed from Yes to No

Also available in: Atom PDF