|
|
Post by ???DaddyIndica on Jul 6, 2017 23:20:22 GMT
So when I ping my server with CMD I get a cloudflare IP and I guess that's the reason no one can connect with the domain. I use a freenom domain with CloudFlare nameservers so I can use SRV records since freenom doesn't work. My DNS:  pings:  |
|
_Windows
Club 4000 Member
Posts: 7,881
| Likes: 9,611
|
Post by _Windows on Jul 7, 2017 0:27:22 GMT
You need a subdomain that bypasses CloudFlare pointed to your servers IP. CloudFlare has a setting for that.
|
|
|
|
Post by ???DaddyIndica on Jul 7, 2017 1:13:17 GMT
You need a subdomain that bypasses CloudFlare pointed to your servers IP. CloudFlare has a setting for that. How?? |
|
_Windows
Club 4000 Member
Posts: 7,881
| Likes: 9,611
|
Post by _Windows on Jul 7, 2017 1:26:51 GMT
|
|
|
|
Post by ???DaddyIndica on Jul 7, 2017 2:25:14 GMT
still isn't working, still pinging to cloudflare0 |
|
taah
Club 4000 Member
sick af
Posts: 4,778
| Likes: 2,850
|
Post by taah on Jul 7, 2017 2:53:08 GMT
i M guessing you're trying to point that to falceso's vps's ip. did you ask him for the new IP for his vps
|
|
|
|
Post by ???DaddyIndica on Jul 7, 2017 2:54:10 GMT
i M guessing you're trying to point that to falceso's vps's ip. did you ask him for the new IP for his vps I totally didn't ping the server |
|
StevenNL2000
Forum Admin 
Posts: 6,415
| Likes: 6,936
IGN: StevenNL2000
Timezone: UTC+01:00
Member is Staff. Need immediate assistance? Send a PM
|
Post by StevenNL2000 on Jul 7, 2017 9:22:16 GMT
That's not a CloudFlare IP you're getting in your command prompt. It belongs to the search page you get from your internet provider (AT&T) when you visit a domain that doesn't exist. Your DNS was never configured at all.
|
|
|
|
Post by jamesgamer1999 on Jul 7, 2017 9:41:32 GMT
^^ Apparently the IP is coming from Rackspace Hosting (RACKS-8), and not cloudflare at all..
Where as if I get boards.net lookup, it's Cloudflare, Inc. (CLOUD14)
|
|
Wild1145
Club 4000 Member
Inactive Player & Inactive Senior Admin
Posts: 10,414
| Likes: 9,680
|
Post by Wild1145 on Jul 7, 2017 14:57:05 GMT
You will need to flush any local DNS Settings, and DNS can take anywhere from mins to 72 hours to properly propagate across a network.
|
|
- March 7, 2016 - Adaptified
- October 31, 2016
- November 30, 2017
- Achieved March 1, added March 16 (early)
