Project

General

Profile

Feature #23544

Allow up to 6 additional domains in DNS search directive

Added by Christopher Pallone over 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Important
Assignee:
William Grzybowski
Category:
Middleware
Target version:
Estimated time:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
No
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:

Description

Please allow up to six domain names up to 256 characters total in the resolver configuration file. This will help prevent multiple logging notifications and reverse lookup failures at sites managing multiple domains.

addtional-domains.png (25.4 KB) addtional-domains.png Nick Wolff, 11/11/2017 07:43 PM
13018

Related issues

Related to FreeNAS - Bug #26912: Don't require reboot when adding additional DNS domainsDone

Associated revisions

Revision 7448de1f (diff)
Added by Nikola Gigic over 1 year ago

feat(gui): up to 6 additional domains with 256 char length

Ticket: #23544

Revision 30b4be1a (diff)
Added by Nikola Gigic over 1 year ago

feat(gui): up to 6 additional domains with 256 char length - migration file

Ticket: #23544

Revision 67eb1973 (diff)
Added by Nikola Gigic over 1 year ago

feat(gui): up to 6 additional domains with 256 char length - migration file

Ticket: #23544

Revision 0bedda46 (diff)
Added by Nikola Gigic over 1 year ago

feat(gui): up to 6 additional domains with 256 char length - migration file

Ticket: #23544

Revision 9ac768bb (diff)
Added by Nikola Gigic over 1 year ago

feat(gui): up to 6 additional domains with 256 char length
Ticket: #23544

Revision b958ad82 (diff)
Added by Nikola Gigic over 1 year ago

feat(gui): up to 6 additional domains with 256 char length
Ticket: #23544

Revision 35715f26 (diff)
Added by Nikola Gigic over 1 year ago

feat(gui): up to 6 additional domains with 256 char length (#290)

feat(gui): up to 5 additional domains with 256 char length

Ticket: #23544

Revision 1caf3977 (diff)
Added by Nikola Gigic over 1 year ago

feat(gui): up to 6 additional domains with 256 char length (#290)

feat(gui): up to 5 additional domains with 256 char length

Ticket: #23544

Revision 44b76c71 (diff)
Added by Dru Lavigne about 1 year ago

Add new Additional domains field.
Ticket: #23544

Revision be582650 (diff)
Added by William Grzybowski about 1 year ago

fix(gui): additional domains parsing

Ticket: #23544

Revision 25350666 (diff)
Added by William Grzybowski about 1 year ago

fix(gui): additional domains parsing

Ticket: #23544
(cherry picked from commit be5826504237e6d46013b4ecf98acd8e7159cde4)

History

#1 Updated by William Grzybowski over 1 year ago

  • Status changed from Unscreened to 15

How is that helpful within FreeNAS?

It strikes me at odd someone would like multiple search domains within a NAS.

Care to elaborate a bit?

#2 Updated by Sam Fourman over 1 year ago

This client is a TrueNAS customer. (Filing a FreeNAS bug so they can track it)
Support suite ticket EVJ-544-21918

#3 Updated by Sam Fourman over 1 year ago

6 domains looks reasonable, however not sure about the 256 characters

From include/resolv.h :

/*% * Global defines and variables for resolver stub.
/
#define MAXNS 3 /
< max # name servers we'll track /
#define MAXDFLSRCH 3 /
< # default domain levels to try /
#define MAXDNSRCH 6 /
< max # domains in search path /
#define LOCALDOMAINPARTS 2 /
< min levels in name that is "local" /
#define RES_TIMEOUT 5 /
< min. seconds between retries /
#define MAXRESOLVSORT 10 /
< number of net to sort on /
#define RES_MAXNDOTS 15 /
< should reflect bit field size /
#define RES_MAXRETRANS 30 /
< only for resolv.conf/RES_OPTIONS /
#define RES_MAXRETRY 5 /
< only for resolv.conf/RES_OPTIONS /
#define RES_DFLRETRY 2 /
< Default #/tries. /
#define RES_MAXTIME 65535 /
%< Infinity, in milliseconds. */

#4 Updated by William Grzybowski over 1 year ago

  • Target version set to 11.1

#5 Updated by Ash Gokhale over 1 year ago

  • Target version deleted (11.1)

Expressing the correct syntax for multiple search entries is a valid request; it's present in freebsd and many enterprises have mixed DNS namespaces that require it. The current implementation uses exactly one entry from the domain field; while convenient, is a simplification that is not necessarily correct or useful to real use cases. Unfortunately we have no ORM structure to store this additional list of namespaces. A migration may be required.

#6 Updated by Ash Gokhale over 1 year ago

  • Target version set to 11.1

#7 Updated by William Grzybowski over 1 year ago

Ash Gokhale wrote:

Expressing the correct syntax for multiple search entries is a valid request; it's present in freebsd and many enterprises have mixed DNS namespaces that require it. The current implementation uses exactly one entry from the domain field; while convenient, is a simplification that is not necessarily correct or useful to real use cases. Unfortunately we have no ORM structure to store this additional list of namespaces. A migration may be required.

I am not questioning what it does neither implementation implications/design decisions/tips.
I am simply trying to understand why its so important for a NAS to have multiple search domains.
This does not seem to be of relevant importance given this is the first request we have had in 6+ years? I understand the mixed DNS namespaces point but is this a deal breaker? Is it worth the extra complexity in the UI?

Guess I just want to be sold on why we need this.

#8 Updated by Christopher Pallone over 1 year ago

The reason I requested the option is to simplify host specific exports. We manage a number of domains and host specific exports require FQDNs to prevent logging noise and permission problems when the NAS domain does not match a client server.
Also, please understand this is only a feature request, and you will not hurt my feelings if it is not implemented. It can be resolved by forcing FQDNs when exporting to a specific set of hosts. This might even be a simple test to add as part of the export process. If I was the only admin, this would be a non issue. With the domain search capability a standard, many other admins assume (i know...) they can use short name lookups for anything.

#9 Updated by William Grzybowski over 1 year ago

  • Status changed from 15 to Screened

Christopher Pallone wrote:

The reason I requested the option is to simplify host specific exports. We manage a number of domains and host specific exports require FQDNs to prevent logging noise and permission problems when the NAS domain does not match a client server.
Also, please understand this is only a feature request, and you will not hurt my feelings if it is not implemented. It can be resolved by forcing FQDNs when exporting to a specific set of hosts. This might even be a simple test to add as part of the export process. If I was the only admin, this would be a non issue. With the domain search capability a standard, many other admins assume (i know...) they can use short name lookups for anything.

Understood, thank you for the detailed explanation. We will take it into consideration.

#10 Updated by William Grzybowski over 1 year ago

  • Status changed from Screened to Unscreened
  • Assignee changed from William Grzybowski to Nikola Gigic

#11 Updated by Nikola Gigic over 1 year ago

  • Status changed from Unscreened to Screened

#12 Updated by William Grzybowski over 1 year ago

  • Status changed from Screened to Ready For Release

#13 Updated by Dru Lavigne over 1 year ago

  • Subject changed from Please allow multiple domains in resolv.conf search directive to Allow up to 6 additional domains in DNS search directive

#14 Updated by Dru Lavigne about 1 year ago

  • Target version changed from 11.1 to 11.1-BETA1

#15 Updated by Dru Lavigne about 1 year ago

  • Status changed from Ready For Release to Resolved

#16 Updated by Nick Wolff about 1 year ago

  • File addtional-domains.png addtional-domains.png added
  • Status changed from Resolved to Unscreened
  • Target version changed from 11.1-BETA1 to 11.1
  • QA Status Test Fails FreeNAS added
  • QA Status deleted (Not Tested)
13018

When I try to add any amount of additional domains it tells me that I can only add 5 additional ones even though I'm below that limit.

Picture attached

#17 Updated by William Grzybowski about 1 year ago

  • Status changed from Unscreened to Screened
  • Assignee changed from Nikola Gigic to William Grzybowski
  • QA Status Not Tested added
  • QA Status deleted (Test Fails FreeNAS)

#18 Updated by William Grzybowski about 1 year ago

  • Status changed from Screened to Needs Developer Review
  • Assignee changed from William Grzybowski to Vladimir Vinogradenko

#19 Updated by Vladimir Vinogradenko about 1 year ago

  • Status changed from Needs Developer Review to Reviewed by Developer
  • Assignee changed from Vladimir Vinogradenko to William Grzybowski

#20 Updated by William Grzybowski about 1 year ago

  • Status changed from Reviewed by Developer to Ready For Release

#21 Updated by Dru Lavigne about 1 year ago

  • Target version changed from 11.1 to 11.1-RC2

#22 Updated by Nick Wolff about 1 year ago

  • Needs QA changed from Yes to No
  • QA Status Test Passes FreeNAS added
  • QA Status deleted (Not Tested)

Test passes

Additional note while dhcp is set additional domains requires a reboot to apply after saving. I believe that is a separate issue. Applies immediately on save when using static ip as expected

#23 Updated by Dru Lavigne about 1 year ago

  • Related to Bug #26912: Don't require reboot when adding additional DNS domains added

#24 Updated by Dru Lavigne about 1 year ago

  • Target version changed from 11.1-RC2 to 11.1-RC3

#25 Updated by Dru Lavigne about 1 year ago

  • Status changed from Ready For Release to Resolved

Also available in: Atom PDF