Re: Question about visibility

2018-10-24 Thread Timothy Metzinger
There's no security in obscurity. Automated port scanners will sweep your system in a couple of seconds. Tim Metzinger From: bind-users on behalf of G.W. Haywood via bind-users Sent: Wednesday, October 24, 2018 12:15:10 PM To: bind-users@lists.isc.org Subject: Re: Question about visibility

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

2018-10-23 Thread Timothy Metzinger
al Message- From: bind-users On Behalf Of Timothy Metzinger Sent: Tuesday, October 23, 2018 8:13 PM To: bind-users@lists.isc.org Subject: RE: Strange DIG behavior on Windows 10: I see NO outgoing bits on the wire, bolstering my theory that DIG isn't finding name servers in the registry. NSLO

RE: Strange DIG behavior on Windows 10:

2018-10-23 Thread Timothy Metzinger
isc.org Subject: Re: Strange DIG behavior on Windows 10: 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 wit

Re: Strange DIG behavior on Windows 10:

2018-10-23 Thread Timothy Metzinger
r other factors. For that matter, you might be trying to use IPv6 resolvers, even though IPv6 may not be routable from your LAN. Check out ipconfig /all. - Kevin On Tue, Oct 23, 2018 at 6:22 PM Timothy Met

Strange DIG behavior on Windows 10:

2018-10-23 Thread Timothy Metzinger
lv.conf file in c:\windows\system32\drivers\etc with contents: nameserver 192.168.1.250 nameserver 192.168.1.251 nameserver 8.8.8.8 And that made no difference. Running the command prompt as an administrator makes no difference. At this point I'm stumped and welcome any suggestions