 Show Posts
|
|
Pages: [1]
|
$ traceroute claimwith.me
traceroute to claimwith.me (66.85.133.212), 64 hops max, 52 byte packets
1 192.168.2.170 (192.168.2.170) 3.315 ms 1.079 ms 0.911 ms
2 192.168.0.1 (192.168.0.1) 1.193 ms 1.168 ms 1.202 ms
3 178.16.95.1 (178.16.95.1) 2.473 ms 4.185 ms 3.234 ms
4 host225-88-16-178.reedlan.com (178.16.88.225) 3.308 ms 1.912 ms 2.212 ms
5 193.27.243.229 (193.27.243.229) 2.801 ms 3.145 ms 5.813 ms
6 v80.g32-simf-bb.crimea-com.net (195.3.246.17) 10.377 ms 7.133 ms 10.613 ms
7 rnd-nt-b1-ae8-vlan3132.fiord.net (93.191.9.120) 19.671 ms 25.210 ms 19.500 ms
8 frankfurt-anc-b1-xe0-0-2-vlan2044.fiord.net (80.77.167.205) 55.195 ms 51.384 ms 86.487 ms
9 ffm-b1-link.telia.net (62.115.63.109) 98.034 ms 93.559 ms 80.163 ms
10 ffm-bb3-link.telia.net (62.115.141.238) 67.360 ms
ffm-bb4-link.telia.net (62.115.121.8) 63.879 ms
ffm-bb3-link.telia.net (62.115.141.240) 95.436 ms
11 ash-bb3-link.telia.net (62.115.122.58) 162.038 ms
ash-bb4-link.telia.net (80.91.246.64) 188.650 ms
hbg-bb4-link.telia.net (80.91.245.122) 97.286 ms
12 atl-b22-link.telia.net (62.115.125.128) 198.464 ms
ffm-bb3-link.telia.net (62.115.121.2) 155.701 ms
atl-b22-link.telia.net (62.115.125.132) 173.086 ms
13 giglinx-ic-312590-atl-bb1.c.telia.net (80.239.160.182) 162.455 ms
giglinx-ic-312589-atl-bb1.c.telia.net (80.239.160.178) 170.861 ms
hbg-bb1-link.telia.net (62.115.123.89) 115.501 ms
14 64.38.239.24 (64.38.239.24) 224.338 ms
64.38.239.20 (64.38.239.20) 205.180 ms
giglinx-ic-312590-atl-bb1.c.telia.net (80.239.160.182) 156.645 ms
15 108.170.0.21 (108.170.0.21) 227.554 ms 222.089 ms
64.38.239.24 (64.38.239.24) 206.531 ms
16 * * 108.170.0.9 (108.170.0.9) 235.578 ms
17 * * *
18 * * *
19 * * *
$ ping -c3 claimwith.me
PING claimwith.me (66.85.133.212): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
--- claimwith.me ping statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss Router, placed before server is down. In this time, problem not with DNS. |
|
|
|
On Android I use an app called DNS Changer with Open DNS ips predefined by app, It works well on 4G, not that well on wifi
On Wi-Fi you can change DNS server address in standard Wi-Fi settings. |
|
|
|
I use an app "Dns changer" to change my DNS, but same problem in 3g/4g.
Sorry, I can't support you about Android DNS changer apps, because I don't have Android phone  |
|
|
|
Don't work for me with android phone...
If you have a solution...
This solution is 100% working. Can you take a screenshot and put it here? |
|
|
|
You can follow short instruction in my message, to get ClaimWithMe work on your phone, if you catch an error. OK, I done that earlier! YOU CAN MAKE IT WORK ON ANDROID AND IOS! For make work claimwith.me on your phone, you must change DNS to 92.43.0.71. On my iphone:  But I don't have android phone. |
|
|
|
so, basically you can double* your investments in a month... looks cool, but the only problem is that we don't know for how long the faucet will exist  *and 'double' is at very least - there are also referral comissions and BTC exchange rate, of course Yeah, referrals rules! PS: I calculate my table for people, who can loose 15 hours of own time on this faucet. |
|
|
|
Humm intesting Faucet.
But i have some problems to access the site. The faucet is up or down ?
Faucet is up, but has some DNS troubles. Please investigate previous 3 pages. |
|
|
|
here are screenshots of issues i have been facing .. let me know what can be done .. screenshot 1 - combines picture of ping result and host file http://i63.tinypic.com/2hfnp10.pngThere is no images in posted links. But if in hosts file really '#'...why? Why you place the comment's hash-mark in beginning of line?.. I clearly wrote how to do it. Please read my post once more. It looks like self-torture  |
|
|
|
Guys can you give us your locations where this site is working ?? As checked with https://www.whatsmydns.net/#A/claimwith.me only 3 locations have DNS propagated. And for those for whom hosts file method worked can let other know how you made the website worked as others including me are not able to access the website even after doing the hosts method. This will ensure other team members of the same website are able to access website and claim their satoshis. Simply try to ping IP-address 66.85.133.212. If ping successful and hosts file not work for you, it means you make something wrong. If ping unsuccessful, then you internet provider may block this IP-address. |
|
|
|
|
GUYS! Who got a successful story with a hosts file, DON'T FORGET DELETE THIS LINE WHEN SITE'S DNS GONE OK!!!
Because if site IP will change, your access to it will lost.
|
|
|
|
Please write how to correctly enter, with a new line or replace, I entered a new line then wanted to save, writes no rights to save changes
You must correct permissions on this file.
You can google about files permissions in Windows. You're right, this is must be a new line. |
|
|
|
echo '66.85.133.212 claimwith.me' | sudo tee -a /etc/hosts It worked ! .. thanks Nice to glad you man! |
|
|
|
You must correct permissions on this file. You can google about files permissions in Windows. |
|
|
|
YOU CAN MAKE IT WORK!
Instructions:
Windows:
Open file C:\WINDOWS\system32\drivers\etc\hosts with notepad, then add following line without quotes: "66.85.133.212 claimwith.me"
Linux:
In terminal enter
echo '66.85.133.212 claimwith.me' | sudo tee -a /etc/hosts
MacOS X:
In terminal enter
echo '66.85.133.212 claimwith.me' | sudo tee -a /private/etc/hosts
Now claimwith.me will work!
ClaimWithMe not scam, but have serious problems with domain name system.
Doesn't work in UK ?? Thx man... its work... It's work in all world. |
|
|
|
OK, I done that earlier! YOU CAN MAKE IT WORK ON ANDROID AND IOS! For make work claimwith.me on your phone, you must change DNS to 92.43.0.71. On my iphone: But I don't have android phone. |
|
|
|
YOU CAN MAKE IT WORK!
Instructions:
Windows:
Open file C:\WINDOWS\system32\drivers\etc\hosts with notepad, then add following line without quotes: "66.85.133.212 claimwith.me"
Linux:
In terminal enter
echo '66.85.133.212 claimwith.me' | sudo tee -a /etc/hosts
MacOS X:
In terminal enter
echo '66.85.133.212 claimwith.me' | sudo tee -a /private/etc/hosts
Now claimwith.me will work!
ClaimWithMe not scam, but have serious problems with domain name system.
Any idea for android phone? Sorry, but I can't do that in this time. I can up claimwith.me zone on my own DNS-server after 19:00 MSK and you can change your DNS-address on phone to my. |
|
|
|
Proof:  |
|
|
|
|
YOU CAN MAKE IT WORK!
Instructions:
Windows:
Open file C:\WINDOWS\system32\drivers\etc\hosts with notepad, then add following line without quotes: "66.85.133.212 claimwith.me"
Linux:
In terminal enter
echo '66.85.133.212 claimwith.me' | sudo tee -a /etc/hosts
MacOS X:
In terminal enter
echo '66.85.133.212 claimwith.me' | sudo tee -a /private/etc/hosts
Now claimwith.me will work!
ClaimWithMe not scam, but have serious problems with domain name system.
|
|
|
|
$ dig +trace claimwith.me
; <<>> DiG 9.8.3-P1 <<>> +trace claimwith.me
;; global options: +cmd
. 851 IN NS h.root-servers.net.
. 851 IN NS d.root-servers.net.
. 851 IN NS j.root-servers.net.
. 851 IN NS f.root-servers.net.
. 851 IN NS k.root-servers.net.
. 851 IN NS e.root-servers.net.
. 851 IN NS g.root-servers.net.
. 851 IN NS c.root-servers.net.
. 851 IN NS m.root-servers.net.
. 851 IN NS i.root-servers.net.
. 851 IN NS a.root-servers.net.
. 851 IN NS b.root-servers.net.
. 851 IN NS l.root-servers.net.
;; Received 436 bytes from 192.168.1.11#53(192.168.1.11) in 82 ms
me. 172800 IN NS c0.nic.me.
me. 172800 IN NS b2.nic.me.
me. 172800 IN NS a2.nic.me.
me. 172800 IN NS a0.nic.me.
me. 172800 IN NS b0.nic.me.
;; Received 339 bytes from 192.33.4.12#53(192.33.4.12) in 213 ms
claimwith.me. 86400 IN NS ns2.claimwith.me.
claimwith.me. 86400 IN NS ns1.claimwith.me.
;; Received 98 bytes from 199.253.61.1#53(199.253.61.1) in 145 ms
;; Received 30 bytes from 66.85.133.212#53(66.85.133.212) in 260 ms
$ dig claimwith.me
; <<>> DiG 9.8.3-P1 <<>> claimwith.me
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 43532
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;claimwith.me. IN A
;; Query time: 1001 msec
;; SERVER: 192.168.1.11#53(192.168.1.11)
;; WHEN: Mon Jul 3 16:08:25 2017
;; MSG SIZE rcvd: 30 What's wrong? I got SERVFAIL error when try to resolve "claimwith.me". |
|
|
|
|
