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

Client PC's can't see our agencys website that has the same name as our Active Directory domain

50- windows xp pro workstations

1-2003 file server (192.168.0.250) w/ Active Directory (myagency.org)

1-Windows 2000 exchange server (192.168.0.249) w/ Active Directory (myagency.org)

To my knowledge neither server has DNS installed.  Both servers referer to an external DNS for web for primary DNS.  There are some minor AD replication problems between the two servers but thats a different problem

The problem here is that the xp workstations run GREAT when there primary IP is set to 192.168.0.249 (exchange server) but the just run ok when primary IP is set to 192.168.0.250 (2003 file server)

the workstations run SLOW when their primary IP is set directly to the external DNS 131.230.xxx.xxx

So I have decided to set the primary DNS to 192.168.0.249 and everyone is happy... except for 1 problem-  the users with the ip of .249 (and .250 for that matter) cant see our companies website www.myagency.org.  They can see all other websites just fine but not ours.  Our website is hosted somewhere else and the name of our website is the same as the name of our Domain.

 So I am guessing that the clients are looking to my server for the address and when it is not there it says page not found, instead of going out to the web to look for it.   Any suggestions on how to get my clients to be able to see our website?   Thanks!!!!
0
JCHD
Asked:
JCHD
  • 4
  • 4
  • 2
3 Solutions
 
nightmare2Commented:
"To my knowledge neither server has DNS installed"

Look more carefully: you can't run an active directory domain without DNS.

"the xp workstations run GREAT when there primary IP is set to 192.168.0.249"

I guess you mean the primary DNS?
That's how it should be: clients must have the internal DNS as primary.
Don't put any external DNS on them.

Each DC should point to itself for DNS.
You will add the external DNS as forwarders on your internal DNS servers.

Refer to this article to configure forwarders: http://www.petri.co.il/configure_dns_forwarding.htm
0
 
northcideCommented:
i agree with nightmare2 regarding forwarders.  they are probably a good idea for your particular problem.

however, nothing in your AD domain should be named "www.myagency.org".  all you need to do is create a manual A record for www in your "myagency.org" dns zone on either server and point it to your real website out in the public and make sure users access the website via "www.myagency.org" rather than "myagency.org".
0
 
JCHDAuthor Commented:
Ok, I have set each server with it's primary DNS as itself and all the clients are pointing to .249

I have also set up forwarders to the external DNS on both servers.

Everything is going good, except we still cant see our own website.

How do I create a "manual A record for www" in DNS that points to my website?
0
Prepare for your VMware VCP6-DCV exam.

Josh Coen and Jason Langer have prepared the latest edition of VCP study guide. Both authors have been working in the IT field for more than a decade, and both hold VMware certifications. This 163-page guide covers all 10 of the exam blueprint sections.

 
nightmare2Commented:
In DNS Manager, go to forward lookup zones
Right click 'myagency.org'
Select New Host (A)
Enter WWW as the name and put the IP of your web site
Click 'Add host'
0
 
JCHDAuthor Commented:
nightmare2-  I got to that screen, and when I went to find the IP address of our website I found out that we do not have a unique IP from our webhost.  I called them and they said that it would cost an extra $5 a month to get a unique IP for our site.

Is there another way to get around that?  thanks
0
 
nightmare2Commented:
myagency.org. A IN 3600 66.166.139.68
Not you ?
0
 
JCHDAuthor Commented:
No no no.... I was just using "myagency.org" as an example domain... our real website is named something else but I didnt want to post it for security reasons.
0
 
nightmare2Commented:
So what do you mean by 'not unique IP' ?
Dynamic IP ?
Multiple IPs ?
0
 
northcideCommented:
jchd, from what i read up there you ARE able to get to the website from the public internet and not from your internal network, right?

If that is the case then you need to create a new A record INTERNALLY, forget about your ISP.  find your DNS server (probably any of your DC's) and then follow nightmare's directions.
0
 
JCHDAuthor Commented:
northcide-

Yes, I can get to our website from the Public Internet.... AND I get to our website if I am logged on locally to our server.

 I just cant see it from the clients because the clients are seeing "myagency.org" website as 192.168.0.249- and there is no website to be found there.

I realise that I did have DNS installed on the Exchange Server, and now I have installed it on the File Server so it is on both servers.  

So how do I set up an a DNS record that gets the clients to realize that the website is not located on .249 or .250?
0

Featured Post

How to Use the Help Bell

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention.  Check out this how-to article for more information.

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