Hi, Schilling -
NS records need to be updated in both the parent and authoritative
zones. The edu. parent is operated by Educause (and Verisign). The
cps.edu hostmaster can request the nameserver addition here:
https://net.educause.edu/
It is best practice for both listings of nameservers to matc
practice, we have encountered caching resolvers that provide
non-decrementing TTL values to downstream resolvers and clients. Even if a
misbehaving resolver expires its cache at the two-day mark, some of its clients
are likely to retain the old records for an additional two days.
Mitchell Kuch
The only remotely valid use case that I have found was the default DNS
monitoring rule for OpenNMS and other monitoring applications. Such a
shame.
On Fri, Mar 21, 2014 at 12:09 PM, Marco Davids (SIDN)
wrote:
> To me, an NXDOMAIN-reply seems better
On Fri, Mar 21, 2014 at 8:50 AM, Mitchell K
Hello -
I've adopted a number of zones and most of them contain "localhost in
a 127.0.0.1" records. I'm curious what current RFC standards state and
what the community considers best practice. RFC1537 states that zones
should contain a localhost record, but it seems that practice was
obsoleted by
4 matches
Mail list logo