[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] Getting Mail working for virtual host
- Subject: Re: [cobalt-users] Getting Mail working for virtual host
- From: "Gerald Waugh" <gerald@xxxxxxxxx>
- Date: Tue Apr 24 13:37:05 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
> "Rick Boucher" <cobalt@xxxxxxxxxxxxxxx> wrote
> <SNIP>
> > I have a virtual domain setup (on a different ip) spiritnw.com set up
> > with www.spiritnw.com (I'd actually like o use mail.spiritnw.com)
> > I have an MX record setup mapping spiritnw.com to www.spiritnw.com
> > as the example shows.
> >
> > I send mail to user@xxxxxxxxxxxx and it bounces with the folowing:
>
> Looking at your DNS records.
Sorry, I was probably a little short on the last email.
Everything is looking better now. ;-)
Whois database says the following are your nameservers:
NS3.ORCASONLINE.COM
NS1.ORCASONLINE.COM
[root /root]# dig spiritnw.com @NS1.ORCASONLINE.COM MX
; <<>> DiG 8.3 <<>> spiritnw.com @NS1.ORCASONLINE.COM MX
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 4
;; QUERY SECTION:
;; spiritnw.com, type = MX, class = IN
;; ANSWER SECTION:
spiritnw.com. 1D IN MX 30 mail.spiritnw.com.
;; AUTHORITY SECTION:
spiritnw.com. 1D IN NS ns2.orcasonline.com.
spiritnw.com. 1D IN NS ns3.orcasonline.com.
spiritnw.com. 1D IN NS ns1.orcasonline.com.
;; ADDITIONAL SECTION:
mail.spiritnw.com. 1D IN A 204.201.136.3
ns1.orcasonline.com. 12H IN A 204.201.135.130
ns2.orcasonline.com. 12H IN A 204.201.135.131
ns3.orcasonline.com. 12H IN A 204.201.136.62
++++++++++++++++++++++++++++++++++++++++++++++++++
[root /root]# dig spiritnw.com @NS2.ORCASONLINE.COM MX
; <<>> DiG 8.3 <<>> spiritnw.com @NS2.ORCASONLINE.COM MX
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 3
;; QUERY SECTION:
;; spiritnw.com, type = MX, class = IN
;; ANSWER SECTION:
spiritnw.com. 23h51m47s IN MX 30 mail.spiritnw.com.
;; AUTHORITY SECTION:
spiritnw.com. 1d22h12s IN NS NS3.ORCASONLINE.COM.
spiritnw.com. 1d22h12s IN NS NS1.ORCASONLINE.COM.
;; ADDITIONAL SECTION:
mail.spiritnw.com. 23h51m47s IN A 204.201.136.3
NS3.ORCASONLINE.COM. 11h53m37s IN A 204.201.136.62
NS1.ORCASONLINE.COM. 10h37m49s IN A 204.201.135.130
;; AUTHORITY SECTION:
spiritnw.com. 1D IN NS ns2.orcasonline.com.
spiritnw.com. 1D IN NS ns3.orcasonline.com.
spiritnw.com. 1D IN NS ns1.orcasonline.com.
;; ADDITIONAL SECTION:
mail.spiritnw.com. 1D IN A 204.201.136.3
ns1.orcasonline.com. 12H IN A 204.201.135.130
ns2.orcasonline.com. 12H IN A 204.201.135.131
ns3.orcasonline.com. 12H IN A 204.201.136.62
++++++++++++++++++++++++++++++++++++++++++++++
[root /root]# dig spiritnw.com @NS3.ORCASONLINE.COM MX
; <<>> DiG 8.3 <<>> spiritnw.com @NS3.ORCASONLINE.COM MX
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 3
;; QUERY SECTION:
;; spiritnw.com, type = MX, class = IN
;; ANSWER SECTION:
spiritnw.com. 1D IN MX 30 mail.spiritnw.com.
;; AUTHORITY SECTION:
spiritnw.com. 1D IN NS ns3.orcasonline.com.
spiritnw.com. 1D IN NS ns1.orcasonline.com.
spiritnw.com. 1D IN NS ns2.orcasonline.com.
;; ADDITIONAL SECTION:
mail.spiritnw.com. 1D IN A 204.201.136.3
ns1.orcasonline.com. 12H IN A 204.201.135.130
ns2.orcasonline.com. 12H IN A 204.201.135.131
It is not good practice to put orcasonline.com 'A' records in
the spiritnw.com zone file. It won't break anything, but to
someone looking at your records it indicates sloppy admin.
All 3 nameservers are giving the same answer for the MX record
now!
GOOD!
It is also good practice to use a backup mail server, but it
is not always done!
ns1 and ns3 both report ns2 as being authoritive for the
domain. For consistency with the Whois database,
you may want to get rid of ns2, or correct it's record,
and the root database.
.
Reverse works even though it's not your name, it's
better than nothing.
Name: prop.mmf.gmwnet.com
Address: 204.201.136.3
Aliases: 3.136.201.204.in-addr.arpa
mail.spiritnw.com is reachable
Name: mail.spiritnw.com
Address: 204.201.136.3
How is it working?
You may want someone else to try it, from a different
location (avoiding some cached data)
Gerald