Can you try a nslookup with a global DNS server like 4.2.2.1, 4.2.2.2, or 8.8.8.8 (Google's Public DNS)??
The globals work, but not the AT&T uVerse DNS server.
Makes sense, that's what I'm using.
I'm also East coast USA
Topic: [NEW POOL & MINER] - BitcoinPool.com - Jump In! ~NO FEES~ :) - page 12. (Read 101960 times)
The globals work, but not the AT&T uVerse DNS server.
Makes sense, that's what I'm using.
I'm also East coast USA
Can you try a nslookup with a global DNS server like 4.2.2.1, 4.2.2.2, or 8.8.8.8 (Google's Public DNS)??
The globals work, but not the AT&T uVerse DNS server.
DNS: 68.94.156.1
C:\>nslookup bitcoinpool.com 68.94.156.1
Server: dnsr1.sbcglobal.net
Address: 68.94.156.1
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to dnsr1.sbcglobal.net timed-out
I was having the same problem with the exact same ATT nameserver earlier today. Switched to Google nameservers and all is fine. Something funky with ATT/SBC today.
Are you by any chance in California?
DNS: 68.94.156.1
C:\>nslookup bitcoinpool.com 68.94.156.1
Server: dnsr1.sbcglobal.net
Address: 68.94.156.1
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to dnsr1.sbcglobal.net timed-out
C:\>nslookup bitcoinpool.com 68.94.156.1
Server: dnsr1.sbcglobal.net
Address: 68.94.156.1
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to dnsr1.sbcglobal.net timed-out
Can you try a nslookup with a global DNS server like 4.2.2.1, 4.2.2.2, or 8.8.8.8 (Google's Public DNS)??
bitcoinpool.com doesn't return an address from DNS.
Just verified that my IP is correct with my DNS registrar. From my PoV with a server in Chicago using two different DNS servers.
root@www [~]# nslookup bitcoinpool.com 4.2.2.2
Server: 4.2.2.2
Address: 4.2.2.2#53
Non-authoritative answer:
Name: bitcoinpool.com
Address: 173.50.236.43
root@www [~]# nslookup bitcoinpool.com 8.8.8.8
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
Name: bitcoinpool.com
Address: 173.50.236.43
What is your DNS server's IP address? I'd like to be able to see that from your PoV.
If any user's are having DNS problems, please try using the IP address directly.
Thank you.
DNS: 68.94.156.1
C:\>nslookup bitcoinpool.com 68.94.156.1
Server: dnsr1.sbcglobal.net
Address: 68.94.156.1
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to dnsr1.sbcglobal.net timed-out
bitcoinpool.com doesn't return an address from DNS.
Just verified that my IP is correct with my DNS registrar. From my PoV with a server in Chicago using two different DNS servers.
root@www [~]# nslookup bitcoinpool.com 4.2.2.2
Server: 4.2.2.2
Address: 4.2.2.2#53
Non-authoritative answer:
Name: bitcoinpool.com
Address: 173.50.236.43
root@www [~]# nslookup bitcoinpool.com 8.8.8.8
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
Name: bitcoinpool.com
Address: 173.50.236.43
What is your DNS server's IP address? I'd like to be able to see that from your PoV.
If any user's are having DNS problems, please try using the IP address directly.
Thank you.
SH@#$%%#%t I got the idle message and lost 4 hours of mining and now says problems communicating with Bitcoin RPC WTF
and cant connect to your site
I can mine with the deepbit pool just fine
and cant connect to your site
I can mine with the deepbit pool just fine
We're still crunching away with 96 active users. You might want to double check your setup.
I'm having the same problem when I just tried with the same settings I have been running for the past few days.
Rebooted and still problems communicating with Bitcoin RPC for some reason.
I have 2 miners actively running from 2 different geographic locations just to make sure that our server is reachable. At this point in time, both of them are able to pull a getwork, solve it, then send it back. Can you ping bitcoinpool.com?? Can you reach the website?
bitcoinpool.com doesn't return an address from DNS.
SH@#$%%#%t I got the idle message and lost 4 hours of mining and now says problems communicating with Bitcoin RPC WTF
and cant connect to your site
I can mine with the deepbit pool just fine
and cant connect to your site
I can mine with the deepbit pool just fine
We're still crunching away with 96 active users. You might want to double check your setup.
I'm having the same problem when I just tried with the same settings I have been running for the past few days.
Rebooted and still problems communicating with Bitcoin RPC for some reason.
I have 2 miners actively running from 2 different geographic locations just to make sure that our server is reachable. At this point in time, both of them are able to pull a getwork, solve it, then send it back. Can you ping bitcoinpool.com?? Can you reach the website?
SH@#$%%#%t I got the idle message and lost 4 hours of mining and now says problems communicating with Bitcoin RPC WTF
and cant connect to your site
I can mine with the deepbit pool just fine
and cant connect to your site
I can mine with the deepbit pool just fine
We're still crunching away with 96 active users. You might want to double check your setup.
I'm having the same problem when I just tried with the same settings I have been running for the past few days.
Rebooted and still problems communicating with Bitcoin RPC for some reason.
Quote
Ours is correct. Check every link on our blocks page if you want, they're all correct.
114974 OverlordQ 03-25-2011 10:55:45 -- 02h 06m 25s Confirmed
http://bitcoinpool.com/block.php?block=114974 ->
http://blockexplorer.com/b/114974 ->
http://blockexplorer.com/block/000000000000da97d2ba7ddb5d3c9b48980b92bb12f3926bb0382615853fbaca
containing generation http://blockexplorer.com/tx/0db08f91bef092708054d340e698986cdac83dbeaaee91f8fe7b94b6b6dcd285
which was sent to SLUSHS pool main addr 1PJnjo4n2Rt5jWTUrCRr4inK2XmFPXqFC7 in tx http://blockexplorer.com/tx/67e8af21b9759571a95b2f73926ccdb59d5fd625acddeb20533c52429efd243e
FML. You're correct. We have been tracking the wrong block. We forgot to add 1 to the block number when it's found. Current blocks in the network != the current block being worked on.
SHIT SHIT SHIT
Will fix this weekend.
OK slush, enjoy this. I'M SORRY
I don't have this problem, Tycho doesn't either.
Actually i'm not displaying block numbers at all to prevent any mismatch :) Quote
Ours is correct. Check every link on our blocks page if you want, they're all correct.
114974 OverlordQ 03-25-2011 10:55:45 -- 02h 06m 25s Confirmed
http://bitcoinpool.com/block.php?block=114974 ->
http://blockexplorer.com/b/114974 ->
http://blockexplorer.com/block/000000000000da97d2ba7ddb5d3c9b48980b92bb12f3926bb0382615853fbaca
containing generation http://blockexplorer.com/tx/0db08f91bef092708054d340e698986cdac83dbeaaee91f8fe7b94b6b6dcd285
which was sent to SLUSHS pool main addr 1PJnjo4n2Rt5jWTUrCRr4inK2XmFPXqFC7 in tx http://blockexplorer.com/tx/67e8af21b9759571a95b2f73926ccdb59d5fd625acddeb20533c52429efd243e
See, your site does have a bug in it's stats page. This has nothing to do with bitcoind.
hehe, looks like you forgot to respond to my previous post
. Don't catch me on stupid problem with mistaken number in stats which I explained.Quote
I don't have this problem
Apparently not.
See, slush's stats page has problem. Look at block 115147. It's listed two times. The bottom link for 115147 takes you to that block in block explorer. The link right above it for the same block, 115147, takes you to blockexplorer where you see an error "No such block". Slush's stats are wrong and have bugs in it.
Ours is correct. Check every link on our blocks page if you want, they're all correct.
We can easily check it.Ours is correct. Check every link on our blocks page if you want, they're all correct.
If you are sure that block 114974 is yours then 1LNMd6utxZQHGkEiL2m2ZSnVqkSNB3M5un is your address because 50 BTC generated in this block were sent to it.
http://blockexplorer.com/block/000000000000da97d2ba7ddb5d3c9b48980b92bb12f3926bb0382615853fbaca
I am correct ?
Then you can send, for example, 100 BTC or at least 60 BTC to this address from your wallet or any pool's wallets. If this is your address, your balance won't change and we all will see that you did it. If it's NOT your address, then this will be your fine for making false statements :)
Is it possible?
Yes, this is the bug which I'm talking about. It's related to latency on bitcoin network. But the link to blockexplorer is correct, because the link uses block hash submitted to the pool. I explained this many times, fix does not a priority for me, it's just cosmetic.
See, your site does have a bug in it's stats page. This has nothing to do with bitcoind. I don't have this problem, Tycho doesn't either. Maybe it's cause you use more than one bitcoind, who knows?? Apparently you don't know either.
Is it possible?
Yes, this is the bug which I'm talking about. It's related to latency on bitcoin network. But the link to blockexplorer is correct, because the link uses block hash submitted to the pool. I explained this many times, fix does not a priority for me, it's just cosmetic.
Is it possible?
Had to be clear about that.
And Slush says we're the ones that are wrong?! Really? Our site doesn't do the same types double listing his does.
So who's site is wrong and buggy here? Not ours and Not Tycho's (deepbit).
Is it possible?
Getting RPC error & also can't able to open website bitcoinpool.com.
I'm looking into this now. Should have an update soon.
I think slush pool shows wrong block in the stats page.
Current Bitcoin block#: 115201, but bitcoin client says 115201.
How can one mine a block which is already solved & accepted & showed by client?
Current Bitcoin block#: 115201, but bitcoin client says 115201.
How can one mine a block which is already solved & accepted & showed by client?
See, slush's stats page has problem. Look at block 115147. It's listed two times. The bottom link for 115147 takes you to that block in block explorer. The link right above it for the same block, 115147, takes you to blockexplorer where you see an error "No such block". Slush's stats are wrong sometimes and have bugs in it.
Ours is correct. Check every link on our blocks page if you want, they're all correct.
Pwned.
Glass house, meet stone
Glass house, meet stone
Jump to: