Please could someone explain why a private name server that handled about 300 names would kill a virtual host. Bandwidth and cpu processiong would be fairly low.

I've had a number of hosting companies state the above, and yet many others seem to ignore the number of domains.

Ok nameservers are nameservers private or not, all they do is just resolve domains to a ip address, I don't see exactly what you mean...

When you say a nameserver that handled 300 names - do you mean domain names? would kill a virtual host? do you mean delete a virtual host from httpd.conf?

Hu?

your name server does not use any real resources, unless you got 1200 + then you start to see some real thump, oh maybe 0.20 on the cpu load. But even then, your dns should/would copy into the service providers dns cache so after a few days the thumping would subside.

it also does not help that there was a report, that states, somewhere in the range of 95% of all the dns calls to the root servers are not really nessassary.

Anyway never judge a server by it's cpu, judge it by the load factors that the host uses. many host load servers till they hit 2 or 3, the host you want to have is one that sit's it around 1 ( cpu usage we are talking about )

OK - as you've guessed I'm not up on running a server. I keep meaning to set one up here but never seem to get round to it.

I want to buy hosting for my domain name business and a few others. The total number of names is 250-300 variable. I'm getting hosting offers between $1 and $300+ per month. About half are saying that more than 50 names would "kill" their server. I don't understand what they are talking about. I just felt that my own name servers ought to reduce the impact if there wasn't too much traffic (well not too much graphic, and no video or audio).

well now we are not talking apples anymore. if you have 300 domain names that redirect to 1 page, then youhave extra cpu cycles that are consumed beside the local dns lookup ( you have dns lookup, go to page, load page, redirect, go to page, load page ) now if you have a busy set of names that will bog the serves ( I charge .25 per redirection after the first free names )

what you need to do is get someone to host your entire set up and make it simple, you should be able to have it done for less than $50 a month ( heck I can do it for less than $50 )

but the point here is that you need to be upfront about what you need. 200 to 400 names can crush a small host if they are not configured for it.

Mike

So would it be easier if I had one master domain and say 250 2nd level names aliased to sub-domains on the master domain. 2nd level name will be the same as the 3rd level sub-name if that makes a difference.

no it would be easyer to have 1 web page per domain
and a master index page at the selling company domains home page. sooo...

joes domains has the master index with the links to each page

each sellable domain has there own web page and a link back to the master index where the sales take place.

this way you gain the advantage of links to the for sale, and the for sale link back to the domain.

Mike

That's a better arrangement logically and commercially. Is there anything else I could do to minimise impact?

I had a look at your site, but got put off by the bandwidth overage charge. I'm paying 50 cents at the moment for some other sites.

Would you be interested in a deal if you had advertising on all pages? (can I post these suggestions in this forum?)