Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hive NA server not working #254

Open
wizzy99 opened this issue Jan 17, 2022 · 7 comments
Open

Hive NA server not working #254

wizzy99 opened this issue Jan 17, 2022 · 7 comments

Comments

@wizzy99
Copy link

wizzy99 commented Jan 17, 2022

My son has been getting routed to the European server rather than the NA server recently. Attempts within the game to connect to NA (where the majority of the users are at 8pm EST) resulted in "Bad IP error". Adding a server with ca.hivebedrock.network (which used to be the NA host) resulted in the same error.

Found that if we added a server using the FQDN hivebedrock.us we were able connect, so may need to add this new domain to the allow list.

C:\Users\wizzy99>nslookup ca.hivebedrock.network
Server: zyx
Address: 192.168.11.1

Non-authoritative answer:
Name: hivebedrock.us
Addresses: 51.222.104.173
144.217.196.205
51.222.41.14
51.222.128.64
51.222.53.167
Aliases: ca.hivebedrock.network

@CrafterPika
Copy link
Collaborator

CrafterPika commented Jan 17, 2022

My son has been getting routed to the European server rather than the NA server recently.

Could be related to commit fc4e2ec(?), where i tweaked how featured servers IPs are being handled, but then i am wondering where is your DNS server/BedrockConnect Instance is located at.

Attempts within the game to connect to NA (where the majority of the users are at 8pm EST) resulted in "Bad IP error". Adding a server with ca.hivebedrock.network (which used to be the NA host) resulted in the same error.

I couldn't reproduce this, joined ca.hivebedrock.network worked perfectly fine.

@wizzy99
Copy link
Author

wizzy99 commented Jan 18, 2022

My son has been getting routed to the European server rather than the NA server recently.

Could be related to commit fc4e2ec(?), where i tweaked how featured servers IPs are being handled, but then i am wondering where is your DNS server/BedrockConnect Instance is located at.

DNS is set to the primary bedrockconnect IP hosted by @Pugmatt (104.238.130.180).

server 104.238.130.180
Default Server: mail.pyratron.com
Address: 104.238.130.180

ca.hivebedrock.network
Server: mail.pyratron.com
Address: 104.238.130.180

*** mail.pyratron.com can't find ca.hivebedrock.network: Non-existent domain

@wizzy99
Copy link
Author

wizzy99 commented Jan 18, 2022

Using jdextraze's server, DNS resolves correctly, so seems to be localized to @Pugmatt DNS server.

server 173.82.100.84
Default Server: [173.82.100.84]
Address: 173.82.100.84

hivebedrock.us
Server: [173.82.100.84]
Address: 173.82.100.84

Non-authoritative answer:
Name: hivebedrock.us
Addresses: 158.69.151.185
167.114.165.240
51.222.53.167
51.222.82.55
198.27.111.218

ca.hivebedrock.network
Server: [173.82.100.84]
Address: 173.82.100.84

Name: ca.hivebedrock.network
Address: 173.82.100.84

@CrafterPika
Copy link
Collaborator

CrafterPika commented Jan 18, 2022

*** mail.pyratron.com can't find ca.hivebedrock.network: Non-existent domain
Using jdextraze's server, DNS resolves correctly, so seems to be localized to @ Pugmatt DNS server.

apologies i didn't try the main one, i tried on my own one, on main i were able reproduce this.

DNS is set to the primary bedrockconnect IP hosted by @ Pugmatt (104.238.130.180).

Strange why it routes to Europe then, tho i am being honest i don't see why fc4e2ec would cause this, all it's literally doing is equivalent to $ ping hivebedrock.network in the command-line. All i know that Pugmatt's DNS server is multi-load load balanced, meaning it uses multiple server to handle the traffic, pretty sure some of these are located in europe (counter me if i am wrong..) causing hive to return an IP from the European server.

@Pugmatt
Copy link
Owner

Pugmatt commented Jan 18, 2022

All the servers load balanced in the official DNS are located in the US, so it's a bit odd that it would be routing to their Europe server. But, it does appear to be doing that after testing on my end.

It's less so the DNS and more what @CrafterPika said where the BedrockConnect server is grabbing the IP from the domain with the recent change. When I ping hivebedrock.network on my server machine it does indeed return one of the European IPs, so I think it's something with how the server is setup with my host in correlation how the Hive detects the country. Either way, I'll look into it and see why this is occurring.

EDIT: As for why ca.hivebedrock.network doesn't work, it's because the DNS is overriding the whole hivebedrock.network domain, so the subdomains arent working. I'll look into a solution for this as well so these work.

@Pugmatt
Copy link
Owner

Pugmatt commented Jan 21, 2022

Thanks for the patience, should now be working. It will still direct to the European server by default, but the region selector in the Hive server should now be working, along with the domains ca.hivebedrock.network. (And other region domains)

@jdextraze
Copy link
Contributor

Sorry if this comment is really late... my DNS has a wildcard setup on the hivebedrock.network domain, this is why it was working. So 2 things need fixing:

First, the bind install script only setup @ and geo subdomain, it should setup a wildcard for hivebedrock.network.

Second, only geo.hivebedrock.network is geo localized, not hivebedrock.network which seems to always go to Europe. That domain should be used instead in Bedrock Connect. But that domain would still be geo localized from the server's perspective, not the user's.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants