On 2009-10-29 Phillip Smith wrote: >>> Tell the admin of the remote domain to fix their PTR records and/or >>> MX helo configuration because in the meantime, you're going to have >>> to implement a dirty hack to make their server work. >> >> But the PTR needs no "fix". >> >> The IP resolves to a hostname perfectly fine , only that the hostname >> does not resolve. > > Then a) it doesn't resolve perfectly -- it should resolve both ways. > And b) any given IP address should only have *one* corresponding PTR > record, not multiple PTR's. For one, it causes problems like this.
It's a perfectly valid and supported DNS feature to have multiple PTR records. If this causes problems, then the respective application is at fault, not DNS. Regards Ansgar Wiechers -- "Abstractions save us time working, but they don't save us time learning." --Joel Spolsky
