[BlueOnyx:01212] FW: Blueonyx Digest, Vol 5, Issue 12
Stuart Clark (Datacenta)
stuart.clark at datacenta.net
Wed May 13 11:36:33 -05 2009
Hi
>>To clarify: It is my position that CNAMEs can serve a legitimate
>>
>>Ralf Q reminded us earlier of the particular RFC this comes from, so I
>>have looked up the particular section and am pasting it here for
>>convenience sake:
>>5.2.2 Canonicalization: RFC-821 Section 3.1
>> The domain names that a Sender-SMTP sends in MAIL and RCPT
>> commands MUST have been "canonicalized," i.e., they must be
>> fully-qualified principal names or domain literals, not
>> nicknames or domain abbreviations. A canonicalized name either
>> identifies a host directly or is an MX name; it cannot be
>> CNAME.
>>So, to sum up: NEVER EVER use a CNAME in an MX.
Ok, I couldn't agree more. I do not use CNAMES for MX records.
I do understand the RFC with regards to this.
This issue arose from setting up a website account on BO www.site.com.
I then setup an ARECORD of post.site.com pointing to 217.xxx.xxx.xxx and then set the mx to be post.site.com
I had a CNAME setup for the WWW record and this was causing the problem with the aliases, it had nothing to do with the MX records on the DNS server.
Once I changed the CNAME for www.site.com to an ARECORD the aliases were resolving. I believe this may be to do with the virtusertable as this shows the aliases as: info at www.site.com which of course was set as a CNAME.
I normally use CNAMES for websites as when migrating to new platforms it is easier for me to update 1 record to populate all cnames rather than change the DNS for 100+ sites
Regards,
Stuart
--
Stuart Clark
Systems Administrator
---------------------------------------------------------------
Datacenta Hosting Ltd
Gild House, 72 Norwich Avenue West, Bournemouth, Dorset, BH2 6AW.
Tel: 01202 755 377 - Fax: 01202 755 301
www.datacenta.net - A Kimcell Company
---------------------------------------------------------------
Datacenta Hosting Ltd is a company registered in Scotland with registration number: SC208801
Registered address: Crescent House, Carnegie Campus, Dunfermline, Fife, KY11 8GR
VAT Number: 785629182
---------------------------------------------------------------
Charitable donations to Julia's House and Youth Cancer Trust were made in 2008 in lieu of sending Christmas cards.
Think before you print! Save paper - do you really need to print this email?
-----Original Message-----
From: blueonyx-bounces at blueonyx.it [mailto:blueonyx-bounces at blueonyx.it] On Behalf Of blueonyx-request at blueonyx.it
Sent: 13 May 2009 17:00
To: blueonyx at blueonyx.it
Subject: Blueonyx Digest, Vol 5, Issue 12
Send Blueonyx mailing list submissions to
blueonyx at blueonyx.it
To subscribe or unsubscribe via the World Wide Web, visit
http://www.blueonyx.it/mailman/listinfo/blueonyx
or, via email, send a message with subject or body 'help' to
blueonyx-request at blueonyx.it
You can reach the person managing the list at
blueonyx-owner at blueonyx.it
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Blueonyx digest..."
Today's Topics:
1. [BlueOnyx:01207] Where can I put my .sh files without them
being overwritten? (Support)
2. [BlueOnyx:01208] Re: Where can I put my .sh files without
them being overwritten? (Taco Scargo)
3. [BlueOnyx:01209] Re: e-mail alias problem (Rodrigo Ordonez Licona)
4. [BlueOnyx:01210] Re: e-mail alias problem
(Chris Gebhardt - VIRTBIZ Internet)
5. [BlueOnyx:01211] Re: e-mail alias problem (Rodrigo Ordonez Licona)
----------------------------------------------------------------------
Message: 1
Date: Wed, 13 May 2009 02:02:23 +1000
From: "Support" <support at etmpacific.com.au>
Subject: [BlueOnyx:01207] Where can I put my .sh files without them
being overwritten?
To: "'BlueOnyx General Mailing List'" <blueonyx at blueonyx.it>
Message-ID: <004f01c9d31b$0a1229b0$1e367d10$@com.au>
Content-Type: text/plain; charset="us-ascii"
Hello,
I initially put my start.sh in /etc/rc.d/rc.local but the recent update has
recreated rc.local with the result that my code doesn't start.
I am not familiar with Linux, my code is Java so it is a Windows port, so if
you could point me to a file that will not be changed (and any steps
required to make use of that file expect for editing it) I would appreciate
it.
Tony
------------------------------
Message: 2
Date: Tue, 12 May 2009 18:18:42 +0200
From: Taco Scargo <taco at scargo.nl>
Subject: [BlueOnyx:01208] Re: Where can I put my .sh files without
them being overwritten?
To: BlueOnyx General Mailing List <blueonyx at blueonyx.it>
Message-ID: <0B6286A9-9A51-4EA5-AE0B-AA773827FC72 at scargo.nl>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
rc.local should NEVER be overwritten by any update.
The rpm system makes sure that any configuration/scriptfile that got
changed is not updated.
Instead, the updated file is created with a .rpmnew extension
Regards,
Taco
On 12 mei 2009, at 18:02, Support wrote:
> Hello,
>
> I initially put my start.sh in /etc/rc.d/rc.local but the recent
> update has
> recreated rc.local with the result that my code doesn't start.
>
> I am not familiar with Linux, my code is Java so it is a Windows
> port, so if
> you could point me to a file that will not be changed (and any steps
> required to make use of that file expect for editing it) I would
> appreciate
> it.
>
> Tony
>
>
> _______________________________________________
> Blueonyx mailing list
> Blueonyx at blueonyx.it
> http://www.blueonyx.it/mailman/listinfo/blueonyx
>
------------------------------
Message: 3
Date: Tue, 12 May 2009 14:04:38 -0600
From: "Rodrigo Ordonez Licona" <rodrigo at xnet.com.mx>
Subject: [BlueOnyx:01209] Re: e-mail alias problem
To: "'BlueOnyx General Mailing List'" <blueonyx at blueonyx.it>
Message-ID: <200905122004.n4CK4Sl9028579 at ana.xnet.com.mx>
Content-Type: text/plain; charset="us-ascii"
Weird,
I have used cnames in all platforms (RAQ,BQ,BO), To alias Websites hosted
elsewhere (not on BQ or BO) without problems. And helped me get rid of ugly
names Like: cameras.noip.org.
My 2 cents.
Rodrigo O
Xnet
-----Original Message-----
From: blueonyx-bounces at blueonyx.it [mailto:blueonyx-bounces at blueonyx.it] On
Behalf Of Michael Stauber
Sent: Martes, 12 de Mayo de 2009 09:19
To: BlueOnyx General Mailing List
Subject: [BlueOnyx:01206] Re: e-mail alias problem
Hi Stuart,
> I recently reported that I was having problems with the aliases
> resolving on certain sites. I have got to the bottom of the issue and
> thought I would update the list.
>
> We have external DNS servers so this is not setup on the blueonyx
> server.
> If you create DNS for the site using CNames then any aliases will not
> resolve.
> If you create DNS using ARecords the aliases resolve just fine.
>
> It seems that sendmail cannot resolve cnames.
There is one mantra that has been repeated over and over again ever since
the first Cobalt RaQs. It's also true for BlueQuartz and BlueOnyx:
Do NOT use CNAMES. They're evil!
That can't be repeated often enough, because sometimes for some cases on a
specific platform CNAMES may work, but don't on another platform. So people
say "But this worked on my RaQ550 or BlueQuartz and doesn't work here!".
Why?
Because CNAMES are evil and you shouldn't use them. :o)
--
With best regards
Michael Stauber
_______________________________________________
Blueonyx mailing list
Blueonyx at blueonyx.it
http://www.blueonyx.it/mailman/listinfo/blueonyx
------------------------------
Message: 4
Date: Tue, 12 May 2009 15:23:46 -0500
From: Chris Gebhardt - VIRTBIZ Internet <cobaltfacts at virtbiz.com>
Subject: [BlueOnyx:01210] Re: e-mail alias problem
To: BlueOnyx General Mailing List <blueonyx at blueonyx.it>
Message-ID: <4A09DAD2.3050202 at virtbiz.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Rodrigo Ordonez Licona wrote:
> Weird,
>
>
> I have used cnames in all platforms (RAQ,BQ,BO), To alias Websites hosted
> elsewhere (not on BQ or BO) without problems. And helped me get rid of ugly
> names Like: cameras.noip.org.
>
> My 2 cents.
To clarify: It is my position that CNAMEs can serve a legitimate
purpose. However, that purpose is NEVER for a mailserver.
Ralf Q reminded us earlier of the particular RFC this comes from, so I
have looked up the particular section and am pasting it here for
convenience sake:
5.2.2 Canonicalization: RFC-821 Section 3.1
The domain names that a Sender-SMTP sends in MAIL and RCPT
commands MUST have been "canonicalized," i.e., they must be
fully-qualified principal names or domain literals, not
nicknames or domain abbreviations. A canonicalized name either
identifies a host directly or is an MX name; it cannot be
CNAME.
So, to sum up: NEVER EVER use a CNAME in an MX.
--
Chris Gebhardt
VIRTBIZ Internet Services
Access, Web Hosting, Colocation, Dedicated
www.virtbiz.com | toll-free (866) 4 VIRTBIZ
------------------------------
Message: 5
Date: Tue, 12 May 2009 17:10:18 -0600
From: "Rodrigo Ordonez Licona" <rodrigo at xnet.com.mx>
Subject: [BlueOnyx:01211] Re: e-mail alias problem
To: <cobaltfacts at virtbiz.com>, "'BlueOnyx General Mailing List'"
<blueonyx at blueonyx.it>
Message-ID: <200905122310.n4CNA9fn024868 at ana.xnet.com.mx>
Content-Type: text/plain; charset="us-ascii"
-----Original Message-----m e
From: blueonyx-bounces at blueonyx.it [mailto:blueonyx-bounces at blueonyx.it] On
Behalf Of Chris Gebhardt - VIRTBIZ Internet
Sent: Martes, 12 de Mayo de 2009 02:24
To: BlueOnyx General Mailing List
Subject: [BlueOnyx:01210] Re: e-mail alias problem
Rodrigo Ordonez Licona wrote:
> Weird,
>
>
> I have used cnames in all platforms (RAQ,BQ,BO), To alias Websites
> hosted elsewhere (not on BQ or BO) without problems. And helped me get
> rid of ugly names Like: cameras.noip.org.
>
> My 2 cents.
To clarify: It is my position that CNAMEs can serve a legitimate
purpose. However, that purpose is NEVER for a mailserver.
Ralf Q reminded us earlier of the particular RFC this comes from, so I have
looked up the particular section and am pasting it here for convenience
sake:
5.2.2 Canonicalization: RFC-821 Section 3.1
The domain names that a Sender-SMTP sends in MAIL and RCPT
commands MUST have been "canonicalized," i.e., they must be
fully-qualified principal names or domain literals, not
nicknames or domain abbreviations. A canonicalized name either
identifies a host directly or is an MX name; it cannot be
CNAME.
So, to sum up: NEVER EVER use a CNAME in an MX.
=================
Couldn't agree more, Now that will demonstrate that the evil is inside us.
Every single one of us the devil inside.... INXS...
------------------------------
_______________________________________________
Blueonyx mailing list
Blueonyx at blueonyx.it
http://www.blueonyx.it/mailman/listinfo/blueonyx
End of Blueonyx Digest, Vol 5, Issue 12
***************************************
More information about the Blueonyx
mailing list