RE: [cobalt-users] MX Record Change on RaQ2

[Jeff Lasman <jblists@xxxxxxxxxxxxx>]

At 06:56 PM 3/9/00 -0500, you wrote:

> I appreciate the response, however, I don't believe you answered the
> question.  I stated in my question that I knew I needed to change the MX
> record.  In fact, the subject of this email is "MX Record Change".  Your
> solution states that I must change the MX record.  You answered my question
> by restating it back to me.  No help! :-)

I think I was asleep when I answered that one <wry grin>.

> I'll try to be more specific...
> What file do I need to change?

Now we're getting a bit complicated.

Did you set up DNS originally using the gui interface?  Or manually?

I presume using the gui interface.  Is that correct?

Then shouldn't you continue using the gui interface?  The gui interface 
WILL allow you to change MX servers; why don't you just use it?

Just select the domain, click on the pencil for the MX record, and change 
the server name to host.newdomain.com, where host is the name of the host, 
and newdomain.com is the new domain name.

Then "Update List" and "Save Changes to DNS Server".

If you want to add another MX server to act as a primary server and keep 
the one you've already got set up as a backup, it becomes a bit more complex.

Change the "Delivery Precedence" of the current MX record to "Low", and 
then add a new MX record for the domain, leaving the default "Delivery 
Precedence" of "High".

The "Update List" and "Save Changes to DNS Server".

The steps to take to add another MX server as the secondary and keep the 
current as a primary are similar:  Leave the current MX record alone, and 
add a new one for the domain, setting the "Delivery Precedence" to "Low".

Then "Update List" and "Save Changes to DNS Server".

That'll do it using the RaQ2s web-based gui interface.

I'm loathe to tell you how to do it by hand, because I do NOT recommend 
mixing web-based and hand administration.

Suffice it to say that if you've already set up your DNS by hand, you know 
the name of the file to change.  If you haven't, then the file to change is 
"/etc/named/pri.domainname.com".

But unless you want the gui to overwrite your changes the next time you run 
it, that's only part of a viable solution.  You also need to change the 
"/etc/named/records" file.  I'm beginning to understand how to change that 
file, but I don't understand it completely yet (I've not bothered to learn, 
since for me it's a lot easier to maintain DNS by hand).  So personaly, I 
don't feel comfortable telling you how to change it.  And that's why I 
don't recommend this solution.

As far as teaching you how to administer DNS by hand, that's beyond the 
scope of a list-reply; I'm happy to consult with you, set up a complete 
solution, and give you master files and scripts to help you automate the 
changes, should you decide to administer DNS manually.  Should you go that 
route, you need to never press on "Save Changes to DNS Server", lest you 
over-write all your own work.  You also need to save a complete copy of 
your work somewhere else on your system lest you accidentally press "Save 
Changes to DNS Server".

> Where specifically is the file located on the RaQ2?

Answered above.

> What information in the file needs to be changed?

Simply the name of the nameserver in the MX record in the zone file, for 
which I've given you the name above.

> How do I restart the DNS server after it is changed?

You do have to learn a bit to feel comfortable administering a RaQ as root 
to do this; I'm not so cavalier as to just give you a line to type in.  You 
can do an awful lot of damage to your RaQs setup as root.  In fact, one 
misplaced spacebar press can delete your entire hard disk in less time than 
you can blink an eye.

So instead, I'll just tell you the help you need should be found in "man ndc".

> Really, I'm not trying to be smartass.  I just don't know where to go.  I
> appreciate any wisdom you can provide.

Wisdom is best obtained over days, months, years.  Build a 
server.  Read.  Make mistakes.

There is NO shortcut to linux administration.  And frankly, I hope I don't 
sound like a smartass saying it.

Jeff

--
Jeff Lasman <jblists@xxxxxxxxxxxxx>