Eric,
Thanks for the complete example below, but I'm not sure what you are
trying to solve?
It looks like the netregistry.net servers don't have zone data loaded
even though they are supposed to be authoritative. Your best bet would be to
contact them and point out it appears s
On first glance it looks like although the domain registration points to
the DNS servers at planetdomain.com., the actual domain has NS records (and
an MNAME entry in the SOA) which point to DNS servers at netregistry.net.
Anyone else have different results?
Regards,
Bob
> Our DNS resolvers are not only used by stub resolvers but by DNS
> resolvers using DNS forwarding as well. I wonder what happens if DNS
> forwarding resolvers do DNSSEC validation? It looks like they would
> return SERVFAIL to the user as the RPZ response omits any RRSIG for the
> landing page.
Hi,
Someday ago netregistry.com bought planetdomain.com. And there are a
number of domains (not sure if all) host at ns1/ns2.planetdomain.com
ns point to ns1/ns2/ns3.netregistry.net. However these netregistry.net do
not host these domain. Then if the records of these domain expired and
refresh
4 matches
Mail list logo
