Accessing an internal webserver with an external domain name

Currently our company has it's webserver on the same network as the DNS server. We use a DNS entry "website" to access the site internally, and an external address for customers (www.ourcompany.com). Our developer, however, wrote an intranet and SQL applications to make calls to the external domain.

Is it possible to use the external domain on our internal network? Our internal DNS server is used strictly for internal DNS functions, and we use EasyDNS for our website. And the entire network operates on a Server 2003 platform.

Any help is greatly appreciated.
MightyPezAsked:
Who is Participating?
 
Chris DentConnect With a Mentor PowerShell DeveloperCommented:

Hi,

You would have to add a version of ourcompany.com to your internal DNS Server so internal clients can resolve it.

If your internal DNS Server already has a Forward Lookup Zone for ourcompany.com you can simply add the www record with the appropriate IP Address.

If your DNS Server doesn't have that zone you can add it, you get a couple of choices as to exactly how you do so (the rest assumes MS DNS). The only difference between the two versions is how much they're responsible for. The first means you will have to create everything you need to resolve under ourcompany.com internally. The second means you only resolve www differently from the rest of the world.

1. Authoritative for ourcompany.com

- Select Forward Lookup Zones in the DNS Console
- Right click and select New Zone
- Zone type should be Primary and can be AD Integrated if you wish (and if applicable)
- Name the zone: ourcompany.com
- Set Dynamic Updates to None
- Add a new Host (A) Record to the zone with the name "www"; set the IP as appropriate

2. Authoritative for www.ourcompany.com (remainder of the domain will be resolved by public DNS)

- Select Forward Lookup Zones in the DNS Console
- Right click and select New Zone
- Zone type should be Primary and can be AD Integrated if you wish (and if applicable)
- Name the zone: www.ourcompany.com
- Set Dynamic Updates to None
- Add a new Host (A) Record to the zone with a blank name; set the IP as appropriate

HTH

Chris
0
 
MightyPezAuthor Commented:
Sorry, i forgot to mention. Our current zone is ourcompany.local. Will the same steps above apply?
0
 
Chris DentPowerShell DeveloperCommented:

Hi,

Yep, the same steps apply, if the zone was ourcompany.com you'd only have to add the www record to the existing zone. 1 and 2 both cover creating a new zone to handle this requirement.

Chris
0
 
MightyPezAuthor Commented:
Very helpful, thank you for your assistance.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.