its because you arent doing it right.. you shoudlnt DNS an internal IP..
most routers have naming built into them. you should use that instead.
Ok I built a BIND DNS server running on Ubuntu 15.04 as the internal put the same DNS entries. Same problem with the S3+, it just refuses to resolve that DNS entry. All other manufacturers I have work with the internal DNS as well as the external providing a private IP. Any other ideas? LOL you come on here.. asking for help.. yet IGNORE all help.... seriously... you just posting to here yourself? why are you going through ALL THE TROUBLE to PUBLICLY DNS YOUR LAN IP.. go into the pc and set the IP as static. then just go into the router.. find the LAN IP you want and name it. then use "computername" as your host. I tried everything you suggested even though I know it would not work. DNS is part of my job for the past 14 years. Put a private DNS server like you said same issue. Named the 192.168.1.133 proxy1 locally like you said same issue. Same things Windows PC and all other resolve proxy and the DNS but not the S3's. And it is not trouble to configure a public DNS server took me all of 10 minutes. What would take a while is reconfiguring over 200 miners if I have to change pools, or change an IP in the pool configs when all you would have to do is change a proxy entry or a dns entry so much easier. Here is a S3 and PC directly connected to my labs Uverse modem, same DNS from the router, same router, same DHCP server from the router. S3 fails. S3: root@antMiner:~# ping proxy1 ping: bad address 'proxy1' PC: C:\>ping proxy1 Pinging proxy1.gateway.pace.com [192.168.1.133] with 32 bytes of data: Reply from 192.168.1.133: bytes=32 time<1ms TTL=64 Reply from 192.168.1.133: bytes=32 time<1ms TTL=64 Reply from 192.168.1.133: bytes=32 time<1ms TTL=64 Reply from 192.168.1.133: bytes=32 time<1ms TTL=64 Ping statistics for 192.168.1.133: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms |
|
|
|
Does the name resolve OK on your usual PC? Maybe a minor mis-spelling of the name?
DNS resolves fine on Windows, Linux, Mac and other brands of miners, but not on Bitmains S3 wether using my private or public DNS serves. Even SSH to the S3's to resolve it fails to resolve in nslookup and ping. |
|
|
|
its because you arent doing it right.. you shoudlnt DNS an internal IP..
most routers have naming built into them. you should use that instead.
Ok I built a BIND DNS server running on Ubuntu 15.04 as the internal put the same DNS entries. Same problem with the S3+, it just refuses to resolve that DNS entry. All other manufacturers I have work with the internal DNS as well as the external providing a private IP. Any other ideas? With a proper DNS it should work fine. I use 8.8.8.8 . But if truly for some reason your network is not resolving it, have you tried using the IP address instead of web address? he is trying to set a public dns to his 192.168.1.X IP.. for some reason so he can use a PC on his network as a pool proxy.. and he says the IP works just fine.. but he doesnt want to use an ip, he wants to use a public url..   It is now a private DNS server same issue. My local DNS server is now on 192.168.1.10. But I knew that would not fix it. DNS an local proxies make configuring 100s of miners a lot easier. |
|
|
|
|
I am looking for a How To that tells you how to unpackage the Bitmain image, change all the settings you wish, and then repackage it.
This is to aid in deployment of miners, So all that you need to do is upload the image and all the settings for you are set.
TIA,
MC
|
|
|
|
|
Sounds interesting, but at the same time fishy. Why must the person be in the US? Sounds like good idea for the US officials to arrest someone for money laundering.
|
|
|
|
And here is finally the board (to be populated for now).
*Saving Space*
Next to its homemade stencil.
*Saving Space*
Very nice!!! Its white!!! Still just a dev board but glad to see how quick you are able to get some boards made. |
|
|
|
|
If no one provides a site soon, I may build a web cluster just to see how quick you can take it down. I am just curious, but if you do not knock it offline I will be disappointed.
|
|
|
|
PM'd
 LOL I wish. Definitely wish I was that good at coding. Just know PI's that will get the info the OP is requesting. |
|
|
|
|
Its actually 2 panels in a cabinet. Using 3 phase power. Why do you ask?
If you want to know manufacturer its Square D.
Edit: Its also not in use, can i plug my miners in for free?
|
|
|
|
I think this is my new favorite coin. I am so anxious to get them shipped out so I can start hearing other opinions, this wait for plastic capsules is killing me. Not sure why they weren't shipped with the coins.
Imagine how anxious all of us are  Yup it is killing me. I need more pics to hold me over in the mean time. lol |
|
|
|
I am interested in opening a farm and purchasing a lot of miners.
Just wondering how my steps would be from here, are there any sites that actually work and send you your miners in time? Any trusted sites?
I wouldn't want my investment to go to scam so just wondering how the situation is nowadays and if there indeed are any trusted sites where you can buy miners from and actually get them in time.
There is not too many options for new equipment. Bitmain and Avalon is about it. For used myself and various others can sell you equipment. How many are you looking for? |
|
|
|
|
Miner Edge is developing high density miners. I think they are at 6+Th per 1U unit.
Still in development but I would not be surprised if they are the highest per unit in this coming year.
|
|
|
|
its because you arent doing it right.. you shoudlnt DNS an internal IP..
most routers have naming built into them. you should use that instead.
Ok I built a BIND DNS server running on Ubuntu 15.04 as the internal put the same DNS entries. Same problem with the S3+, it just refuses to resolve that DNS entry. All other manufacturers I have work with the internal DNS as well as the external providing a private IP. Any other ideas? |
|
|
|
|
I would probably wait at this point to see what Bitmain and Sfards releases in the next couple of months.
|
|
|
|
|
You should list every site you created so people know which ponzi's are still out there and runnning. You are already paid so it won't hurt you.
|
|
|
|
even if you have something on that IP, nobody else in the world will be able to access it.. just you.
That is the exact point. This is an internal proxy only, no one else should have access to it. The problem is the Bitmain S3 refuse to resolve the address. just use the ip. its probably not the s3 fault, its the network dns is windows only. No cause I am configuring over 100 S3's if I use an IP it is very hard to change their config, as with DNS I can change it on the server. I am pretty sure this is a Bitmain issue as the DNS is hosted by GoDaddy and works on all other platforms I tested BTCGarden, Linux, Mac, and Windows. Going to test Bitmine, MAT, and others tonight, but I am assuming they will all work. um, its pretty easy to change their config, just enable the write access to the api and use a program like cryptoglance. sucks you would have to do each one because its not enabled by default, but once it is, you can just upload the new config to them all at once vie api. Modding the config via SSH takes a lot longer then just setting something that should work anyways. I am really surprised no one has run into this before. im still confused as to what you are running into.. so you are using a proxy to mine through, but you can still set it to IP and change the proxy on the host computer just the same. the IP on the host computer shouldn't change, if you set it to static. proxy-a.brokenshop.net resolves to 192.168.1.133 Bitmain S3+ does not resolve this address via Ping or Configuring as a pool If I put the IP address is 192.168.1.133 in the pool config everything works fine. Everywhere else in the world this DNS entry resolve correctly except on these Bitmain devices. Even at my office, behind many corporate firewalls it still resolves. Just not on these Bitmains for some reason. C:\>ping proxy-a.brokenshop.net Pinging proxy-a.brokenshop.net [192.168.1.133] with 32 bytes of data: Request timed out. Request timed out. Ping statistics for 192.168.1.133: Packets: Sent = 2, Received = 0, Lost = 2 (100% loss), Control-C ^C C:\> its because you arent doing it right.. you shoudlnt DNS an internal IP.. most routers have naming built into them. you should use that instead. DNS resolving an internal IP is allowed even hosting on public external servers. Might be a security risk, but it is allowed and does works. DNS just resolves a name to an IP. This is done at major corporation all day long. Only difference is they restrict via ACL the IPs that can resolve to the servers that have the internal IP addresses. There should be nothing that keeps this from working, but it does not on an S3+ I could setup just an internal DNS server as you are referring to, but functional external or internal DNS servers should not matter. Have you done this and know that this will fix the issue? |
|
|
|
even if you have something on that IP, nobody else in the world will be able to access it.. just you.
That is the exact point. This is an internal proxy only, no one else should have access to it. The problem is the Bitmain S3 refuse to resolve the address. just use the ip. its probably not the s3 fault, its the network dns is windows only. No cause I am configuring over 100 S3's if I use an IP it is very hard to change their config, as with DNS I can change it on the server. I am pretty sure this is a Bitmain issue as the DNS is hosted by GoDaddy and works on all other platforms I tested BTCGarden, Linux, Mac, and Windows. Going to test Bitmine, MAT, and others tonight, but I am assuming they will all work. um, its pretty easy to change their config, just enable the write access to the api and use a program like cryptoglance. sucks you would have to do each one because its not enabled by default, but once it is, you can just upload the new config to them all at once vie api. Modding the config via SSH takes a lot longer then just setting something that should work anyways. I am really surprised no one has run into this before. im still confused as to what you are running into.. so you are using a proxy to mine through, but you can still set it to IP and change the proxy on the host computer just the same. the IP on the host computer shouldn't change, if you set it to static. proxy-a.brokenshop.net resolves to 192.168.1.133 Bitmain S3+ does not resolve this address via Ping or Configuring as a pool If I put the IP address is 192.168.1.133 in the pool config everything works fine. Everywhere else in the world this DNS entry resolve correctly except on these Bitmain devices. Even at my office, behind many corporate firewalls it still resolves. Just not on these Bitmains for some reason. C:\>ping proxy-a.brokenshop.net Pinging proxy-a.brokenshop.net [192.168.1.133] with 32 bytes of data: Request timed out. Request timed out. Ping statistics for 192.168.1.133: Packets: Sent = 2, Received = 0, Lost = 2 (100% loss), Control-C ^C C:\> |
|
|
|
even if you have something on that IP, nobody else in the world will be able to access it.. just you.
That is the exact point. This is an internal proxy only, no one else should have access to it. The problem is the Bitmain S3 refuse to resolve the address. just use the ip. its probably not the s3 fault, its the network dns is windows only. No cause I am configuring over 100 S3's if I use an IP it is very hard to change their config, as with DNS I can change it on the server. I am pretty sure this is a Bitmain issue as the DNS is hosted by GoDaddy and works on all other platforms I tested BTCGarden, Linux, Mac, and Windows. Going to test Bitmine, MAT, and others tonight, but I am assuming they will all work. um, its pretty easy to change their config, just enable the write access to the api and use a program like cryptoglance. sucks you would have to do each one because its not enabled by default, but once it is, you can just upload the new config to them all at once vie api. Modding the config via SSH takes a lot longer then just setting something that should work anyways. I am really surprised no one has run into this before. |
|
|
|
even if you have something on that IP, nobody else in the world will be able to access it.. just you.
That is the exact point. This is an internal proxy only, no one else should have access to it. The problem is the Bitmain S3 refuse to resolve the address. just use the ip. its probably not the s3 fault, its the network dns is windows only. No cause I am configuring over 100 S3's if I use an IP it is very hard to change their config, as with DNS I can change it on the server. I am pretty sure this is a Bitmain issue as the DNS is hosted by GoDaddy and works on all other platforms I tested BTCGarden, Linux, Mac, and Windows. Going to test Bitmine, MAT, and others tonight, but I am assuming they will all work. |
|
|
|
|
Show Posts
