Networks

Ask something
Discussion Locked

DNS Reslove?

0 helpful
7 replies

by big trent 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Ok, I have built a uploaded a client's web site, if i use the IP address in my browser it will come up fine, if I use the url it doesn't relsolve, tracert has the same problem, tracert will not work for the url, but will work fo r the ip, when i go to samspade.org I can use both ip, and URL, nslookup doesn't reslove with IP, or URL, we updated the site last week with the correct name servers, what i would like to know is how to determine who is dropping the ball, what name server is it getting dropped at and why.

7 replies

by timwalsh

The first place to check is the DNS server hosting the web site.

Some things to remember:

DNS Forward lookup zones resolve IP addresses to host names.

DNS Reverse lookup zones resolve host names to IP addresses.

Usually, if an IP addresswill resolve, but the URL (or host name) won't resolve, either a Reverse lookup zone has not been created, or the proper records in the Reverse lookup zone have not been created.

The bottom line is that if the DNS server hosting the website is not configured correctly, name resolution will NOT work properly. Also realize that once DNS IS configured properly, it may still take some time for this information to be propagated to the Internet TLD root servers.

Hope this helps.

by tonysci

It would be getting dropped at the hosting companies DNS servers. If you updated the name servers and they show correctly when you do a whois at the site then the DNS of the hosting company is configured incorrectly (if you type in the IP and it shows your uploaded site as you say then it is pointing correctly from the domain registrar to the hosting company).
So DNS (or IIS) needs to be reconfigured at your hosting company.
The A record for the site could be configured incorrectly in DNS. Or if IIS is configured incorrectly it may be that the DNS record points correctly but in IIS under your website name (web site, advanced, multiple identities)there is nothing defined. It should be listed like the following.

myname.com
www.myname.com

(plus more depending on how you use the domain)
but that is bare minimum.

If this is left empty it can cause problems. (This is on windows based servers)

Hopefully this helps.

by joseph moore

I agree with the majority opinion on this. After you configure the nameservers when you register the domain with your registrar, the company that owns the nameservers (usually, the ISP) have to add A and/or MX records (maybe even CNAME records) in their DNS servers. These records would resolve the WWW portion of WWW.COMPANY.COM, for example.

What domain did you register? We could do extended nslookups to see what looks wrong.

This discussion is closed to new replies.