esses in the glue records.
>
> e.g.
> dig +dnssec +norec internet-dns1.state.ma.us @146.243.122.17
>
> Mark
>
> > On 10 Feb 2021, at 14:50, sami's strat wrote:
> >
> > Thanks Mark.
> >
> > However, the traceroute to the hostnamed failed for
10 PM Mark Andrews wrote:
> Well you could try tracing the addresses of the nameservers for which
> there where errors reported. It could be as simple as a routing issue
> between you and these servers.
>
> > On 10 Feb 2021, at 13:25, sami's strat wrote:
> >
> > c
I'm running BIND 9.11 on a CentOS 7 VM/ BIND is giving me the wrong answer
for a single domain. I've cleared cache, restarted BIND, restarted the
server, and ensured that I don't have the referenced domain anywhere in my
configuration hardcoded.
Please note the following query:
[root@myhost ~]
wrote:
> On 14 July 2017 at 01:52, sami's strat wrote:
> > However, the zone is missing the DS record, completely. That being said,
> > what is the offset, or result? I don't see an AD flag when querying the
> > zone. Other then that, are there any other ramificat
The following zone is dnssec signed: ns2cloud.com
However, the zone is missing the DS record, completely. That being said,
what is the offset, or result? I don't see an AD flag when querying the
zone. Other then that, are there any other ramifications?
thanks in advance.
If I have two domains, say a.us and b.com
a.us is (dnssec) signed and the parent domain has a copy of the DS keys.
Is there a way to have host.b.com run dnssec aware queries against a.us?
I was thinking of setting up and using the ISC trust anchor with both
domains. Would that work? Are there
6 matches
Mail list logo
