Re: DNS issues, reverse lookup, MX records
- From: "Bharat Suneja [MVP]" <bharatsuneja@xxxxxxxxxxx>
- Date: Fri, 5 Jan 2007 08:42:27 -0800
If they're the ones maintaining reverse lookup zone for your block of IP
address(es), yes.
--
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
www.exchangepedia.com/blog
----------------------------------------------
<bjriffel@xxxxxxxxxxx> wrote in message
news:1168013166.746535.308430@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
We have a dedicated T1 from AT&T, so does that mean that we need to ask
AT&T to add a PTR record for server.ourdomain.com for our static
external address?
Bharat Suneja [MVP] wrote:
PTR record is a reverse lookup record that maps your IP address to the
fqdn - opposite of what an A record does.
PTR records are added in reverse lookup zones by owner of that IP address
block.
Typically for consumer DSL/cable connections, even though you may get a
few
static IP addresses, the service provider will maintain the reverse
lookup
zone. Talk to your service provider.
If you have a block of IP addresses and want to maintain your own reverse
lookup zone (doubtful in this case since you've outsourced your forward
lookup zone), you can try talking to your service provider about
delegating
reverse lookup for your block of IPs.
--
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
www.exchangepedia.com/blog
----------------------------------------------
<bjriffel@xxxxxxxxxxx> wrote in message
news:1168010304.912925.304150@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hello,
I've done some searching in the groups, but I'd like to pose a specific
scenario. We are getting these errors:
#4.7.1 smtp;450 4.7.1 Client host rejected: cannot find your reverse
hostname,
This is the situation. Our domain name is registered with network
solutions. Our website is hosted with Yahoo on a business account.
Yahoo used to host our email as well. Recently we put in a local SBS
2003 server to host our Exchange locally. Originally our Network
solutions account had all DNS pointing to Yahoo's name servers, as it
should have. We wanted to switch the MX record to point to our static
IP on our T-1 for our new server. However, we can't have the www
address point to a single IP with Yahoo. Yahoo requires that we just
redirect Network Solutions DNS to them. So we reverted all DNS back to
Yahoo.
Now Yahoo has static entries for www and mail .domain.com pointing to
internal yahoo server, which we can't change. We added a record for
our mail server: server.domain.com and pointed it to our static
external IP address. We also created an MX record for
server.domain.com. Email started flowing in as expected.
However now some email systems, most notably AOL and Comcast, are
resolving our name it seems. We are getting the message I posted
above. Many of the postings I've read say that we need to add a PTR
record for our mail server. Is that on our local internal DNS or on an
external? If it is external DNS, then whos? Our ISP (AT&T) or on
Yahoo?
Thank you,
Brandon Riffel
.
- Follow-Ups:
- Re: DNS issues, reverse lookup, MX records
- From: bjriffel
- Re: DNS issues, reverse lookup, MX records
- References:
- DNS issues, reverse lookup, MX records
- From: bjriffel
- Re: DNS issues, reverse lookup, MX records
- From: Bharat Suneja [MVP]
- Re: DNS issues, reverse lookup, MX records
- From: bjriffel
- DNS issues, reverse lookup, MX records
- Prev by Date: Re: share address space
- Next by Date: ESEUTIL defrag and Disk space - Exchange 5.5/sp4
- Previous by thread: Re: DNS issues, reverse lookup, MX records
- Next by thread: Re: DNS issues, reverse lookup, MX records
- Index(es):
Relevant Pages
|
