On 27.04.2024 16:54, Lee wrote:
On Sat, Apr 27, 2024 at 9:50 AM Walter H. via bind-users
wrote:
# host dnssec-analyzer.verisignlabs.com
dnssec-analyzer.verisignlabs.com is an alias for
dnssec-analyzer-gslb.verisignlabs.com.
dnssec-analyzer-gslb.verisignlabs.com has address 209.131.158.42
Righ
On 2024-04-26 16:45, Josh Kuo wrote:
In this particular case, isn't the resolver attempting to do a reverse
lookup of the IP address that's listed ?
You are right, I missed that this is a reverse-mapping zone. In that
case, run DNSSEC analyzer on the domain "180.96.34.in-addr.arpa" and
On 2024-04-26 16:28, Mark Andrews wrote:
DS records live in the parent zone and the RFC 1034 rules for serving zone
break down when a grandparent zone and child zone are served by the same
server. This is corrected be the client by looking for intermediate NS records
to find the hidden deleg
On Sat, Apr 27, 2024 at 9:50 AM Walter H. via bind-users
wrote:
>
> # host dnssec-analyzer.verisignlabs.com
> dnssec-analyzer.verisignlabs.com is an alias for
> dnssec-analyzer-gslb.verisignlabs.com.
> dnssec-analyzer-gslb.verisignlabs.com has address 209.131.158.42
>
Right, the IPv4 address look
# host dnssec-analyzer.verisignlabs.com
dnssec-analyzer.verisignlabs.com is an alias for
dnssec-analyzer-gslb.verisignlabs.com.
dnssec-analyzer-gslb.verisignlabs.com has address 209.131.158.42
On 27.04.2024 01:35, Lee wrote:
dig dnssec-analyzer.verisignlabs.com
gives me a SERVFAIL & thi
5 matches
Mail list logo