Re: [cobalt-users] Getting Mail working for virtual host

[flash22@xxxxxxx]

On Wed, 2 May 2001, Rick Boucher wrote:

> Hey Thanks for all the help.  I knew I was asking a base question and things
> seem to be working better now.  Couple of follwup questions.
> 
> 1.  I was told that I should not put an A record for orcasonline.com in my
> spritnw.com zone file. I checked the file, which was all generated by the
> Cobalt Admin scripts, and the only reference to orcasonline.com were two NS
> records.
> 
> spiritnw.com in NS ns3.orcasonline.com
> spiritnw.com in NS ns1.orcasonline.com
> 
> This appears in dig spiritnw.com  in the authority section.
> 
> there is then an additional section, in the dig spiritnw.com, which has
> 
> ;; ADDITIONAL SECTION:
> ns1.orcasonline.com.    12H IN A        204.201.135.130
> ns3.orcasonline.com.    12H IN A        204.201.136.62
> 
> I tried dig amazon.com and the report was similar.  So I am stumped as to
> how the cobalt admin script created a sloppy zone file.  I want it right and
> perfect not sloppy.

nope, it's correct as is now at least, the listed nameservers go with the
zone, and the A records you are seeing are additional data passed by the
nameserver, so they are ok ...

> Below is the zone file for spiritnw.com as produced by the cobalt admin
> mail.spiritnw.com.      in      a       204.201.136.3
> spiritnw.com.   in      a       204.201.136.3
> spiritnw.com.   in      mx      30 mail.spiritnw.com.
> www.spiritnw.com.       in      a       204.201.136.3

> So help me out here.  Mail does work now. But what is the proper way to do
> it?

This is fine....

It's possible the stray A record for orcasonline.com that looked like it
was in spriitnw.com's zone really wasn't, but was passed as additional
info because the nameserver thought it was needed to resolve spiritnw's
nameservers....it's somewhat hard to tell this from what the nameserver
says vs what's really in the zone file...

gsh