In message <4e8f2e2c-7571-44dd-b012-57543debd...@ncartron.org>,
Nico Cartron wrote:
>Are you sure it's not your setup?
>I have plenty of dig running on FreeBSD (with bind-utils 9.14) and also
>Debian and they work just fine.
You know what? I think we may both be right.
Checking now, I think I
Are you sure it's not your setup?
I have plenty of dig running on FreeBSD (with bind-utils 9.14) and also Debian
and they work just fine.
--
Nico
> On 21 Jun 2019, at 09:14, Ronald F. Guilmette wrote:
>
> In message <9ba154cc-2272-46ec-a793-47ff31dca...@arin.net>, you wrote:
>
>> Hi Ronald,
In message <9ba154cc-2272-46ec-a793-47ff31dca...@arin.net>, you wrote:
>Hi Ronald,
>You usually need to reinstall packages and ports after you do a major
>version upgrade to FreeBSD.
I guess that I did not make myself clear. Everything on this system is
freshly installed, from scratch.
I have t
Hi Ronald,
You usually need to reinstall packages and ports after you do a major version
upgrade to FreeBSD.
pkg update && pkg upgrade
You should see bind-tools in the list. Version might stay the same but you’ll
be getting a different version, compiled against FreeBSD 12.
cheers,
—Matt
>
I just recently "upgraded" my old FreeBSD system to the latest, 12.0
release. Now, something that used to work doesn't seem to work anymore,
specifically "dig +trace" seems to no longer function at all.
Example:
% dig +trace -x 195
Harshith Mulky wrote:
>
> 1. How is Negative Caching Applied for other RCODES : FORMERR, SERVFAIL,
> REFUSED and NOTIMPL? What is the minimum TTL Value for these responses?
Good question: this isn't well specified. BIND has servfail-ttl (1s by
default) and lame-ttl (600s by default). The lame-ttl
Hello experts,
If a DNS server looks up a record and it's missing, it will often "negatively
cache" the fact that this record is missing, and not try to look it up again
for a while.
>From RFC 2308, Negative Caching of DNS Queries, I understood, the TTL for
>NXDOMAIN RCODE responses is taken fr
7 matches
Mail list logo
