Re: Understanding TTL in "rndc dumpdb"-output

2018-10-23 Thread Michał Kępień
> After querying my resolver for "testbla11.example.com", I receive a NXDOMAIN > response with a minimum-ttl (in the soa) of 3600. > When I afterwards dump the cache of my resolver (9.12.2-P1) with "rndc > dumpdb" and look for the negative ttl, then a value much bigger than 3600 is > shown (608363)

Strange DIG behavior on Windows 10:

2018-10-23 Thread Timothy Metzinger
I have two windows 10 pro boxes, both with Bind 9.12.3 tools installed. On one machine, entering "dig" by itself gives me back the root server list as expected. On the other machine, I get an error that says no name servers could be contacted. However, if I specify the local name server on t

Re: Strange DIG behavior on Windows 10:

2018-10-23 Thread Kevin Darcy
To be honest, I don't have a lot of experience running dig on Windows, but I assume it would use the same resolvers as everything else, in which case they're either statically defined (typically through Control Panel) or assigned via DHCP. One thing to consider, though: on Windows, resolvers tend

Re: Strange DIG behavior on Windows 10:

2018-10-23 Thread Timothy Metzinger
That's a good Avenue to explore I will see if I can find any differences Tim Metzinger 703.963.3015 From: bind-users on behalf of Kevin Darcy Sent: Tuesday, October 23, 2018 6:44:52 PM To: bind-users@lists.isc.org Subject: Re: Strange DIG behavior on Windows 10

Re: Strange DIG behavior on Windows 10:

2018-10-23 Thread Grant Taylor via bind-users
On 10/23/2018 04:21 PM, Timothy Metzinger wrote: At this point I’m stumped and welcome any suggestions. Trust the bits on the wire. What sort of outgoing DNS queries do you see when you run dig on the problematic system without specifying the DNS server? Can you find that server listed anyw

RE: Strange DIG behavior on Windows 10:

2018-10-23 Thread Timothy Metzinger
I see NO outgoing bits on the wire, bolstering my theory that DIG isn't finding name servers in the registry. NSLOOKUP works fine. There's no difference between the working and non working PC in the name servers listed in all the interfaces in ifconfig /all. Registry values for HKLM\system

RE: Strange DIG behavior on Windows 10: - SOLVED (sorta)

2018-10-23 Thread Timothy Metzinger
One machine had resolv.conf in ISC BIND 9\etc, the other didn't. So I suspect that in spite of the release notes about resolv.conf not being needed... it really is. Perhaps it isn't if you install the full BIND service but is needed if you only install the tools. -Original Message- Fro

Re: Understanding TTL in "rndc dumpdb"-output

2018-10-23 Thread Tom
Hi Michal Thank you for this feedback. I've checked the serve-stale status, which is currently off. # rndc serve-stale status _default: off (stale-answer-ttl=1 max-stale-ttl=604800) _bind: off (stale-answer-ttl=1 max-stale-ttl=604800) Is this a normal behavior, that in the "rndc dumpdb" neverthe