In
jwkh said:
Okay, I'm confused. Is there a Microsoft Q article that
explains this?
We have our Web site hosted outside our network. Our mail
server has always been inside the network but we recently
changed the name from mail to exchange (we used a third
party system before and just changed to MS Exchange). The
FQDN for our mail server is now exchange.mycompany.com.
But DNS outside our network still has mail.mycompany.com
pointing to our router/firewall's IP address. We get email
okay, but we cannot get to our outside Web page from
inside.
The web page is simple, the www record must point to the web site IP. If you
want to find out what IP to give the record use nslookup then use the change
server command so nslookup is using your ISP's DNS then resolve
www.mycompany.com nslookup will return the IP or CNAME record that your
public www record points to.
If this sounds too confusing and I know it can be, if you will post your
website name I will give you step by step directions.
As for the PTR record you referred to, reverse lookups are for the most part
only used by mail servers. Many mail servers are configured to receive mail
from mail servers that have a PTR record for their IP. If you create a
reverse lookup zone that conflicts with a public IP and your mail server is
configured to do reverse lookups on mail servers sending it mail your mail
server will be unable to do the reverse lookups on IP in that NetBlock and
will reject the mail.