[dns-operations] does it matter when nameserver recs have non-matching PTRs ?
jimpop at gmail.com
Mon Aug 3 14:56:48 UTC 2015
On Sat, Aug 1, 2015 at 2:22 PM, Mark Jeftovic <markjr at easydns.com> wrote:
> Ideally there is some leeway for common sense, i.e.
> ns1.example.com is temporarily using 192.168.4.13
> and if the PTR on 192.168.4.13 has a PTR to another hostname under the
> same superdomain (example.com), it should signal the same intent.
> If the IP PTR's back to mx.hotmail.com, then sure, I can see the
> reluctance to allowing the delegation.
So is this not considered a good use:
~$ dig NS speedyiguana.com
~$ host ns1.speedyiguana.net
ns1.speedyiguana.net has address 220.127.116.11
~$ host 18.104.22.168
22.214.171.124.in-addr.arpa domain name pointer ns1.domainmail.org.
More information about the dns-operations