You're kidding, right? It becomes a matter of disservice when I stop/start a nameserver so we can add "im-cool-i-have-my-own-domain-now-what-do-i-do-with-it.com". It flushes the caches and causes dns lookups for our clients to take longer, not to mention the fact that it increases traffic on the global net. If every isp/nsp did this, the entire cacheing function of DNS would be moot. Noone would have a live cache. When someone signs up for hosting services with us, they are not told "your zone entry will be live in our servers before I hit the send button on your domain app." They wouldn't have a clue what I was talking about to begin with. Secondly, until the app is processed, my servers AREN'T authoritative for the domain. More than once, I have sent in a registration for a domain that was available in whois only to have it rejected. Some other person beat me to the punch by a few minutes and the domain was awarded to them. At 04:40 AM 11/21/98 -0800, Randy Bush wrote:

...

The reason I say this is that some folks automatically reload their nameservers which have tens of thousands of domain names once a day and have clients that want domains registered on the same day they request them. (queuing is not an option.)

if they intend to serve those clients, as opposed to pretending to do so, then they should load thier servers when they are pretending to do so.

randy

------------------------------------------------------------------ Get your *FREE* Parked Domain account at http://www.EZ-Hosting.Com ------------------------------------------------------------------ John Fraizer | __ _ | The System Administrator | / / (_)__ __ ____ __ | The choice mailto:John.Fraizer@EnterZone.Net | / /__/ / _ \/ // /\ \/ / | of a GNU http://www.EnterZone.Net/ | /____/_/_//_/\_,_/ /_/\_\ | Generation