Internal and External Domain Name

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I've recently run into a problem where users on the LAN side of my network
cannot access their website hosted by and ISP when typing in the
http://www.domain.com address in IE. This occurs shortly after adding my
internal server's DNS IP (192.168.xxx.xxx) in my router's DNS Servers Table
along with my ISP's DNS IP information. I recall reading somewhere that using
the same domain name (domain.com) both internally and externally can cause
problems. Is this the reason I am having this issue? Is there a workaround?

I've read in this forum that adding a record to my zone file may fix this
problem. If so, what type of record (A, Mx, etc.) do I need to create?

Appreciate your help with this one.
 
In
Bob Fitz said:
I've recently run into a problem where users on the LAN
side of my network cannot access their website hosted by
and ISP when typing in the http://www.domain.com address
in IE. This occurs shortly after adding my internal
server's DNS IP (192.168.xxx.xxx) in my router's DNS
Servers Table along with my ISP's DNS IP information. I
recall reading somewhere that using the same domain name
(domain.com) both internally and externally can cause
problems. Is this the reason I am having this issue? Is
there a workaround?

I've read in this forum that adding a record to my zone
file may fix this problem. If so, what type of record (A,
Mx, etc.) do I need to create?

Appreciate your help with this one.
Click to expand...

You don't need your own MX record, you need to a A records named www, mail,
or whatever name missing from the internal zone to accesss external sites in
the domain.
Just to add, you cannot access the external website by using only the domain
name, the domain name record MUST point to the addresses on all Domain
Controllers which have file sharing enabled. This is for the Domain SYSVOL
share at \\domain.com\SYSVOL
 
In
SYNCRO said:
And how exactly we do this? Can you provide step by step
instruction please
Click to expand...

Using the DNS management console, open the domain.com forward lookup zone,
right click in the zone and select new host from the drop down list. Name
this host www, give it the IP of the website, click create. Repeat for other
missing host records such as mail, ftp, and etc.
There is no need for a local MX record for your own domain, even if you had
your own mail server locally, it would need to see its own MX record, it
would already know it is the mail server for your domain.
 
Thank you kevin I will look into that

Syncro


Kevin D. Goodknecht Sr. said:
In

Using the DNS management console, open the domain.com forward lookup zone,
right click in the zone and select new host from the drop down list. Name
this host www, give it the IP of the website, click create. Repeat for
other
missing host records such as mail, ftp, and etc.
There is no need for a local MX record for your own domain, even if you
had
your own mail server locally, it would need to see its own MX record, it
would already know it is the mail server for your domain.
Click to expand...
 
Back
Top