On 08/11/2017 02:40 PM, ToddAndMargo wrote:
On 08/10/2017 07:07 PM, Grant Taylor via bind-users wrote:
On 08/10/2017 06:21 PM, toddandmargo wrote:
Fedora 26
Fedora = Linux (vs Windows vs other)
I am stumped. I need to be able to look up short names on my local
network.
...
What am I
On 08/10/2017 07:07 PM, Grant Taylor via bind-users wrote:
On 08/10/2017 06:21 PM, toddandmargo wrote:
Fedora 26
Fedora = Linux (vs Windows vs other)
I am stumped. I need to be able to look up short names on my local
network.
...
What am I missing?
domain and / or search configuration
On 08/10/2017 10:18 PM, /dev/rob0 wrote:
Note that this still work for dig(1) and host(1) as per the OP's
examples. But things like ping(1) and browsers will work with a
search domain.
Do you mean to say that the search / domain entry in /etc/resolv.conf do
/not/ work for dig / host? (Or am
On Thu, Aug 10, 2017 at 08:07:00PM -0600,
Grant Taylor via bind-users wrote:
> On 08/10/2017 06:21 PM, toddandmargo wrote:
> > I am stumped. I need to be able to look up short names on my
> > local network.
> ...
> > What am I missing?
>
> domain and / or search configuration in
On 08/10/2017 06:21 PM, toddandmargo wrote:
> Fedora 26
Fedora = Linux (vs Windows vs other)
> I am stumped. I need to be able to look up short names on my local
> network.
...
> What am I missing?
domain and / or search configuration in /etc/resolv.conf
man resolv.conf
--
Grant. . . .
Appending suffixes to short names to make them legal DNS names, is considered
the responsibility of the *client*, not the *server*.
Look up “resolver search list” (more Unix-ish/Linux-ish) or “suffix search
list” (more Windows-ish), and you should find some useful information.
-
6 matches
Mail list logo
