Networks

Ask something
Discussion Locked

DNS Server problems

0 helpful
12 replies

by darts32

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Looking for some help.

I set up a test computer called mynamedc at 192.168.1.100 to play with Active Directory (AD). This computer runs Windows 2003 Server and acts as both the DNS server and the first AD domain controller on my test domain, which I call myname.com. Everything works fine except DNS on the DC. I cannot get to myname.com when logged into the domain. nslookup says:
default server: unknown
address: 192.168.1.100

I can browse every other site but myname.com when logged into the domain. What am I missing?
My ISP nor me is hosting the domain name I am using for my domain.

12 replies

by darts32

ISP Setup:
Using Roadrunner for ISP. ISP modem to Linksys router BEFSR41 to a switch.

by bobsta

Phone your ISP and aske for DNS ip's.
Open DNS managment console and setup DNS Forwarders, insert IP's given by ISP, restart Server.

by mike_w

How are you trying to access myname.com? In the DNS server on the domain controller there should be several service record entries for the domain myname.com is this is the name of the AD domain. If you can login to the domain then the name resolution is at least somewhat functional otherwise your PC would not be able to find a domain controller for the domain.

by darts32

added the ISP's DNS on the forwarders tab. No change.

accessing myname.com in a browser. The service records are the same as the ad domain. In order for the pc's to join the domain I must specify a dns server on the client pc's. In this case 192.168.1.100. This is another issue I have as well.

by zaferus

If I understand your issue correctly:

This issue can occur when your internal domain is the same as your external domain. Since your DNS server will try to resolve an address internally first - it will direct internally first. And since your web site isn't internal it fails the server resolution.

On your DNS - go to forward lookup zones and create and Alias (A) record for www pointint to it's correct IP.

This will create the DNS record for www.myname.com so that internally you can resolve your own web site! If your server is internal just have this direct to 192.168.1.100, and ensure you have proper web access setup.

-Z

by adembo

You said that you can browse every other site except for myname.com. So what do you mean by browse? Are you talking about IE? If so, you then have IIS setup to have your web page. Is that the case? If not, of course you will not be able to browse your DC with IE.

Your primary DNS server is 192.168.1.100? Can you ping your DC name from the DC itself?

With the address you have, that almost sounds like you are getting the IP from a DHCP server. Is that the case? If so, then that is probably your problem. You would need to statically assign the IP and the DNS server to your DC. Be sure to have it on the same subnet if you do do that.

by darts32

Thank you for your comments.

Yes I did mean browse with IE. I am not hosting my site and it is on a different ISP than my own. I can ping the DC from itself and the address is static.

by adembo

Well I guess this does not answer your question, but just something to think about. It is never a good idea to have your domain name the same as your external web address. That can pose security risks. You obviously have spent a great deal of time on this, but you may want to think about changing the internal domain name. Even to something as simple as myname.net and have your web site still point to myname.com

You then should not have the DNS confusion about what you are looking for. You would still need to have the DNS forwarder to the ISP DNS so you can resolve your myname.com

If you do not have the forwarder address setup properly in DNS, it will never look outside your domain to resove the web address.

This discussion is closed to new replies.