Post your static IP

[omegadraconis]

My clients are running pretty much 24/7 and can be reached at:
wan1.adminitator.com or wan2.adminitator.com

The IP addresses should be pretty static from now on and both address should be running 24/7.

[nethoncho]

My client is running pretty much 24/7 and can be reached at either 65.60.177.164(adminitator.com) or 75.118.213.133(wan2.adminitator.com)

Both failed to accept a connection. Maybe a firewall rule?

[rodin]

200.35.150.50

[HarryS]

I just sent 0.01 to 14 different IPs, I tried all of them, but some were not responding. Also I just noticed that the send coin dialog only works with IP address, not host names.

:~$ ./bitcoind getinfo
"balance" : 0.000000000000000

Waaah! My client was on, so it should have worked. Hostname sending should work or be added, I shall suggest that up.

Post your IP and I will try again...

It changes too often for me to post it here. The hostname should work, if not, it should be added.

[adamjkok]

I don't have a static IP, but I have a dedicated domain that points to it.

ewt5.tk

[nethoncho]

I don't have a static IP, but I have a dedicated domain that points to it.

ewt5.tk

Just sent 0.01

[adamjkok]

I don't have a static IP, but I have a dedicated domain that points to it.

ewt5.tk

Just sent 0.01

Hey, thanks! I got it!

[TG12]

Dynamic DNS. sawyer12.homeip.net. Not running 24/7 however.

[Brandon]

Original IP/address posted has since gone down. From now on use 16bit.doesntexist.com - This one is constantly updated to my IP as it changes and is up 24/7.

[mizerydearia]

host: nullvoid.org

Also, http://www.bitcoin.org/wiki/doku.php?id=74638_nodes

[torservers]

I set up bitcoind on bitcoin.torservers.net now. Hopefully up 24/7 Feel free to test, I'm not so sure, it went too smoothly

[Gatsu]

Hello im gatsu im new here im trying to understand this program and my IP is 90.229.148.152

[mizerydearia]

It is no longer necessary to post ip addresses at this time.  The reason there was an abundance of hype regarding everyone to quickly publish their addresses was due to a severe vulnerability in a previous version of Bitcoin and to alert everyone to quickly reorganize using a new version of Bitcoin client that was patched to fix/prevent the vulnerability.

http://bitcointalk.org/index.php?topic=822.0
http://bitcointalk.org/index.php?topic=823.0
http://bitcointalk.org/index.php?topic=827.0
http://bitcointalk.org/index.php?topic=828.0
http://bitcointalk.org/index.php?topic=837.0

[lfm]

It is no longer necessary to post ip addresses at this time.  The reason there was an abundance of hype regarding everyone to quickly publish their addresses was due to a severe vulnerability in a previous version of Bitcoin and to alert everyone to quickly reorganize using a new version of Bitcoin client that was patched to fix/prevent the vulnerability.

http://bitcointalk.org/index.php?topic=822.0
http://bitcointalk.org/index.php?topic=823.0
http://bitcointalk.org/index.php?topic=827.0
http://bitcointalk.org/index.php?topic=828.0
http://bitcointalk.org/index.php?topic=837.0

Well if you look at the start of THIS thread you will see a different reason for THIS thread.

[mizerydearia]

You're right.  :3  *hides*

[LZ]

lzsaver.dlinkddns.com

I hope that next Bitcoin version will accept DNS addresses.

[Dybbuk]

New Tor bitcoind service: j43z65b6r2usg3vk.onion

However, somebody brought up a good point on the IRC channel: since Bitcoin uses Socks4A, do .onion addresses even work, or does the DNS lookup fail and no connection to any Tor-ified .onion addresses even get attempted?

Anybody know?

[ech]

New Tor bitcoind service: j43z65b6r2usg3vk.onion
However, somebody brought up a good point on the IRC channel: since Bitcoin uses Socks4A, do .onion addresses even work, or does the DNS lookup fail and no connection to any Tor-ified .onion addresses even get attempted?
Anybody know?

That's true, but theymos also mentioned that you can mapaddress the .onion addresses to an IP.
On that note, I would like to add my own hidden service address to the list: vso3r6cmjoomhhgg.onion

So this is what your torrc should include:
mapaddress 10.10.10.1 aaiuestmhzt6pjsl.onion
mapaddress 10.10.10.2 ijzt2eeizty3p5xe.onion
mapaddress 10.10.10.3 vso3r6cmjoomhhgg.onion
mapaddress 10.10.10.4 j43z65b6r2usg3vk.onion

and in your ~/.bitcoin/bitcoin.conf:
addnode=10.10.10.1
addnode=10.10.10.2
addnode=10.10.10.3
addnode=10.10.10.4

Hopefully they will add socks 4a/5 + dns support soon.

[The Madhatter]

Here are some that I've collected from various forums that are not on your list.

pvuif6nonbhj3o3r.onion
c5qvugpewwyyy5oz.onion
xqzfakpeuvrobvpj.onion

[mizerydearia]

Here are some that I've collected from various forums that are not on your list.

pvuif6nonbhj3o3r.onion
c5qvugpewwyyy5oz.onion
xqzfakpeuvrobvpj.onion

Maybe add to http://www.bitcoin.org/wiki/doku.php?id=74638_nodes or combine that wiki page with teh additions in forming a new wiki page with a more appropriate name?