MX Record Modification for one of my users

[mrproducer]

Hello.

I'm fairly new to direct admin and seem to have already run into an issue with one of my clients.

My client wishes me to change his MX record to an IP# that he has supplied.

I am a reseller, so his account is listed under mine as a user.

I went to his directadmin pannel/email/mx records, when I clicked on MX Records I recieved this message:

Cannot modify MX records

Details

You do not have permission to add records to your zone

Can you use an IP# for mx records?
Can i setup an account under mine with a different MX Recrod?
Are they out of their mind?

any help would be greatly appreciated.
thank you,
Patrick

 

[mrproducer]

IP# won't work, then how?

I have read that MX Records can not point to an IP# as my client has requested.

Can I modify the A record for mail to point to their IP?
Would I also modify the POP A Record for their IP?


I'm guessing that they are trying to use their own server for email, but my servers for the website. I know that they want to leave large amounts of email with large file attachments on their servers as an archive for projects, and they don't want to pay for the large storage space that they estimate they would need.

I have enabled DNS for them in DirectAdmin. I'm just lost on this whole idea.

any help is always appreciated. thanks.

Patrick

 

[Icheb]

Here we go:

You should remove the existing A record for mail, add a new A record for mail pointing to the given ip.
Furthermore you should make sure the server is acting as relay backup OR isn't acting at all.

I've had some problems, a reseller of mine has about all national company in a certain sector as his customer, but mailing from A to B on the server isn't really possible. As the server checks out the local config (is this domain hosted by me ?) in Exim first.
I resolved it by removing the name of the domain in question from /etc/virtual/domains.

After that Exim just did what it was supposed to do if it had to deliver to the mail server of the customer.

But as long as the webserver isn't processing any mail the first part of the solution is fine .

 

[nobaloney]

mrproducer,

Of course to do any of this you've got to get your host (the folk you've purchased the reseller account from) to allow you to change DNS records.

Then you can do exactly what you've tried to do, but instead of using an IP#, click on MX Record" and create an MX record for the domain name of your client's mailserver (be sure to end the domain name with a "." character). And be sure to uncheck "Use this server to handle my emails".

Then click on "Save".

Icheb, that should allow your server to send email to the same domain's email server on another system without having to remove any entries manually.

Jeff

 

[Icheb]

Thank you

Me and console are really good friends, I usually solve problems I can't instantly see in DA in console...
Let's fix this, once and for all .

 

[mrproducer]

MX Record Change for Exchange Server

Hi Guys,
sorry for the late reply in this, but my client has finally contacted me ready to perform this change.

I'm lost on the exact procudure to follow, since I"m not sure what you thought I was going to do in the first place.

My client has an IP# for their exchange server and wish for me to modify my mx records to send all mail to them, instead of through their hosting plan.

OF course, I have send mail scripts installed on their website, so I wish to be sure that they recieve the email generated from these contact forms.

I understand that I am to delete the original MX record. I can see how to do this from the email/mxrecords in DA.

Then,
Create an A record with their exchange server name, pointing to the IP number they provided. but I don't have a exchange server name? Do I just make one up?

Then,
Create an mx record that points to the A record.
I see where I create the new mx record "email/mxrecords", what do I put in the yellow field?

Do I need to delete or modify any of the other A records, such as "POP" or "Mail"?

Thanks for your help. I see others are having similiar problems but I couldn't see the procedure.

 

[nobaloney]

Re: MX Record Change for Exchange Server

I'm lost on the exact procudure to follow, since I"m not sure what you thought I was going to do in the first place.

There was a street comedian in San Francisco in the late 70s who spoke much like you wrote above. He also said: "I'm sorry but I got my tongue caught in my eye-tooth and I can't see what I'm saying ".

I understand that I am to delete the original MX record. I can see how to do this from the email/mxrecords in DA.

Then,
Create an A record with their exchange server name, pointing to the IP number they provided.[/quote]
If it were me, I'd change smtp.example.com, mail.example.com, and pop.example.com to their IP#, and then log into your system under the client user account and go to this URL:

https://da1.namelessnet.net:2222/CMD_DNS_MX?domain=domain.com

Delete the mx record there, and add the new one pointing to smtp.example.com.

Two notes: if you don't allow the customer to change his DNS you'll have to allow this, at least temporarily, so you can do the above. If you're only a reseller and the cleint can't change his own DNS, then you'll have to ask your hosting company to turn it on for you.

And...

of course you shouldn't actually do it for example.com, but rather for your client's domain name .

but I don't have a exchange server name? Do I just make one up?

Then,
Create an mx record that points to the A record.
I see where I create the new mx record "email/mxrecords", what do I put in the yellow field?

Do I need to delete or modify any of the other A records, such as "POP" or "Mail"?

Just see what I wrote above.

Thanks for your help. I see others are having similiar problems but I couldn't see the procedure.

If you do what I see then after a day or so (during which old information will still be cached on the 'net) everything will work as you and your client expect. Of course they may need to log into your webmail system to make sure they read any mail that got misrouted between the time you changed the DNS and the time it "took" all over the 'net.

And of course your client will have to figure out how to get their users to look at their Exchange server for email rather than your server, but hopefully that'll be their problem .

Jeff