Can't get to our own website

[JohnB]

Our website is hosted externally, but we can't get to it from our inside
network.
I can do a NSLookup on any site but our own.
Our internal Win2k DNS servers are configured as forwarders.
What could be the problem?

 

[Scott Harding - MS MVP]

Is your Internal domain name the same as your real Internet Domain Name? You
may have to add a www record in your DNS server for this site.

 

[JohnB]

That was it. Thanks!

Is your Internal domain name the same as your real Internet Domain Name? You
may have to add a www record in your DNS server for this site.

 

[Scott Harding - MS MVP]

Your welcome, thanks for the feedback. This is one of the issues that can
arise from having your domain names the same internally/externally.

 

[Jeff]

I have the same issue. Scott, can you walk me throught the steps of adding a
www record in DNS? I just looked at DNS Server and I wasn't sure how to add
the record.

 

[Scott Harding - MS MVP]

Create a new A record and call it www and enter the correct IP address. As
long as you create it under the zone that is mydomain.com(where mydomain.com
is your domain name) when you type in www.mydomain.com it will use this
record from your DNS server.

 

[Jeff]

Cool beans! Thank you, Scott!

Create a new A record and call it www and enter the correct IP address. As
long as you create it under the zone that is mydomain.com(where mydomain.com
is your domain name) when you type in www.mydomain.com it will use this
record from your DNS server.

--
Scott Harding
MCSE, MCSA, A+, Network+
Microsoft MVP - Windows NT Server

adding

 

[Scott Harding - MS MVP]

Your welcome!

 

[Guest]

My question is along these lines. Our internal domain is .local and of course .com for external. Our users can't access our own internally hosted FTP site by it's external name

----- Scott Harding - MS MVP wrote: ----

Your welcome

--
Scott Hardin
MCSE, MCSA, A+, Network
Microsoft MVP - Windows NT Serve

Cool beans! Thank you, Scott

 

[Ace Fekay [MVP]]

In

My question is along these lines. Our internal domain is .local and
of course .com for external. Our users can't access our own
internally hosted FTP site by it's external name.

What Scott was trying to say is to manually create the record internally.
The reason why your folks can't get to it is because apparently, you are
hosting the FTP and website on a private internal address and you are port
remapping from the external WAN IP to the internal private IP and a NAT
device won't take a internal request on the internal interface and send it
to the external interface (the WAN IP) and then send it back in again. None
of them do.

So in your case, you have to manually create your external domain zone on
your internal DNS server and manually create an ftp and www record and give
it the actual internal private IP address. Then they can get to it.




--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Kevin D. Goodknecht [MVP]]

In

My question is along these lines. Our internal domain is .local and
of course .com for external. Our users can't access our own
internally hosted FTP site by it's external name.

If you want to access the site by ftp.domain.com, create a forward lookup
zone named ftp.domain.com, then create a blank host pointing to the IP
address of the internal FTP site.
Most FTP servers can be accessed by any name with the IP address. You can
create the new host in your existing domain.local zone and access it by
ftp.domain.local