DNS Hosting Policies?
Cheeze asks: "What do other administrators do about domain registering? Where I work, we require to either be the administrative or technical contact for the domain. Before this policy was implemented, we had no way of knowing if we were the authoritative DNS for our DNS customers. Sure, we can probe whois every day, looking up every single domain, but that puts a heavy load on their servers and what usually ended up happening is there would be about 20% false DNS entries, causing our customer's grief. What do other companies do in this situation? Is that a common practice?" What other (or alternative) policies do DNS hosting services implement that you all like. Are there policies in place at some DNS hosting services that you think are unfair? Why?
"Our reasons behind implementing this practice :
- Increased security - you can turn off the spammers when they violate your terms of service.
- When they try to change domain name servers with their registrar, an e-mail is usually sent to the administrative and technical contacts. This is a good notification that you just lost a customer and can take the record out of your DNS.
- You can hold the domain for ransom when/if the customer does not want to pay their bill (evil, but sometimes necessary)."
Spammed? Don't sign up for lists...I get about 1 Email from them a month, and it't Tim's monthly info mail. If one mail a month is too much for you, then you don't really need Email. DynDNS work well with a home-brew perl script I wrote to do my own Dynamic DNS updates to make my mail server and such appear as the name I want them to be, not the name my Cable Modem provider picked.
This space for rent. Call 1-800-STEAK4U