Could some MX expert help by checking this MX record syntax i n a virtual host SOA file?

Klinkefus, Dave dave.klinkefus at icn.state.ia.us
Tue Jul 18 17:03:31 UTC 2000


Don't forget the trailing dots at the end of the MX record. If you don't
have
the dot, it will attach the domain on the end. For example, an nslookup to 
mail.waldorfcanberra.com.au, will look like
mail.waldorfcanberra.com.au.waldorfcanberra.com.au.

Hope this helps.



-----Original Message-----
From: Robert Chalmers [mailto:robert at chalmers.com.au]
Sent: Tuesday, July 18, 2000 3:42 AM
To: comp-protocols-dns-bind at moderators.isc.org
Subject: Could some MX expert help by checking this MX record syntax in
a virtual host SOA file?


I'm checking the syntax of this example, but it doesn't seem right.
  I set up a similar virtual domain on my system, to check it out. The
original I found is first, followed by my set up to test the theory. I
thought I had a grip of all this - but it seems to get more confusing as I
get older :-)

This is the original, and apparently works fine.  But I thought you couldn't
put "other" domains into an soa record, as is happening  here with the
'mail' entry ....  which resolves to mail.waldorfcanberra.com.au - when in
actual fact it isn't.

> ls -t any waldorfcanberra.com.au
[ns.inature.com.au]
 waldorfcanberra.com.au.        SOA   ns.inature.com.au
hostmaster.inature.com.au. (2000060910 10800 3600 3600000 86400)
 waldorfcanberra.com.au.        NS    ns.inature.com.au
 waldorfcanberra.com.au.        NS    ns1.telstra.net
 waldorfcanberra.com.au.        MX    10   mail.waldorfcanberra.com.au
 waldorfcanberra.com.au.        MX    50   postoffice.telstra.net
 waldorfcanberra.com.au.        A     203.59.126.78
 mail                                      A     203.38.96.33
 www                                     A     203.59.126.78
 waldorfcanberra.com.au.        SOA   ns.inature.com.au
hostmaster.inature.com.au. (2000060910 10800 3600 3600000 86400)
>
................

The setup I used on my server to duplicate this, looks like this, naturally
the NS are different etc, and the mail server is my own server, however -
the nslookup is about the same ... So, is it kosher to use syntax like that
mail........A xxx.xxx.xxx entry.??
I note bind isn't complaining - but then sometimes it doesn't :-)

=============
; Nameservers
;
                IN NS   nanguo.chalmers.com.au.
                IN NS   ruby.chalmers.com.au.
                IN NS   ns1.telstra.net.
;
                IN A    203.1.96.200
                IN MX   10 mail.waldorfcanberra.com.au.
                IN MX   50 postoffice.telstra.net.
;
www             IN CNAME waldorfcanberra.com.au.
mail            IN A    203.1.96.5
=================
> ls -t any waldorfcanberra.com.au.
[nanguo.chalmers.com.au]
 waldorfcanberra.com.au.        SOA   waldorfcanberra.com.au
robert.nanguo.chalmers.com.au. (71813 10800 3600 604800 86400)
 waldorfcanberra.com.au.        NS    nanguo.chalmers.com.au
 waldorfcanberra.com.au.        NS    ruby.chalmers.com.au
 waldorfcanberra.com.au.        NS    ns1.telstra.net
 waldorfcanberra.com.au.        MX    10   mail.waldorfcanberra.com.au
 waldorfcanberra.com.au.        MX    50   postoffice.telstra.net
 waldorfcanberra.com.au.        A     203.1.96.200
 mail                                     A     203.1.96.5
 www                                    CNAME waldorfcanberra.com.au
 waldorfcanberra.com.au.        SOA   waldorfcanberra.com.au
robert.nanguo.chalmers.com.au. (71813 10800 3600 604800 86400)
>

Note, the output of my nslookup is practically the same as the original, so
apparently it works?

The bottom line of course is this.
mail.waldorfcanberra.com.au actually resolves to 203.1.96.5 - which is my
main (true, not virtual) server, also the mail server. So then 203.1.96.5
will try and handle the mail, and failing that, pass it off to
postoffcie.telstra.net ... I presume??

hmm. If this is actually the "correct" syntax, then I have a lot of changes
to make....

oh, and in addition, this then ties into the virtusertable/genericstable
thing that handles virtual users on their domains. which I think I finally
do understand... even to having to have an actual user name on the real
server so the virtual users mail works.

Anyway, thanks for any feedback on the veracity of the above syntax.

cheers
Bob










More information about the bind-users mailing list