DNS Traversal says RDNS/PTR doesn't match
In dnsstuff.com rdns check..h_t_t_p://www.dnsstuff.com/tools/traversal.ch?domain=reverseipxx.xx.xx.xx.in-addr.arpa&type=PTR
2 QUESTIONS
-----------
1. what is DNS TRaversal
2. what are the implications when DNS TRaversal reports
Looking up at the 4 xxx.xxx.xxx.in-addr.arpa. parent servers:
Server Response Time
ns1.managed.net [Reports no PTR record] 110ms
ns1.mesonix.com mydoman.com. 110ms
ns2.managed.net [Reports no PTR record] 110ms
ns2.mesonix.com mydomain.com. 110ms
Status: Records DO NOT all match: Results from ns1/2.managed.net do not match results from ns1/2.mesonix.com.
Server Response Time
ns1.managed.net [Reports no PTR record] 110ms
ns1.mesonix.com mydoman.com. 110ms
ns2.managed.net [Reports no PTR record] 110ms
ns2.mesonix.com mydomain.com. 110ms
Status: Records DO NOT all match: Results from ns1/2.managed.net do not match results from ns1/2.mesonix.com.
Does anyone else in managed have this problem. Why does managed need to have RDNS/PTR done on both managed.net and mesonix.com name server.?
How do I get all the name servers (ns1/2.managed.net and ns1/2.mesonix.com) to report RDNS/ptr.
RDNS/PTR was done for me months ago ;-)
TIA