• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 189
  • Last Modified:

DNS Connection Setup Problem

Hi All,

We have recently set-up our company corporate DNS.

Our Domain Name is our <companyname> [Easy choice].
Our internal network is a 198.XXX.XXX.XXX
[Internal Network Addresses].

Unfortunatly, as a result we cannot access our company home page. [www.<companyname>.com].

This is due to the fact that our DNS cannot resolve the name + find its entry which is on a seperate network address: 213.XXX.XXX.XXX.  All client machines have the Internet IP DNS entrys on their machines.

What is the easiest fix to allow the users access to the company home page [www.companyname.com].
1) Rename the Domain to something else ->
[And change 50+ Client Machines]
2) Provide a fix to add to DNS
[Which I require: My prefered fix]
3) Access Company homepage via IP Address
[Not acceptable Solution]
4) Reverse DNS lookup solution ?

Thanks in Advance,

dna.
0
danblake
Asked:
danblake
  • 4
  • 2
1 Solution
 
geoffrynCommented:
The preferred way to accomplish this is to use a split DNS.  You install DNS on your internal network and populate it with the host names and IP addresses both internal and external.  Then you delete the root zone (.) and set up forwarders.  Modify your DHCP to hand out only the internal DNS server address.  The clients will query the local DNS server and if it does not have the record it will forward to the ISP DNS.  The local DNS will respond with the correct external address for your web site.
0
 
danblakeAuthor Commented:
Hi Geoffryn,

I am new'ish to (Microsoft)DNS -> What is a split DNS ?

Our population our host names is automatically generated from our DHCP server.

Our external IP address resolutions -> machine names have been added to our existing DNS [I don't think this is a split DNS ? - see diagram of our dns layout at the end of this comment].  Our DNS forwarder has been set-up as the ISP DNS (This is also on client machines as one of their available DNS - should this be removed ?).

We currently have the client machines IP Addresses assigned by our DHCP server [This is set in our 198.XXX -> 198.XXX range].

Could give some further info about the setup of a split-level DNS.

Unfortunatly our DNS looks like:
\ForwardLookupZone
 \CompanyName
  \_msdcs
  \_sites
  \_tcp
  \_udp
\ReverseLookupZone

I am guessing a split-level DNS is:
\ForwardLookupZone
  \.
    \CompanyName
     \All Items
    \ExternalDNSResolutions
     \All Items
\ReverseLookupZone

Regards,

Dan.
0
 
danblakeAuthor Commented:
Hi Geoffryn,

I am new'ish to (Microsoft)DNS -> What is a split DNS ?

Our population our host names is automatically generated from our DHCP server.

Our external IP address resolutions -> machine names have been added to our existing DNS [I don't think this is a split DNS ? - see diagram of our dns layout at the end of this comment].  Our DNS forwarder has been set-up as the ISP DNS (This is also on client machines as one of their available DNS - should this be removed ?).

We currently have the client machines IP Addresses assigned by our DHCP server [This is set in our 198.XXX -> 198.XXX range].

Could give some further info about the setup of a split-level DNS.

Unfortunatly our DNS looks like:
\ForwardLookupZone
 \CompanyName
  \_msdcs
  \_sites
  \_tcp
  \_udp
\ReverseLookupZone

I am guessing a split-level DNS is:
\ForwardLookupZone
  \.
    \CompanyName
     \All Items
    \ExternalDNSResolutions
     \All Items
\ReverseLookupZone

Regards,

Dan.
0
Cloud Class® Course: Ruby Fundamentals

This course will introduce you to Ruby, as well as teach you about classes, methods, variables, data structures, loops, enumerable methods, and finishing touches.

 
geoffrynCommented:
A split DNS is two different DNS servers, one internal, one external, resolving names differently.  I assume that all of your client recieve external DNS addresses from DHCP?  Are you running AD?  
0
 
danblakeAuthor Commented:
The external DNS server -> ISP [ADSL].
The internal DNS server -> [CompanyName Domain]
Modify your DHCP to hand out only the internal DNS server address -> This has now been performed.
DNS Addresses from DHCP ? -> Yes.
AD -> Yes.

This now seems to be working.

Hoorah - I can now get direct access to our <CompanyName> website.

Thanks,

Dan.

0
 
danblakeAuthor Commented:
Thanks for the 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.

Join & Write a Comment

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now