This is a discussion on RE: Need help with reverse zone record within the Bind Users forums, part of the DNS and Related Forums category; -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > -----Original Message----- > From: bind-users-bounce@isc.org > [mailto:bind-users-...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > -----Original Message----- > From: bind-users-bounce@isc.org > [mailto:bind-users-bounce@isc.org] On Behalf Of Chris Fortune > Sent: Wednesday, August 25, 2004 10:05 PM > To: comp-protocols-dns-bind@isc.org > Subject: Re: Need help with reverse zone record > > > > SMTP error from remote mailer after initial connection: > > > host mx02.sccoast.net [66.153.203.185]: 550 Reverse > DNS lookup > > > failed for host 69.56.237.82 > > > > Reverse lookup seems to be working for these ips. One possility > > is that the receiving mail server is trying to match a forward > A record > > with the reverse PTR for 69.56.237.82. if mail is in fact > coming from > > 69.56.237.82, some receiving smtp servers will deny a > connection from > > it because there is not forward A record for spameater.com > that points > > to 69.56.237.82. > > > > Just a guess > > mv > > > > DNS is so confusting. Does the A record go into the zone > record (not the reverse zone record)? > Yes the A record goes in the forward zone. If 69.56.237.84 reverse resolves to spameater.com then there should also be a forward A record with the same ip. > How to do this? Can I have two A records for the same domain > name? Like > this: > spameater.com. IN A 69.56.237.84 > > spameater.com. IN A 69.56.237.82 Yes you can have as many A records you want. But again, I don't know for a fact that this is your root problem. I just know I have seen some systems deny because of lack of A records that match to PTR records and it cant hurt to set it up correclty like this. mv -----BEGIN PGP SIGNATURE----- Version: PGP 8.1 iQA/AwUBQS4jX0YhBmUvDNxOEQI8EQCg30eFITWAhl+GKCY8wRSR+R vhWNsAn22b bWKsxjnf+LQbvAFp8HPshi2v =9Vwy -----END PGP SIGNATURE----- |