Skip to content

Kévin Dunglas

Founder of Les-Tilleuls.coop (worker-owned cooperative). Creator of API Platform, Mercure.rocks, Vulcain.rocks and of some Symfony components.

Menu
  • Talks
  • Resume
  • Sponsor me
  • Contact
Menu

Feedburner: Switching to Google account with MyBrand enabled

Posted on January 31, 2009February 1, 2009 by Kévin Dunglas

Since I’ve migrated my FeedBurner account to Google I encounter a lot of problems, especially with the MyBrand service. MyBrand is a service allowing to use custom domain names with FeedBurner. Instead of something like http://feeds.feedburner.com/lapin-blanc, your feed address become http://feeds.dunglas.fr/lapin-blanc. I’ve already explained why it’s better !

My subdomain for feeds was rss.dunglas.fr. There is no way to get this subdomain working since I’ve switched to Google accounts. I’ve followed the Tim Heuer’s tutorial but the message The domain “rss.dunglas.fr” you specified is already in use. is still displayed when I try to recreate my main custom URL in the MyBrand settings page. I’ve just managed to get my “backup” domain called feeds.dunglas.fr working.

So I’ve created this quick-and-dirty hack:

  1. Set a working MyBrand domain. For me: feeds.dunglas.fr.
  2. Point the DNS entry of your primary feeds domain on your web server. For me me: replace rss 10800 IN CNAME <my-login>.feedproxy.ghs.google.com. by rss 10800 IN CNAME www.
  3. Create a virtual host on your web server to redirect permanently the old addresses to the new one. For me (using Debian GNU/Linux):
    Create a file called /etc/apache2/sites-available/rss.dunglas.fr containing:

    <VirtualHost *>
            ServerName rss.dunglas.fr
    
            RewriteEngine On
            RewriteRule ^(.*) http://feeds.dunglas.fr$1 [L,R=301]
    </VirtualHost>

    Next type in a shell a2ensite rss.dunglas.fr && /etc/init.d/apache2 reload.

  4. Change all occurrences of your old feeds URL to the new in your site to reduce the number of HTTP requests.

Your burned feed must work without losing readers. This a temporary solution, and I think that the only useful long term solution is to go away from FeedBurner…

Related posts:

  1. feedproxy.google.com semble remplacer feeds.feedburner.com
  2. FeedBurner avec votre nom de domaine !
  3. Google change encore de favicon
  4. Google indexe les sites en Flash : un coup d’épée dans l’eau

4 thoughts on “Feedburner: Switching to Google account with MyBrand enabled”

  1. Gonzague says:
    February 1, 2009 at 11:40 pm

    tiens.. j'ai fait pareil 😛

    Reply
  2. Sarah Graham says:
    May 26, 2010 at 9:21 am

    Feedburner is really very useful for syndicating feeds from other websites.””*

    Reply
  3. Lunch Bags ` says:
    October 11, 2010 at 7:09 pm

    feed burner is very useful for blog owners because it is easy to syndicate feeds using feedburner *~;

    Reply
  4. Shirly Strehle says:
    February 11, 2011 at 6:36 pm

    Together with the whole thing which appears to be developing within this particular subject material, your perspectives are somewhat radical. Having said that, I appologize, because I do not subscribe to your entire strategy, all be it radical none the less. It looks to us that your remarks are actually not entirely justified and in fact you are generally your self not fully confident of the point. In any case I did take pleasure in looking at it.

    Reply

Leave a Reply Cancel reply

Follow me on Twitter

My Tweets

Subscribe to this blog

Recent Posts

  • Read the Linux Manual Pages on Mac and BSD, Directly From the Terminal
  • Ne vous lamentez pas, organisez-vous !
  • FrankenPHP: The Modern Php App Server, written in Go
  • API Platform 3 Is Released!
  • Mercure 0.14: Major Performance Improvement and New Features

Top Posts & Pages

  • Securely Access Private Git Repositories and Composer Packages in Docker Builds
  • JSON Columns and Doctrine DBAL 3 Upgrade
  • Preventing CORS Preflight Requests Using Content Negotiation
  • FrankenPHP: The Modern Php App Server, written in Go
  • Symfony's New Native Docker Support (Symfony World)
  • Goroutines, threads, and thread IDs
  • Generate a Symfony password hash from the command line
  • API Platform 3 Is Released!
  • Connection to a MS SQL Server from Symfony / Doctrine on Mac or Linux
  • Vulcain: HTTP/2 Server Push
 and the rise of client-driven REST APIs

Persistence in PHP with the Doctrine ORM

Persistence in PHP with the Doctrine ORM

Tags

Apache API API Platform Buzz Caddy Docker Doctrine Go Google GraphQL HTTP/2 Hydra hypermedia Hébergement Javascript JSON-LD Kubernetes La Coopérative des Tilleuls Les-Tilleuls.coop Lille Linux Mac Mercure Mercure.rocks Messagerie Instantanée MySQL PHP Punk Rock Python React REST Rock'n'Roll RSS Schema.org Security SEO SEO Symfony Symfony Live Sécurité Ubuntu Web 2.0 Wordpress XHTML XML

Archives

Categories

  • DevOps (25)
  • Mercure (4)
  • Opinions (91)
  • Programming (185)
    • Android (5)
    • Go (13)
    • JavaScript (43)
    • PHP (143)
      • API Platform (65)
      • Symfony (89)
    • Python (14)
      • Django (5)
  • Security (15)
  • SEO (24)
  • Talks (39)
  • Ubuntu (68)
  • Wordpress (6)

Social

  • Mastodon
  • Twitter
  • LinkedIn
  • YouTube
  • GitHub

Links

  • API Platform
  • Les-Tilleuls.coop
  • Mercure.rocks
  • Vulcain.rocks
© 2023 Kévin Dunglas | Powered by Minimalist Blog WordPress Theme