Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I am trying to get my domain to point to my server correctly. In my domain manager I had to register a custom nameserver (instead of just pointing it to the IP for some reason), which I did as ns1.mydomain and ns2.mydomain. I then in windows server setup the DNS role and configured DNS manager with the two forward lookup zomes and set their host(a) to their respective IPs.

When I lookup my domain I don't get anything (I configured this over 24 hours ago), however if I go to ns1.mydomain I get the IIS welcome page (expected).

This is my first time setting up a windows box so I think I am just missing a step which is obvious.

any help is greatly appreciated

share|improve this question

1 Answer 1

up vote 1 down vote accepted

EDIT

Since ns1 and ns2 belong to you and your registrar is already pointing to them, there is likely something wrong with your DNS zone. Find your zone under forward lookup in the DNS snap-in, and fire up properties. Under the name servers tab, do you see ns1 and ns2 in there? Make sure it is a FQDN like ns1.mydomain.com. Under the general tab make sure it is a primary zone, since I am assuming you do not have active directory installed. Under the security tab, make sure the 'everyone' person has read access.

For the A records, you are right to have public IP's in here since this is your public authoritative DNS server (and web server, but that's not as important).

If you go to the properties of the DNS server itself in the DNS snap in, go to forwarders and remove them. You want to check the box to use root hints. If you have NS1 and NS2 listed as forwarders, that means they forward to themselves when they can't look something up and that is bad. Under the monitoring tab do a simple query test and recursive query test and let me know what you find.


It sounds like you have DNS setup fine on the server, but where is the authoritative name server? Say you are using GoDaddy, you would need to specify the public IP of your new windows server as the authoritative name server. Make sure you have port 53 open on your firewall, as that is what DNS uses.

To expand upon the authoritative name server, it is the one that says that example.yoursite.com should point to 66.103.21.201 (or whatever). For my domains, the authoritative name servers are owned by GoDaddy and Network Solutions. Given that, I use their DNS edit page to specify my A records. I've found it takes about an hour to update if the TTL is set at 3600. It won't go any faster.

If a workstation in my network wants to do a DNS lookup, it first asks the local windows server. Say I am looking up google.com. My local server isn't the authoritative name server and let's also say it has never seen google.com before so it hasn't cached the DNS record. It will then use the forwarder you have specified to ask the next DNS server up the tree what the IP is. If that server isn't authoritative, it will continue upwards until it gets the official answer. I am guessing that this scenario is what you have, which means your fix is to add all those A records to your domain registrar's DNS page since they are probably the authoritative name server.

As an aside, don't put public IP's on the A records for your subdomains on your DNS server, unless you have your firewall setup for proper loopback NAT rules. Use local IP's (like 192.168.x.x) so internal workstations that do a DNS query for another internal server will get the local answer and not have to make an extra trip to the internet.

share|improve this answer
    
I registered the custom dns through their site to point to my public IP, so that may have been all I needed for that, so I guess I'm confused if that would be the authoritative name server or if the DNS I setup on the windows machine would be it. The DNS service and IIS are on the same machine so should I set the a records to localhost? The exception is also set in windows firewall –  dreadlocks1221 May 24 '12 at 1:15
    
The authoritative name server is what is specified by the registar. The registar is the ultimate level of authority we care about, and that is where you specify the domain's name servers. Since you have that set, there is nothing you need to do there since your A record on the registrar's page is all set. –  Bill Sambrone May 24 '12 at 1:30
    
When users that are internal talk to the local DNS server, they get the local A record because it is explicitly specified. If it wasn't, then traffic would be forwarded out to the internet where your registrar's DNS server would respond, then your firewall would need the loopback rule. Since DNS and IIS are on the same box, you can still have the same A record of site.example.com points to 192.168.1.5 or whatever it's internal IP is. –  Bill Sambrone May 24 '12 at 1:31
    
So I guess I'm confused why it isn't loading after 24 hours. My site is chicagobluesnetwork.com ns1.chicagobluesnetwork.com and ns2.chicagobluesnetwork.com. I'll leave the A record alone for now because with an external IP it should still forward correctly and I can try localhost once it starts working –  dreadlocks1221 May 24 '12 at 1:56
    
In whois the name server is set correctly. –  dreadlocks1221 May 24 '12 at 2:05

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.