DNS Domain name is same as domain fname for website...help!

[ITErik]

My current domain name in 2000 Active directory is domian.com (not really my domain name!!!)and my domian name for my website is also domain.com. The problem is that anyone from my LAN can't access the website. I put an alias record in DNS to point to

http://www.domian.com.

However, this isn't working or this isn't the way to resolve this issue. Any suggestions would be most helpful.

Thanks

 

[aznluvsmc]

Have you try using an A record for

http://www which

maps to the public IP address of the web server?

Did you verify that the names are being resolved correctly through the use of nslookup or ping? Did you try clearing the DNS cache from the server?

 

[luismagally]

Hi, I've seen your problem before. I have a similar problem, but before trying to explain how to fix this in my own words, try this link. The solution is a split DNS and this guy really knows what he's talking about.

 

[luismagally]

Hi, I've seen your problem before. I have a similar problem, but before trying to explain how to fix this in my own words, try this link. The solution is a split DNS and this guy really knows what he's talking about.

http://www.isaserver.org/tutorials/You_Need_to_Create_a_Split_DNS.html

 

[ITErik]

I have created an Alias under the forward lookup zone for my domain. Below is what I did.

Alias name is: www
Fully qualified name for target host is:

http://www.domain.com

How do you do an A record that will map to the IP address of the website Domian name? Is that the sam as an Alias? If you know how to map it to the IP please let me know or give an example. I can resolve the domain name by ping: domain.com (which is my Active Directory domain), but I can't resolve to

http://www.domain.com

(which is my website). NSLOOKUP works the same for me as the ping command did. I didn't clear the DNS cache. How do you do that?

Thank you for your response!!!

 

[ITErik]

I cleared the DNS cache. That didn't help.

Thanks

 

[ITErik]

luismagally-

I checked out the link and it makes sense. However, if it's also is simple as creating and an A record and mapping the IP address or name to it I'll try to do this first. If you have any hints on how to do that let me know.

Thanks,

I hope I can return the help one day, much appreciated!

 

[aznluvsmc]

I've tested this in lab environments with a simple Linksys router running NAT. On your DNS server that is authoritative for domain.com add an A host record with the name

http://www and

then type in the public or private IP address of your webserver.

When you ran ping or nslookup for the server's FQDN did the name resolve to the correct IP of the web server? If not, then you have a name resolution issue. If the name is resolving to the correct IP then it may very well be the issue with proxy servers that require a split DNS.