On Tue, 22 Apr 2003, David Phillips wrote: > Another problem is that a CNAME cannot exist for a name if there are any > other records for that name, regardless of the type. This means you > can't have both a CNAME and an MX record for a name. You mean this is illegal: mail A 10.0.0.1 MX 5 mx1.example.com. MX 5 mx2.example.com. MX 10 offsitemx.example.com. pop CNAME mail What RFC is that in? That's pretty common practice, and has never broken anything for me.. Or are you just saying that you can't have *different* MX records for the CNAME than the record it's pointing to? That should be self-obvious -- it's a pointer. So if you don't use cnames at all, how do you do virtual hosting? IE: webserver.example.com. A 10.0.0.2 www.customer1.example.com. CNAME webserver.example.com. www.customer2.example.com. CNAME webserver.example.com. www.customer3.example.com. CNAME webserver.example.com. This is especially important if, say, www.customer3.example.com is hosted on the customer's own DNS server.. then if you need to change webserver's ip address, it doesn't affect the customer, you just do it. If the customer was adding an A record to your IP, you'd have to make sure that they also update their DNS servers when the change is made.. speaking from personal experience, customers have a tendancy to ignore the three warnings in advance of the change and then they get all pissed when their web site stops working. -- Nate Carlson <natecars at real-time.com> | Phone : (952)943-8700 http://www.real-time.com | Fax : (952)943-8500 _______________________________________________ TCLUG Mailing List - Minneapolis/St. Paul, Minnesota http://www.mn-linux.org tclug-list at mn-linux.org https://mailman.real-time.com/mailman/listinfo/tclug-list