On 9/15/14 7:04 AM, Lightner, Jeff wrote:
While the final dot has been required within zone files to prevent unwanted appendages to
records it has NOT been required by tools such as host and nslookup on either Windows or
Linux/UNIX which routinely use "search" domains.
On Windows the behavio
In article ,
Steven Carr wrote:
> Without the final explicit "." your name is not fully qualified.
Except in an email address where a trailing "." is illegal.
Sam
--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.
_
> ...
> > Heh thanks, yeah...initially I was erring on the side of caution and using
> > 9.9.x because it's served us well (~20k recursive clients without any
> > significant problems). Meanwhile we've been keeping a close eye on
> > community comments, and to be honest opinions wax and wane. Jus
Steven Carr schreef op 15-9-2014 om 4:07:
On 15 September 2014 02:56, Pieter De Wit wrote:
Is there any way we can reduce the memory footprint/optimize this any more ?
Look ups are really fast and not a problem, just reload time and memory
used.
Look into using an RPZ instead of individual zon
While the final dot has been required within zone files to prevent unwanted
appendages to records it has NOT been required by tools such as host and
nslookup on either Windows or Linux/UNIX which routinely use "search" domains.
As I noted this is something that seems to have changed recently.
* Barry Margolin [2014-09-15 15:18]:
> In article ,
> Steven Carr wrote:
>
> > On 15 September 2014 13:29, Lightner, Jeff wrote:
> > > I've begun seeing this recently in nslookup on Windows workstations as
> > > well.It appears it is appending search domains even when I've
> > > specifie
In article ,
Steven Carr wrote:
> On 15 September 2014 13:29, Lightner, Jeff wrote:
> > I've begun seeing this recently in nslookup on Windows workstations as
> > well.It appears it is appending search domains even when I've specified
> > an FQDN. That is I have two search domains such
On 15 September 2014 13:29, Lightner, Jeff wrote:
> I've begun seeing this recently in nslookup on Windows workstations as well.
> It appears it is appending search domains even when I've specified an FQDN.
> That is I have two search domains such as ex1.com and ex2.net and I typed
> short
I've begun seeing this recently in nslookup on Windows workstations as well.
It appears it is appending search domains even when I've specified an FQDN.
That is I have two search domains such as ex1.com and ex2.net and I typed short
name "ralph" for nslookup or host it would give me "ralph.
...
> Heh thanks, yeah...initially I was erring on the side of caution and using
> 9.9.x because it's served us well (~20k recursive clients without any
> significant problems). Meanwhile we've been keeping a close eye on
> community comments, and to be honest opinions wax and wane. Just as I
> t
Partially qualified names are DANGEROUS. You realy do not want
to use them ever no matter how convient or useful they appear to be.
In message <20140915083532.ga29...@danton.fire-world.de>, Sebastian Wiesinger w
rites:
> Hello,
>
> I noticed a change in the host tool in regard to how searches a
Hello,
I noticed a change in the host tool in regard to how searches are done
when there are >= "ndots" dots in the query. In the following case
ndots is always nonexistant in the configuration.
With bind 9.8 (Debian 1:9.8.4.dfsg.P1):
$ host -d test.example
Trying "test.example"
Received 105 byt
12 matches
Mail list logo
