Mike Vanecek wrote: > Two questions. > > 1. Why do I not run into the same reverse lookup problem? Is it > because I have a static ip? Probably. FWIW: I have a static IP address through Verizon and never had a problem deliving e-mail even though reverse lookup queries did not match the name lookup. After three years, I finally found the right department at Verizon and got my PTR record changed. > > 2. If I understand things correctly ... The only way host ip-address > will return my domain-name is for my isp to put a PTR record in their > zone definitions (which most are reluctant to do)? Any other way to > get a reverse lookup to point to my domain name as opposed to the isp > name? Not that I'm aware of. Your ISP has to either: 1) Delegate the PTR record lookup at your DNS server. 2) Change the PTR record to what you specify in their zone files. This is what Verizon did for me. They would not delegate (add a NS record) to my DNS server. BTW: Based on my conversations with Verizon, they only make these PTR record changes for Business (static) accounts, not residential (DHCP assigned) accounts. If you want to understand why your ISP must make the PTR record change... Type: dig +trace -x yy.yy.yy.yy where yy.yy.yy.yy is your static IP address. The above dig command will follow the query back from the root name servers. The final "answer" should come from your ISP's name servers. Steve Cowles -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
