·AT&T DSL Service
|reply to osravens |
Re: Why Business?
I run a server with several services including httpd, imapd, pop3d, squid, ssh, and so on. In order to get an rDNS/PTR record for email services, I would need business class to change arpa records.
In order to have registered domains point to a qualified A-Record, I need a static IP assignment of at least 1 IP.
Doing this on residential services is prohibited according to the TOS. Also, even if I chose residential services, email would never work, as class names on dynamic ips are normally black listed because the forwarding address would not match the reverse.
I.E. blahblah.dyndns.org for instance would point to something like static-xxx-xxx-XXX-XXX.bltmd.verizon.net. It would automatically get rejected (by most) because they don't match.
All my records point to a static, non changing (for as long as I have the lease) IP. My A, MX, NS, TXT, SOA, PTR all point to a qualified source. I don't have to worry about dealing with some dynamic name server making sure the IP and records are all updated and blah blah and doing voodoo to keep it all running smoothly. This is how you do it when you run a small server on a business class service.
Also, setting up many services, it is easier to use static assignments. For instance binding a particular IP or network to Apache, DoveCot, and so on. Some configs even require a static assignment or they cannot function.
So... this list could go on forever.
Hope I made it clear why I chose business over residential.