1. Bitbucket
  2. Public Issue Tracker
  3. master
  4. Issues

Issues

Issue #3071 resolved

Custom domain now resolving

Steve Ivy
created an issue

I setup a CNAME on wallrazer.com that points to bitbucket.org. BB says that the domain does not resolve, though I can ping the hostname without an issue:

{{{ titan[~]> ping code.wallrazer.com PING bitbucket.org (207.223.240.181): 56 data bytes 64 bytes from 207.223.240.181: icmp_seq=0 ttl=53 time=65.572 ms 64 bytes from 207.223.240.181: icmp_seq=1 ttl=53 time=69.725 ms 64 bytes from 207.223.240.181: icmp_seq=2 ttl=53 time=67.172 ms 64 bytes from 207.223.240.181: icmp_seq=3 ttl=53 time=66.595 ms ^C --- bitbucket.org ping statistics --- 4 packets transmitted, 4 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 65.572/67.266/69.725/1.531 ms

}}}

Is there something I'm missing?

Thanks

--Steve

Comments (9)

  1. Dylan Etkin

    Hi Steve,

    You need to configure you domain to point to us.

    You can read the full details here, http://confluence.atlassian.com/display/BITBUCKET/Using+your+Own+Bitbucket+Domain+Name

    The relevant bit is:

    To set up a CNAME, you must have access to the DNS of your domain name. The actual steps to do this will vary depending on the DNS provider you use. In your domain control panel or configuration, set up the domain name you want as a CNAME pointing to bitbucket.org. For example, you might set up hg.example.com as a CNAME to bitbucket.org.

    I hope this helps,

    Dylan

  2. Charles McLaughlin

    Hi Steve,

    We looked into this a little more closely and I think I know what happened. You probably tried to add your cname in Bitbucket before you registered the DNS entry. Then we started caching the negative lookup. I just cleared our dns cache, so if that's what happened you should be all set.

    [root@bitbucket09 ~]# host code.wallrazer.com
    Host code.wallrazer.com not found: 3(NXDOMAIN)
    
    [root@bitbucket09 ~]# svc -t /service/dnscache/
    
    [root@bitbucket09 ~]# host code.wallrazer.com
    code.wallrazer.com is an alias for bitbucket.org.
    bitbucket.org has address 207.223.240.181
    bitbucket.org has address 207.223.240.182
    bitbucket.org mail is handled by 1 aspmx.l.google.com.
    bitbucket.org mail is handled by 5 alt1.aspmx.l.google.com.
    bitbucket.org mail is handled by 5 alt2.aspmx.l.google.com.
    bitbucket.org mail is handled by 10 aspmx2.googlemail.com.
    bitbucket.org mail is handled by 10 aspmx3.googlemail.com.
    

    Please let us know if you need any futher assistance.

    Regards,

    Charles

  3. Mats Larsson

    I have also the same problem. I would appreciate if someone could resolve it for me. Thanks! {{{ Oracle:Documents matslarsson$ ping www.labast.com PING bitbucket.org (207.223.240.182): 56 data bytes 64 bytes from 207.223.240.182: icmp_seq=0 ttl=50 time=247.664 ms 64 bytes from 207.223.240.182: icmp_seq=1 ttl=50 time=136.088 ms 64 bytes from 207.223.240.182: icmp_seq=2 ttl=50 time=136.894 ms 64 bytes from 207.223.240.182: icmp_seq=3 ttl=50 time=135.753 ms 64 bytes from 207.223.240.182: icmp_seq=4 ttl=50 time=236.623 ms 64 bytes from 207.223.240.182: icmp_seq=5 ttl=50 time=136.559 ms 64 bytes from 207.223.240.182: icmp_seq=6 ttl=50 time=135.832 ms 64 bytes from 207.223.240.182: icmp_seq=7 ttl=50 time=137.050 ms 64 bytes from 207.223.240.182: icmp_seq=8 ttl=50 time=134.321 ms 64 bytes from 207.223.240.182: icmp_seq=9 ttl=50 time=137.431 ms 64 bytes from 207.223.240.182: icmp_seq=10 ttl=50 time=138.114 ms ^C --- bitbucket.org ping statistics --- 11 packets transmitted, 11 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 134.321/155.666/247.664/40.845 ms }}}

  4. Quentin Schuler

    Hello, I did the same mistake and now the negative DNS lookup seems to be cached. Can you help me ?

    ping bitbucket.neosyne.com
    
    Envoi d'une requête 'ping' sur bitbucket.org [207.223.240.182] avec 32 octets de données :
    Réponse de 207.223.240.182 : octets=32 temps=131 ms TTL=44
    Réponse de 207.223.240.182 : octets=32 temps=130 ms TTL=44
    Réponse de 207.223.240.182 : octets=32 temps=130 ms TTL=44
    Réponse de 207.223.240.182 : octets=32 temps=130 ms TTL=44
    
    Statistiques Ping pour 207.223.240.182:
        Paquets : envoyés = 4, reçus = 4, perdus = 0 (perte 0%),
    Durée approximative des boucles en millisecondes :
        Minimum = 130ms, Maximum = 131ms, Moyenne = 130ms
    

    Thanks guys.

  5. Ryan Watts

    Hi I am having this same issue. I set the repo.wattsapplications.com in bitbucket before creating it. Could you all reset the cache so that it pulls through.

    Thanks.

  6. Log in to comment