(at least in Linux) suffixes the
original domain name with each item in the search list until the new
domain name resolves.
So this is regular behaviour and it explains the needless DNS queries.
AdguardHome uses the response code NXDOMAIN to signal the client "this
is a forbidden domain&qu
On 6/8/22, Greg Wooledge wrote:
> On Wed, Jun 08, 2022 at 12:56:52AM +, Lee wrote:
>> host and dig are non-standard. or use non-standard name lookups?
>> library??
>> In any case, try your example with ping or ssh - the search list will
>> be applied after the initial NXDOMAIN
>
> On Debian,
On Wed, Jun 08, 2022 at 12:56:52AM +, Lee wrote:
> host and dig are non-standard. or use non-standard name lookups? library??
> In any case, try your example with ping or ssh - the search list will
> be applied after the initial NXDOMAIN
On Debian, the canonical tool for performing generic ho
On 6/7/22, Tim Woodall wrote:
> On Tue, 7 Jun 2022, Greg Wooledge wrote:
>
>> On Tue, Jun 07, 2022 at 11:22:34AM -0400, Dan Ritter wrote:
>>>
>>> search Search list for host-name lookup. By default, the
>>> search
>>> [...]
>>> This may be changed by listing the desired domain
On Tue, 7 Jun 2022, Greg Wooledge wrote:
On Tue, Jun 07, 2022 at 11:22:34AM -0400, Dan Ritter wrote:
search Search list for host-name lookup. By default, the search
[...]
This may be changed by listing the desired domain search
path following the search keyword with spaces o
On 6/7/22, Darac Marjal wrote:
>
> On 07/06/2022 17:53, Greg Wooledge wrote:
>>
>> To the best of my knowledge, there isn't any setting to *prevent* the
>> appending of search domains to a name, no matter how many dots you put
>> in the name.
>
> I've wondered about that in the past. Is this maybe
On 07/06/2022 17:53, Greg Wooledge wrote:
On Tue, Jun 07, 2022 at 11:22:34AM -0400, Dan Ritter wrote:
search Search list for host-name lookup. By default, the search
[...]
This may be changed by listing the desired domain search
path following the search keyword with spaces
On Tue, Jun 07, 2022 at 11:22:34AM -0400, Dan Ritter wrote:
>
> searchSearch list for host-name lookup. By default, the
> search
> [...]
> This may be changed by listing the desired domain search
> path following the search keyword with spaces or tabs separating the
> name
On Tue, 7 Jun 2022, Dan Ritter wrote:
Dieter Rohlfing wrote:
Hello everybody,
When a client queries for a domain and the answer is NXDOMAIN, there is
immediately a second query with the original domain name, but suffixed
with the domain name of my home network.
Example:
1. query: www.example
Dieter Rohlfing wrote:
> Hello everybody,
>
> When a client queries for a domain and the answer is NXDOMAIN, there is
> immediately a second query with the original domain name, but suffixed
> with the domain name of my home network.
>
> Example:
>
> 1. query: www.example.com (result NXDOMAIN)
On Tue 07 Jun 2022 at 17:01:21 (+0200), Dieter Rohlfing wrote:
> When a client queries for a domain and the answer is NXDOMAIN, there is
> immediately a second query with the original domain name, but suffixed
> with the domain name of my home network.
>
> Example:
>
> 1. query: www.example.com (
Hello everybody,
I've installed AdguardHome to serve the clients in my home network.
After checking AdguardHome's query logs I noticed a lot of needless DNS
queries.
When a client queries for a domain and the answer is NXDOMAIN, there is
immediately a second query with the original d
12 matches
Mail list logo
