Help with MX Record

J

jechilt

Verified User
Joined
Jun 21, 2004
Messages
212
Greetings,

I am needing to add a MX record for another server for a few domains.

When I log in using an admin level account and go into DNS Administration, I will click on a domain name (sudo name is MX.COM), I go to the domain account info.

In the window, there is a place to add an MX record but there is no listing for the default MX record (mail.MX.com.).

I need to be able to change the primary mail.mx.com record from a value of 10 to 20 so I can add the new mx record and set it to 10.

I did go into the user account and add a MX record and set it to 10. After all the updates are done, the only thing that shows up in a NSLOOKUP is mail.mx.com. set to 10.

Where can I change the default mail.mx.com setting value to 20?
Is there a problem that I am not seeing this default value in the control panel as the admin or user account?

Please help...
 
I'm no expert on this, but as far as I know it isn't possible to change the priority value of a mx record after it's been added. You would first have to delete the existing mx record and then add it again using the value you want.
 
Also I noticed that the serial number in the SOA record of the dns zone file for mx.com is in a non-standard format.
I'm just guessing here, but if this would cause DA not to increase de serial number because it doesn't understand the existing format than that could explain why any changes you make to the zone file do not propagate.
Of course if DA simply overwrites any existing serial number than it wouldn't cause any problems. On the other hand, in order for DA to increase the serial number it would first have to be able to interpret the existing serial. I'm not sure how DA would behave if it encounters a non-standard serial.
You could edit the .db file for the account in /var/named by hand if you know the syntax of a dns zone file...
 
Aspegic said:
Also I noticed that the serial number in the SOA record of the dns zone file for mx.com is in a non-standard format.
Click to expand...
On our RHL, RHEL, and CentOS DA-powered servers the serial number is in the format:

2006010600

which is the correct format as far as I know.

What have you seen?

Jeff
 
On our RHL, RHEL, and CentOS DA-powered servers the serial number is in the format:

2006010600

which is the correct format as far as I know.

What have you seen?
Click to expand...

My server (FC2) also uses that same format (yyyymmddnn),
but the serial of mx.com is: 1109780267
I've never seen a number like that. Not that it's illegal, any number is valid. It's just that I didn't know for sure what DA would do if it encounters a serial it doesn't understand.
 
Last edited:
I'm not sure what DA would do.

But you can change it yourself, as long as the number you put in would be higher than the number that's in there now.

So I'd simply shell in and change the zone file at /var/named/mx.com.db to today's date with "01" appended afterwards; for example 2005011501.

Then restart the NAMED daemon.

That should work.

Since the serial number is only used for keeping slave nameservers up-to-date, if you only use your one server, it really doesn't matter.

Jeff
 
You must log in or register to reply here.
Back
Top