Internet URL and Server Domain are same

mtroxmtrox Minnesota
edited December 2006 in Science & Tech
Somebody here's had this one. I'll change the name to protect the client, but....what if the domain controller is set up as whatever.com, and they then build a web site with a URL of whatever.com? Everyone on the outside can get to the whatever.com web site, but everyone on a client workstation attached to the domain controller can't get there. I'm sure they're just going to the DC...which contains no web site. In fact I can get to whatever.com.....unless I'm VPN'd in to the domain troubleshooting. Then I can't get there.

What do I have to do to get people on the whatever.com domain to their own web site? Obviously they can just use the IP adddress and get there, but you know how pesky customers can be.

Its a small office...maybe 15 computers so I could edit everyone's HOSTS file. But would that then screw up the domain login? I think Microsoft has a domain renaming app of some sort. Anyone done it or have some other workaround?

Comments

  • RyderRyder Kalamazoo, Mi Icrontian
    edited December 2006
    What is acting as the Internal DNS server? The DC or another box?

    You say the DC holds no website...so is that on another box internally or externally?

    Go to the DNS server for Internal use...setup whatever.com and point it to the proper IP (either internal or external)
  • KwitkoKwitko Sheriff of Banning (Retired) By the thing near the stuff Icrontian
    edited December 2006
    That's why you shouldn't use a public domain in AD, just causes issues. Change the domain to anywhere.local.
  • mtroxmtrox Minnesota
    edited December 2006
    It's a one server office....so the DC is the same address as the DHCP, the local DNS, etc. Yea I should have clarified, the web site is hosted outside the office...somewhere....
  • mtroxmtrox Minnesota
    edited December 2006
    Kwitko wrote:
    That's why you shouldn't use a public domain in AD, just causes issues. Change the domain to anywhere.local.

    I can't take credit for this one...I usually set up .local too. If I change it now I just have the feeling it will have a lot of unintended consequences....won't it?
  • primesuspectprimesuspect Beepin n' Boopin Detroit, MI Icrontian
    edited December 2006
    Yes, don't change the domain, that's needlessly complicated.

    Just go into DNS and add an A record pointing to the proper www ip for the www. record

    Problem solved.
  • mtroxmtrox Minnesota
    edited December 2006
    primesuspect wrote:
    Yes, don't change the domain, that's needlessly complicated.

    As in reattaching every workstation to a "new" domain? And then finding that every %$#@! workstation now has a "new" user and all the settings and files had to be transferred out of the old user......but before you could do that you'd have to take ownership of all the stuff that was owned by a user that no longer exists? Is that what you mean by "needlessly complicated"?

    And yes, I've done things that painful before.
    primesuspect wrote:
    Just go into DNS and add an A record pointing to the proper www ip for the www. record

    Problem solved.

    Had to do an A record for the whatever.com entry, and a CNAME for the www.whatever.com entry. After I flushed DNS I could get there from the two I VPN'd into.

    Thanks guys.
Sign In or Register to comment.