wrote:
>
> +cd disables DNSSEC validation. You are running some very old versions of
> dig in some cases which don't have dnssec support. The 9.9 version of dig
> you have on at least one server should work.
>
> What version of BIND server are you running on the pr
> On May 31, 2018, at 5:29 PM, Mark Andrews wrote:
>
> Well the first thing is that dig +trace is making queries from the machine it
> is running on and not the name server unless they are one and the same. The
> @ns2.service.uci.edu is only used to lookup the root nameservers. Dig +trace
>
Hi
Can you elaborate on +cd? a dig option, I am not finding it as an option.
thanks
con
> On May 31, 2018, at 2:51 PM, Warren Kumari wrote:
>
> Try it with +cd and see if that fixes it.
>
> The DNSSEC stuff for this domain is all borked up -- sufficiently that
> I felt like I was playing snak
Thanks for the explanation of “ANY”
The strange thing is this server previously answered this correctly. We
changed the ip address ( on the same network segment) of it to replace one of
our existing servers. That is when it no longer resolved extranet.aro.army.mil.
It otherwise is resolving na
4 matches
Mail list logo
