> > 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.
- Re: Reverse DNS Rejection Proble... Wietse Venema
- Reverse DNS Rejection Problem Stan Hoeppner
- Re: Reverse DNS Rejection Proble... Dennis Putnam
- Re: Reverse DNS Rejection Proble... Eero Volotinen
- Re: Reverse DNS Rejection Proble... Dennis Putnam
- Reverse DNS Rejection Problem Stan Hoeppner
- Re: Reverse DNS Rejection Proble... Paul Beard
- Reverse DNS Rejection Problem Stan Hoeppner
- Re: Reverse DNS Rejection Problem Phillip Smith
- Re: Reverse DNS Rejection Problem ram
- Re: Reverse DNS Rejection Problem Phillip Smith
- Re: Reverse DNS Rejection Problem Ansgar Wiechers
- Re: Reverse DNS Rejection Proble... mouss
- Re: Reverse DNS Rejection Proble... Ansgar Wiechers
- Re: Reverse DNS Rejection Proble... Noel Jones
- Re: Reverse DNS Rejection Proble... Ansgar Wiechers
- Re: Reverse DNS Rejection Problem d . hill
- Re: Reverse DNS Rejection Problem Charles Marcus
- Re: Reverse DNS Rejection Problem Dennis Putnam
- Re: Reverse DNS Rejection Problem Victor Duchovni
- Re: Reverse DNS Rejection Problem Dennis Putnam