Anyone have experience with DNS resolving issues... the issue is it takes way too long to reslove the dns to one of my hosts. The domain is registered with godaddy, and pointed to ns1.west-datacenter.com and ns2.west-datacenter.com.

It looks like these are their only name servers, do you think that if I got custom nameservers from them ($10/month) that the reslove time would be faster?

Here's the other thing... it seems like my more recent sites take longer to reslove.

Can a nameserver get overloaded? If so, why wouldn't a host just get a few more boxes in their network?

-Chris

Custom name servers would not resolve quicker. All domains are going to take 24-72 hours to resolve. Your domain basically needs to spread accross the internet telling everyone that if they type your domain it should go to your server. Takes time.

If you have a dedicated IP you can give that out as it will point directly to your site.

I suspect AuraDev was not referring to the fact that it takes a long time for new domain DNS propagation.

Hey, look under DNS Report. www.dnsreport.com

Check with the SOA refresh values etc, because my current host takes the absolute maximum amount of time 72 hours - very fustrating, sometimes it's longer, up to 4 full days.

Just ask them to manually refresh their servers.... or change hosts.

After finding dnsreport.com I'm screening all my potential hosting candidates through it to find out the stuff they don't tell you.

how can it be possible that some hosts take longer. after they initialized the change it should be ok in 24 hours. Maybe they need time to process your request internally.

Originally Posted by Jcgeuze

how can it be possible that some hosts take longer. after they initialized the change it should be ok in 24 hours. Maybe they need time to process your request internally.

I hate to say this but it is not the host that is really the problem on DNS propigation/resolution. As long as they have added the entry to thier DNS servers, thier half is done. The rest of the process pretains to ISP, or who we the users use to connect to the internet. They need to updated thier records by checking nameservers for new entries and changed entries. Once they do that, then thier users or clients can see the domain.

so you are confirming my reaction. The update time should be more or less equal nomatter which host you use.

Originally Posted by Jcgeuze

so you are confirming my reaction. The update time should be more or less equal nomatter which host you use.

The only thing that would be host related would be if your ISP or user's ISP do not check the DNS servers of your host. Ask your host for the IP addresses of the DNS servers and call your ISP and see if you can have them added or updated on the ISP's side.

This is not about how long it takes between registering a domain name and when it goes live.

DNS Propagation = when you change the dns or register, it takes a while for everyone elses nameservers to update

DNS Resolution = the process of changing a domain name into the correct IP address and then connecting to the correct web server. This process is what the name servers do.

My problem is that that DNS resolution takes way long on one host and is normal on my other host, domains are both registered through godaddy. What Im wondering is this- if a host has only one name server for all of its customers, and its a large host, wouldnt that create a bottleneck in the datastream?

From my understanding the request flow would be this- I type in auradev.com, my isps nameserver resloves auradev.com into the IP, a request containing the IP and Domain are made to the hosts name server, the host grabs the correct data and sends it back.

Now- wouldnt having a billion domains on the one host server create a bottle neck. Every other host i have seen has like ns1.server1-hostcompany.com and ns2.server1-hostcompany.com, then ns1.server2-hostcompany.com and ns2.server2-hostcompany.com and so on.... so each physical server has its own Domain Name Server....

Any thoughts?

In that case a bottle neck could be created but there would need to be specfic conditions.

1: A slow line to the DNS servers, as the information from the DNS servers is very little.
2: A overloaded server, the CPU/Mem of that server would need to be taxed to the extreme as said before very little is being sent from the DNS server to your ISP on domain name request.

Alot of times when a host that has billions of domains will have a server cluster running as DNS servers with more than a 100 Mbit per a second line going to them.