Search Again: Re: How badly have I screwed up? From: Men & Mice Support Date: Friday, January 4, 2002 Time: 2:49:13 am At 7:12 AM -0600 1/1/02, Len Conrad wrote: >>officemedic.net. 3600 A 12.39.138.249 >>www.officemedic.net. 3600 A 12.39.138.249 >>officemedic.net. 3600 NS ns1.officemedic.net. >>officemedic.net. 3600 NS ns2.officemedic.net. > >ns2 is not responding. > >>officemedic.net. 3600 MX 10 mail.officemedic.net. > >... don't use CNAMEs for MX and NS hostnames, only canonical hostnames. He didn't. The A record is 4 records down. >>officemedic.net. 3600 MX 20 >>mail2.officemedic.net. > >you don't have an A record for mail2 Yes he does. Again, 4 records down. >I suggest the preceding two be changed to mx1.officemedic.net. and >mx2.officemedic.net. > >then create names for pop, smtp, webmail, imap so you have >functional hostnames for various mail functions. We should probably update the examples in the documentation for QuickDNS to have a setup like this. It makes good sense. Of course, if you're not offering imap or webmail service, for example, then you don't need these records - they can always be added later. >>ns1.officemedic.net. 3600 A 12.39.138.244 >>ns2.officemedic.net. 3600 A 12.39.138.144 >>mail.officemedic.net. 3600 A 12.39.138.244 >>mail2.officemedic.net. 3600 A 12.39.138.244 Note that the preceding two A records resolve to the same IP address. This is generally pointless. Is this a typo, or do you not have a separate backup mail server? >>lists.officemedic.net. 3600 A 12.39.138.244 >>ftp.officemedic.net. 3600 A 12.39.138.249 >> >> >>An example of a virtual domain is officemedic.com: > >that isn't a virutal domain, is it's the officemedic.com zone. Yes, it is a virtual domain. The primary domain ends in "net", not "com". >>officemedic.com. NS ns1.officemedic.net. >>officemedic.com. NS ns2.officemedic.net. >>officemedic.com. MX 10 >>mail.officemedic.net. >>officemedic.com. MX 20 >>mail2.officemedic.net. >>officemedic.com. A 12.39.138.249 >>www.officemedic.com. A 12.39.138.249 >>lists.officemedic.com. A 12.39.138.244 >>mail.officemedic.com. CNAME mail.officemedic.net. >>ftp.officemedic.com. CNAME ftp.officemedic.net. >> >> >>Question 1: How badly have I screwed this up? > >about typical. :))) > >>Question 2: What should the reverse domain(s) look like? > >hostname PTR hostname. Eh? I wouldn't describe the PTR record name as a "hostname". More like: reverse-name PTR hostname Of course, the reverse zone needs more than just PTR records, it needs NS records, too. Like this: zone.name. NS server.name. reverse.name. PTR hostname. Of course, repeat each type of record as needed - one NS record per server (just like any other zone) plus one PTR record per IP address. >>Question 3: Why would EIMS all of a sudden be telling me "The following >>message could not be delivered to list@lists.officemedic.net because the >>host lists.officemedic.net does not exist"? > >probably because EIMS is too dumb to resolve YOUR ERROR of a CNAME >into the (exising A record): > >mgw1# dig lists.officemedic.net > >; <<>> DiG 8.3 <<>> lists.officemedic.net >;; res options: init recurs defnam dnsrch >;; got answer: >;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4 >;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 2 >;; QUERY SECTION: >;; lists.officemedic.net, type = A, class = IN > >;; ANSWER SECTION: >lists.officemedic.net. 1H IN CNAME ns1.officemedic.net. >ns1.officemedic.net. 1H IN A 12.39.138.244 > >;; AUTHORITY SECTION: >officemedic.net. 1H IN NS ns2.officemedic.net. >officemedic.net. 1H IN NS ns1.officemedic.net. > >I suggest in your virgin state of newness that you replace all >CNAMEs with A records. Interesting that the data you quote above doesn't match the records in the original list posting. Are we talking about a zone that's not yet live, and that's replacing the current zone? Also, of course, there's nothing wrong with the CNAME record you found, Len. It would be better if there were an MX record instead, of course, since some mail servers (like EIMS) don't handle A records as well as they handle MX records, but the CNAME record is within the rules. ____________________________________________________________________ Chris Buxton Men & Mice support@menandmice.com Making DNS Easy

Messages In This Thread: How badly have I screwed up? by Don Morris on Jan 1, 2002 at 2:44:34 am Re: How badly have I screwed up? by Len Conrad on Jan 1, 2002 at 5:13:21 am Re: How badly have I screwed up? by Don Morris on Jan 3, 2002 at 10:40:49 pm Re: How badly have I screwed up? by Men & Mice Support on Jan 4, 2002 at 2:49:13 am Re: How badly have I screwed up? by Men & Mice Support on Jan 4, 2002 at 3:10:08 am Re: How badly have I screwed up? by Don Morris on Jan 4, 2002 at 9:07:55 am Re: How badly have I screwed up? by Don Morris on Jan 4, 2002 at 3:10:28 pm Re: How badly have I screwed up? by Len Conrad on Jan 4, 2002 at 3:27:21 pm Re: How badly have I screwed up? by Don Morris on Jan 4, 2002 at 4:40:29 pm Re: How badly have I screwed up? by Len Conrad on Jan 4, 2002 at 4:53:37 pm Re: How badly have I screwed up? by Don Morris on Jan 4, 2002 at 6:07:41 pm Re: How badly have I screwed up? by Len Conrad on Jan 4, 2002 at 6:32:54 pm Re: How badly have I screwed up? by Men & Mice Support on Jan 4, 2002 at 7:24:33 pm Re: How badly have I screwed up? by Men & Mice Support on Jan 4, 2002 at 7:27:58 pm Re: How badly have I screwed up? by Men & Mice Support on Jan 4, 2002 at 7:29:49 pm Re: How badly have I screwed up? by Don Morris on Jan 4, 2002 at 9:33:03 pm Re: How badly have I screwed up? by Don Morris on Jan 4, 2002 at 9:36:40 pm Re: How badly have I screwed up? by Len Conrad on Jan 4, 2002 at 9:44:07 pm Re: How badly have I screwed up? by Don Morris on Jan 4, 2002 at 10:29:51 pm Re: How badly have I screwed up? by Len Conrad on Jan 5, 2002 at 4:17:19 am Re: How badly have I screwed up? by Men & Mice Support on Jan 5, 2002 at 6:32:21 am Re: How badly have I screwed up? by Don Morris on Jan 5, 2002 at 11:08:01 pm