Add the search domain in resolv.conf

[pvasirani]

Hi,

Is it possible to add a second search domain in resolv.conf?

The hand-edited file works but, of course, is rewritten by the PFSense configurations.

Thanks in advance

[johnpoz]

@pvasirani do you have a use case example for this? I just having a hard time understanding to be honest why any search domain is even needed on pfsense.

When are you on pfsense looking up stuff and not using the fqdn in your query? Are you doing this so often that it makes sense have multiple search domains?

But if something you would like to see, you can always put in a feature request

[pvasirani]

@johnpoz
My "problem" is that 2 domains (Active Directory) access pfsense. Name resolution must check these two (internal) domains to "find" the correct resolution.

However, I fully agree that the FQDN must always be indicated, but it is not always available in the infrastructure.

Example of resolve.conf
nameserver 10.10.0.1
nameserver 10.20.0.2
search domain1.local
search domain2.local

[johnpoz]

@pvasirani still not getting what your looking to do..

The only time resolv.conf comes into play is if you were on the console of pfsense and looking for something via just host name..

How often are you on the console and trying to resolve just a hostname?

This does not come into play if some client is asking pfsense for dns..

[pvasirani]

@johnpoz Thanks for the explanation, if it works this way I think I won't need it.
Thank you

[johnpoz]

@pvasirani your clients asking pfsense for dns should have whatever search suffixes they want to use on themselves.

If you want unbound to ask specific NS your running locally on your network when a client asks for something, this would be setup in a domain override on unbound.