This is a discussion on Re: Does IP have DNS or not? within the mailing.postfix.users forums, part of the Mail Servers and Related category; On Wed, 7 Jul 2004, Jim Wright wrote: > This came in a few days ago, and so I contacted ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
On Wed, 7 Jul 2004, Jim Wright wrote: > This came in a few days ago, and so I contacted the postmaster there > regarding his system having a problem: > > Jul=A0 1 21:19:02 localhost postfix/smtpd[509]: connect from > unknown[63.82.232.8] > Jul=A0 1 21:19:04 localhost postfix/smtpd[509]: NOQUEUE: reject: RCPT > from unknown[63.82.232.8]: 550 Client host rejected: cannot find your > hostname, [63.82.232.8]; from=3D<***@hometel.com> > to=3D<***wrightthisway.com> proto=3DSMTP helo=3D<mail.hometel.com> > Jul=A0 1 21:19:04 localhost postfix/smtpd[509]: disconnect from > unknown[63.82.232.8] > > He has responded back saying his info resolves fine, claiming the issue > is on my end. I tried resolving that IP both on my home system and > work system (different ISP/DNS servers), and both came back as: > > ** server can't find 8.232.82.63.in-addr.arpa: NXDOMAIN > > However, in between those two I went to remote.12dt.com/rns/ to do a > reverse lookup on that address, and it responded with ns2.hometel.com > for that IP. > > So, I'm assuming that he still has some DNS issues on his end, but I > don't know enough about such things to tell him what the problem is. > Or is there really a problem on my end somehow? It looks like there is no PTR for 63.82.232.8: The Authoratative servers are: NameServer: AUTH03.NS.UU.NET NameServer: AUTH00.NS.UU.NET AUTH00.NS.UU.NET returns an NS delagation -- but no PTR: ;8.232.82.63.in-addr.arpa. IN PTR ;; AUTHORITY SECTION: 232.82.63.in-addr.arpa. 21600 IN NS ns1.hometel.com. 232.82.63.in-addr.arpa. 21600 IN NS ns2.hometel.com. AUTH03.NS.UU.NET returns no delagation: ;; QUESTION SECTION: ;8.232.82.63.in-addr.arpa. IN PTR ;; AUTHORITY SECTION: 232.82.63.in-addr.arpa. 21600 IN SOA auth03.ns.uu.net. Thus, it appears to be a sync problem between the UUnet servers. . . You need to contact the UUnet hostmasters and have them re-initiate a zone transfer... --sjk |