Re: ipv4-mapped reverse lookups

2013-07-09 Thread Lawrence K. Chen, P.Eng.
Well, it seems to work testing it... But, the systems that are having trouble are still having trouble. Though taking a closer look at the logs of one of the systems, the problem started in April 2009 (and the system was rebooted shortly after that point, and the problem continued...) Since i

Re: ipv4-mapped reverse lookups

2013-07-08 Thread Mark Andrews
In message <9efac3c5-c5be-43f8-b7f4-2be8ba30d...@isc.org>, Mark Andrews writes: > One could also look at the dns64 reverse code to do this. It synthesises > cname records on the fly. > > Mark > e.g. zone "f.f.f.f.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa" { type

Re: ipv4-mapped reverse lookups

2013-07-08 Thread Mark Andrews
One could also look at the dns64 reverse code to do this. It synthesises cname records on the fly. Mark On 09/07/2013, at 8:27, Mark Andrews wrote: > Getnameinfo and gethostbyaddr are supposed to lookup the in-addr.arpa records > instead of ip6.arpa records for mapped addresses. If you only

Re: ipv4-mapped reverse lookups

2013-07-08 Thread Mark Andrews
Getnameinfo and gethostbyaddr are supposed to lookup the in-addr.arpa records instead of ip6.arpa records for mapped addresses. If you only have a limited range of addresses one could use $generate to add cname records which map from ip6.arpa to in-addr.arpa. Mark On 09/07/2013, at 8:12, "Lawr

ipv4-mapped reverse lookups

2013-07-08 Thread Lawrence K. Chen, P.Eng.
For reasons unknown, some old Solaris servers are suddenly seeing connections to them as ipv4-mapped ipv6 (ie: :::10.20.30.40 ) Which is causing problems because it needs the reverse lookup to be right. So while we struggle between spending time to investigate why or continue to try to get