can't access own web site typing www.mydomainname.com 1

[ska4reak]

hello everybody...
i host my website , and run dns services for my website from my home (i have leased a static ip from my dsl provider)...i use win2k server for those purposes...
i have also implemented active directory services in my home network...my web server and my active directory domain name controller are the same named ns1... everything works well and good but for one small problem...when i type

http://www.mydomainname.com

on my browser from within my home network i get pointed to my modem/router provided by my dsl provider...of course

http://www.mydomainname.com

if typed from anywhere else in the world, serves up the correct pages from my web server...in order to view my own site, i need to type the lan ip address of my web server that being ns1...i'd like to be able to type

http://www.mydomainname.com

from within my lan and view my pages...what should i do? thanks in advance..

 

[markdmac]

create a hosts entry and point it to your internal IP address. The HOSTS file gets checked before DNS so it will head it off at the pass.

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark

 

[ska4reak]

mark..it worked for mydomain.com...thanks a bunch for that...but i type

http://WWW.mydomain.com

on the browser, i still get pointed to my router...what am i doing wrong? but

 

[Jpoandl]

Is your internal domain name the same as your internet domain name?

This will cause you some trouble...next time your would be better off naming the two domains something different.

The problem is (if they are the same domain name), your internal DNS server is authoritative and responsible for resolving DNS for your internal domain. If you internet domain is the same name, you will have trouble forwarding requests to another DNS server. This is becuase your internal DNS server will believe if the host does not appear in my database, the host must not exist. On the other hand, if your domain names are different, your DNS server will realize that the request if for a domain that it is not responsible for. Therefore, your internal DNS will forward the request to another DNS server (you ISP DNS servers.)

You have to delete the "." root zone in your internal DNS server in order to forward DNS lookups. Once it is deleted, you will be able to add forwarder IP addresses. If the domain names are different, this will resolve your problem.

As an alternative, you can create a manual host record for

http://WWW in

your internal DNS server. Link this with the IP address of your web server.

-hope this helps...

Joseph L. Poandl
MCSE 2003

If your company is in need of experts to examine technical problems/solutions, please check out

http://www.NJCOMPUTERNETWORKS.com

(Sales@njcomputernetworks.com)

 

[markdmac]

ska4freak,

You can add an additional HOSTS entry for

http://www.domain.com

if you don't want ot be messing with your DNS.

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark

 

[vbrocks]

Hosts

IP address Hostname Alias

192.168.254.4 mydomain.com

http://www.mydomain.com

 

[Numbnortel]

Hi all,

I am a newbie to 2000 server and want to do the same and eliminate our hosting service. Since most of our items I create for the web sites this would be more economical.

Can someone give me a quick rundown of the setup to host on the server or from it. I have already gotten the ip address to send out for the registration.

Currently I produce the and run the intranet off of the server for our inhouse sales area.

Thanks

 

[markdmac]

Numbnortel, If you already have an Intranet running you just need to configure your server with a public IP or use a firewall to redirect requests to your IIS server.



I hope you find this post helpful. Please let me know if it was.

Regards,

Mark