Big Help needed with MX (again)

Kevin Darcy kcd at daimlerchrysler.com
Thu Jul 5 19:50:15 UTC 2001


MX records just say "deliver mail for name X to server Y" (or multiple
MX targets, for redundancy). As for *forwarding* mail, i.e. accept mail on
server Y and send it to server Z, typically DNS is *not* used for that.
It's typically something you configure within the mail server itself, with
e.g. a mailertable, smarthost, nullclient, mail aliases or whatever.


- Kevin
BCC wrote:

> Hi, I have a linux box (RH 6.2) that needs help.
>
> Long before I arrived, this machine was also set up as a webserver and
> as a nameserver but, sadly, it was set up like *&!# (I made some posts
> earlier about this) and needs some work.
>
> As I am 1. Doing this for a friend 2. Not getting paid for it 3. Can't
> take too much time from my real job, and 4. Know squat about how named
> and MX and nameservers work, I need some help on how to get this thing
> set up correctly.
>
> What I need it to do is simply be a webserver, and forward email to an
> exchange server on port 25.  Im going to assume that I must have named
> running to forward email?  If this is an incorrect assumption, I would
> love to hear how else I can do it, as I dont care if this machine is
> running named or not.  I have other nameservers I can use if need be,
> and can re-register the domain with those servers.
>
> But if I must use named, can someone please spare a moment to look at
> these config files and tell me what is wrong?  named locks up about once
> a week, and uses 99% of the cpu and stops forwarding email.  The
> extremely helpful responses from my earlier posts on this subject
> clearly state that there is a major problem with DNS, but I need help
> getting it straight.
>
> In case its useful, the two nameservers I have access to are ns1.cts.com
> and ns2.cts.com.  The only zone that is important is nextproteins, all
> the other crap is kind of meaningless, as nextproteins.com is the
> ONLY email domain.
>
> I am including the config files for everyone to check out.  I know this
> is asking a lot but it would really help me out.
>
> Thanks in advance for any help!
> Bryan
>
> /etc/named.conf
> ------------
> options {
>         directory "/var/named";
> };
>
> zone "." in {
>         type hint;
>         file "named.ca";
> };
>
> zone "0.0.127.in-addr.arpa" in {
>         type master;
>         file "named.local";
> };
>
> zone "133.216.204.in-addr.arpa" in {
>         type master;
>         file "204.216.133";
> };
>
> zone "nextproteins.com" in {
>         type master;
>         file "nextproteins";
> };
>
> zone "isisprotein.com" in {
>         type master;
>         file "isisprotein";
> };
>
> zone "npisurvey.com" in {
>         type master;
>         file "npisurvey";
> };
>
> zone "designerwhey.com" in {
>         type master;
>         file "designerwhey";
> };
>
> zone "ultimatepunch.com" in {
>         type master;
>         file "ultimatepunch";
> };
>
> zone "designerprotein.com" in {
>         type master;
>         file "designerprotein";
> };
>
> zone "bigwhey.com" in {
>         type master;
>         file "bigwhey";
> };
>
> zone "nextraproteincrunch.com" in {
>         type master;
>         file "nextraproteincrunch";
> };
>
> zone "staronthejar.com" in {
>         type master;
>         file "staronthejar";
> };
> --------
>
> /var/named/named.local
> ----------------
> @               IN      SOA     localhost.      root.localhost. (
>                         1997022700 ; serial
>                         28800 ; refresh
>                         14400 ; retry
>                         3600000 ; expire
>                         86400 ; default_ttl
>                         )
> @               IN      NS      localhost.
> 1               IN      PTR     localhost.
> ----------------
>
> /var/named/nextproteins
> ---------------
> nextproteins.com. IN SOA webserver.nextproteins.com.
> webserver.nextproteins.com. (
>                         2000110507      ; serial, todays date + serial
>                         8H              ; refresh, seconds
>                         2H              ; retry, seconds
>                         1W              ; expire, seconds
>                         1D )            ; minimum, seconds
>
> nextproteins.com.               IN NS
> webserver.nextproteins.com.
> nextproteins.com.               IN MX 0
> exchange.nextproteins.com.
>
> localhost.nextproteins.com.     IN A            127.0.0.1
> nextproteins.com.               IN A            204.216.133.114
> webserver.nextproteins.com.     IN A            204.216.133.114
> exchange.nextproteins.com.      IN A            204.216.224.18
>
> www.nextproteins.com.           IN CNAME
> webserver.nextproteins.com.
> -----------------





More information about the bind-users mailing list