Dns Issues: Can Access Via Ip Address But Not The Host Name

E

eaglehosting

New member
Joined
Jul 2, 2011
Messages
4
Location
Louisiana
Hello,

I am currently running Windows Server 2008 Enterprise Edition on one of my Dell laptop computers. I am using this for educational purposes as to decide if I would like to switch my existing domains to my local network instead of using a third party. I have successfully installed AC DC and DNS onto the server. I have also configured my router to forward the necessary ports to my server's static IP address. I have tested the server using a connection outside of my local network using the public IP address, which works. However, I am having problems setting up the DNS to forward to the public IP using the host name. I have searched numerous forums, websites, and videos, but I am still unable to successfully configure the DNS.

The methods I have tried includes:
Creating a new forward zone
Adding new Host & Alias records to that zone (www.mydomain.com, mydomain.com)
Creating a NS1.mydomain.com host to add to the Name Servers

I have also performed several instances of the "nslookup" command.
On my server computer the server always returns as "unknown" and returns the private IP as the address. However, when I perform this command on an outside computer it returns "non-authoritative" IP addresses, none of which are mine.

I apologize for the large post but I would like to describe my problem in detail for anyone who may be capable of assisting me. Please provide any information or advice possible. Thank you in advance for your help!
 
I am having problems setting up the DNS to forward to the public IP using the host name
Click to expand...

I don't understand this point.

Your PC is a DC, where are your clients? On the same network?

I really don't understand what are you trying to do!
 
Okay, I'll start over. I am trying to host my websites on my home network. My PC is a Domain Controller. I AM capable of viewing my test site externally using ONLY my public IP address. My research is showing that the problem is most likely DNS Name Resolution. For example, I want people outside of my network to be able to access my websites using a host name (mydomain.com). When I set up my A(Host) records to point to my public IP address, the domain name is not found at all (internally nor externally). When I set up my forward-lookup zones using my private IP address (192.168.x.x), I am able to connect and view the website ONLY locally. My goal is to make the website available on the Internet. I need assistance in setting up my own DNS servers on my local network to do so. I do not want to use any third parties.
 
Your DNS must be public, people must be able to contact it in order to resolve the name / IP. I really don't suggest you to use the same DNS for external and internal purpose... anyway, is up to you.

Now, if you have an A record (let's say mysite.mydomain.com), and you CANNOT reach it from INSIDE, first of all you must check if at least your DNS knows how to resolve it, in other words, if you ping mysite.mydomain.com, you should see the IP address of your website. If this is correct, the problem could be the routing.
 
Okay, I set the domain IP in the IIS manager and the DNS A records to my public IP but nothing is coming up. When I tried to ping the domain name it showed IP addresses that were not mine. Could the problem be related to my ISP? Do you think I should contact them for assistance?
 
Wait, I assume that your domain name is managed by a webhoster or ISP, so they must provide name resolution, not you!

Anyway, if you ping and you get IP ADDRESSES which are not yours... you should investigate WHO is the owner of those addresses.
 
Back
Top