4 ms·

I wanted to like bitbucket for the private free repos that they offer. But I ran into an domain verification issue when I tried to update/push a repository as

I wanted to like bitbucket for the private free repos that they offer. But I ran into an domain verification issue when I tried to update/push a repository as listed in their docs. So I did a bit of dig and found this: ~ » dig bitbucket.org <snipped> ;; ANSWER SECTION: bitbucket.org. 36584 IN A 207.223.240.182 bitbucket.org. 36584 IN A 207.223.240.181 OK. So two IPs there. I visit those IPs and they show what seems like some usernames that have zero activity and seem suspicious (to my paranoid brain atleast). Last I remember, which was about a couple of months ago, 182 was fetching the proper bitbucket.org pages. But even that seems to show up some username created in Dec 2012(!)

pbnjay 14y ago
This doesn't make any sense. You had an issue verifying your own domain... I don't understand what that has to do with bitbucket's DNS. ... so then you loaded the site directly from the IP? And then you were surprised that it gave you a random virtual host?
- davyjones 14y ago
  > You had an issue verifying your own domain. No. There was an issue verifying bitbucket.org. A git push could never be done because of some cert issue. That is when I dug a little further to look at the IPs directly. FWIW, the cert issue seems to be resolved now. I just checked with two VMs.
0x0 14y ago
That's probably just some web route mishap that didn't expect to be accessed without a hostname and probably maps to two (unfortunate) user IDs that match the IP addresses, or something. Try reporting it to @bitbucket on twitter?
levesque 14y ago
So what are the implications here?
- kyrra 14y ago
  as far as I can tell, none what-so-ever. Go ahead and visit the sites yourself. [1] http://207.223.240.181/ http://207.223.240.181/ [2] http://207.223.240.182/ http://207.223.240.182/ For whatever reason, going to those IP addresses, take you to 2 these pages: [3] http://bitbucket.org/dqvsra http://bitbucket.org/dqvsra [4] http://bitbucket.org/antonrylov http://bitbucket.org/antonrylov There isn't anything really of interest on either of the pages. It's not like you're seeing their logged in page. This is just some kind of routing issue with Bitbuckets server configuration.

pbnjay 14y ago

This doesn't make any sense. You had an issue verifying your own domain... I don't understand what that has to do with bitbucket's DNS. ... so then you loaded the site directly from the IP? And then you were surprised that it gave you a random virtual host?

davyjones 14y ago
> You had an issue verifying your own domain. No. There was an issue verifying bitbucket.org. A git push could never be done because of some cert issue. That is when I dug a little further to look at the IPs directly. FWIW, the cert issue seems to be resolved now. I just checked with two VMs.

0x0 14y ago

That's probably just some web route mishap that didn't expect to be accessed without a hostname and probably maps to two (unfortunate) user IDs that match the IP addresses, or something. Try reporting it to @bitbucket on twitter?

levesque 14y ago

So what are the implications here?

kyrra 14y ago
as far as I can tell, none what-so-ever. Go ahead and visit the sites yourself. [1] http://207.223.240.181/ http://207.223.240.181/ [2] http://207.223.240.182/ http://207.223.240.182/ For whatever reason, going to those IP addresses, take you to 2 these pages: [3] http://bitbucket.org/dqvsra http://bitbucket.org/dqvsra [4] http://bitbucket.org/antonrylov http://bitbucket.org/antonrylov There isn't anything really of interest on either of the pages. It's not like you're seeing their logged in page. This is just some kind of routing issue with Bitbuckets server configuration.