Access external website with same domain name


Recommended Posts

OK, so my Windows domain on my network is called fault.com (for example). Now I have an external website on the Internet hosted by my ISP also at fault.com (and www.fault.com).

How do I access it now cause the DNS on the Windows Server 2003 box thinks it's internal :(

Thanks.

wouldnt that be bad since his pc would think the domain controller was at that ip instead of his lan ip

PS. what if you add a dns record on ur dns server so that www.xxxxx.com point to the external website and xxxx.com points to your internal website

  semaja2 said:

wouldnt that be bad since his pc would think the domain controller was at that ip instead of his lan ip

PS. what if you add a dns record on ur dns server so that www.xxxxx.com point to the external website and xxxx.com points to your internal website

Sounds like exactly what I need :) How do I do that exactly :p I can get to the DNS config screen in Administrative Tools but I'm clueless from there!

Thanks man.

I think you should analyze why you have an internal domain named after a public domain that is not under your control... If you want your employees to have access to your public website, that is one thing, but unless you control both sites, you'll only open yourself up to security issues.

it would be quite hard for me to just explain how to do what i said but you could get some reading matterial or with that hosts file but add www.xxxx.com xxx.xxx.xxx.xxx to it but not your normal domain name

PS if ya get that cuz i dont

  John said:

I think you should analyze why you have an internal domain named after a public domain that is not under your control... If you want your employees to have access to your public website, that is one thing, but unless you control both sites, you'll only open yourself up to security issues.

I think what the topic starter was saying is that he DOES control the domain, but it's not DNS'd to his domain controller.

  Leddy said:

I think what the topic starter was saying is that he DOES control the domain, but it's not DNS'd to his domain controller.

Hello, if I understand you right: correct! I own the public external domain on the Internet too, but it's hosted by my ISP.

So, how might I add this DNS record to my DNS configuration on Windows Server 2003 to point to this external website at my ISP?

  semaja2 said:
PS. what if you add a dns record on ur dns server so that www.xxxxx.com point to the external website and xxxx.com points to your internal website

No. Because of the www before the domain name. You are telling windows that any requests for www.domain.com are to be forwarded to xxx.xxx.xxx.xxx

Requests to domain.com know, because for the entries in DNS server, that this is the local domain.

This is a dirty little trick that works.

This is also a neat trick for other things too.

Example 1:

Your users love using eBay.co.uk, but you don't want them to go to ebay.com. Well an entry in the hosts file can tell windows that the ip address of ebay.com is the ip of ebay.co.uk.

Example 2:

When you have a adware problem, but you don't have time fix it now because its smoke break time. A quick entry into hosts can open your intranet site rather than an external site.

1) Ah ok, but wouldn't creating a DNS entry that www.fault.com points to an external IP equally do the same? Or am I wrong?

2) I tried your little hosts file trick. It works but now I guess I have to copy that hosts file to each workstation on the network :( Easy enough with a little script, but is this what they do in practice?

Why can't you just add a CNAME record or A record in DNS that points www to you external site.

So in the DNS tool on your Windows 2003 server - you open up your FORWARD zones and there should be one there for your domain name (fault.com). Right click on FAULT.COM and from the drop down menu choose A RECORD and simply type in www and give the external IP address.

Now - if for some reason you have named your main Windows 2003 server as WWW - then you are screwed... but if you have no other records called www in your dns zone then simply adding a A RECORD will do exaactly what you want.

Bill

  teeple said:

Why can't you just add a CNAME record or A record in DNS that points www to you external site.

So in the DNS tool on your Windows 2003 server - you open up your FORWARD zones and there should be one there for your domain name (fault.com). Right click on FAULT.COM and from the drop down menu choose A RECORD and simply type in www and give the external IP address.

Now - if for some reason you have named your main Windows 2003 server as WWW - then you are screwed... but if you have no other records called www in your dns zone then simply adding a A RECORD will do exaactly what you want.

Bill

Sweet, that works perfectly :) Exactly what I needed - thanks Bill.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Now I may not quite understand this, so someone tell me if I'm off the mark here, but does this mean they'll be potentially removing drivers for now unsupported systems, such as old processors and chipsets? In the past 15 years, Windows has been amazing at just installing on any device, and often having zero, or just a few unessential drivers missing on first install. It would be a shame for that experience to go, though I understand the reasoning, or at least their financial reasoning for it!
    • Microsoft is removing legacy drivers from Windows Update by Usama Jawad Last month, we learned that Microsoft is making major changes to the development of hardware drivers in Windows. This included the retirement of Windows Metadata and Internet Services (WMIS), along with the process for pre-production driver signing. Now, the Redmond tech firm has informed partners that it will be getting rid of old drivers in Windows Update. In what is being described as a "strategic" move to improve the security posture and compatibility of Windows, Microsoft has announced that it will be performing a cleanup of legacy drivers that are still being delivered through Windows Update. Right now, the first phase only targets drivers that already have modern replacements present in Windows Update. As a part of its cleanup process, Microsoft will expire legacy drivers so that it is not offered to any system. This expiration involves removing audience segments in the Hardware Development Center. Partners can still republish a driver that was deemed as legacy by Microsoft, but the firm may require a justification. Once the Redmond tech giant completes its first phase of this cleanup, it will give partners a six-month grace period to share any concerns. However, if no concerns are brought forward, the drivers will be permanently eradicated from Windows Update. Microsoft has emphasized that this will be a regular activity moving forward and while the current phase only targets legacy drivers with newer replacements, the next phases may expand the scope of this cleanup and remove other drivers too. That said, each time the company takes a step in this direction, it will inform partners so that there is transparency between both parties. Microsoft believes that this move will help improve the security posture of Windows and ensure that an optimized set of drivers is offered to end-users. The firm has asked partners to review their drivers in Hardware Program so that there are no unexpected surprises during this cleanup process.
    • No idea, but I had a client the other week that lost the entire drive to it. I suggested relying on the Samsung T7's instead. The Sandisk Extreme's had reliability issues too.
    • I use it every day so personally yes I need it, or rather I want it. I use OpenShell though, not the garbage modern Start Menu. I just counted and at the moment I have a total of 92 program shortcuts organized into six folders almost exactly the way I did back in Windows 95. I can get to any program I want to run very quickly. I never use Search to find or run programs.
    • I do miss the Apps view from Windows 8.1 Update.
  • Recent Achievements

    • One Month Later
      KynanSEIT earned a badge
      One Month Later
    • One Month Later
      gowtham07 earned a badge
      One Month Later
    • Collaborator
      lethalman went up a rank
      Collaborator
    • Week One Done
      Wayne Robinson earned a badge
      Week One Done
    • One Month Later
      Karan Khanna earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      682
    2. 2
      ATLien_0
      274
    3. 3
      Michael Scrip
      220
    4. 4
      +FloatingFatMan
      171
    5. 5
      Steven P.
      160
  • Tell a friend

    Love Neowin? Tell a friend!