samba - Jun 2015 - Internal DNS CNAME To Amazon Web Services Problem

On Fri, Jun 26, 2015 at 10:08:18AM +0100, Paul Littlefield
wrote:
> Damn, anyone know what can I do to get my situation solved?
The issue is not hard to fix, maybe a day or two. You might
contact someone from https://www.samba.org/samba/support/
for paid support to get this done.

With best regards,

Volker Lendecke

-- 
SerNet GmbH, Bahnhofsallee 1b, 37081 G?ttingen
phone: +49-551-370000-0, fax: +49-551-370000-9
AG G?ttingen, HRB 2816, GF: Dr. Johannes Loxen
http://www.sernet.de, mailto:kontakt at sernet.de

On 26/06/15 11:18, Volker Lendecke wrote:
> The issue is not hard to fix, maybe a day or two. You might
> contact someone from https://www.samba.org/samba/support/
> for paid support to get this done.
Hello Volker

Thanks for the encouragement.

I shall contact a few names on this page:-
https://www.samba.org/samba/support/uk.html

Fingers crossed it's not going to cost a fortune.

Paul

https://lists.samba.org/archive/samba/2015-June/192512.html

Hello Samba Mailing List

Well, the companies I contacted about this problem said that they could not help
because it was an actual Samba code issue, and not a configuration issue.

I have "got around it" for now by changing the internal CNAME to an A
record which points to another in-house server running Apache and then creating
a quick internal web site for the www.domain.com in question which then serves
an .htaccess file with the following:-

Redirect 301 / http://path.to.amazon.s3.site.com

e.g.     PC > DC > Apache Server > .htaccess > Amazon

Not great, but it'll do for now, so the boss can see what the rest of the
world sees at the Amazon Web Services.

I don't really want to bother with all the hassle of changing to BIND for
this tiny thing, so I am hoping the Samba developers can either fix the
recursive CNAME bug or put back the smb.conf option...

...fingers and toes crossed!

Thanks and regards,

Paul