You can see if your Host/Host’s ISP is willing to implement the above fix on your IP but most hosts will not if they already have a referral server hosting their up to date IP registration information.
I have reached out to technetium to see about that PR and if it would be beneficial to just implement logic to default back to ARIN data if no contacts are found when attempting to parse the referral server.
169.254.171.26
I’m unable to resolve my public IP either - address is 135.23.87.99 - as an additional note when I go here https://www.networksolutions.com/whois and enter the above IP it hangs
I have the same problem with my clients on IP RANGE: 104.149.182.XX.
I was able to solve my problem my registering using a VPN - in my case HotSpot shield. Once the key has been registered 1 time you are free to use it on any machine going forward and can ditch the VPN.
@d-bubble @technetium Updated the PR to have logic that will use cached ARIN Whois data if any referral server fails to connect or not have a parsing template available.
66.206.8.138 is my machine ip and I am having issues please help
I have confirmed with the CFX Elements that they are working to push the changes I submitted to help resolve 90% of the problems the people posting here have been running into. This hopefully will be live in Keymaster later today.
Great work @fireant456 , with your continued persistence and hard work, you have solved a great issue and you have both the fivem communities and my own thanks. If this ends up working then hooray! if not then there isn’t much more that we can do. 
The merge seems to finally be deployed and I have verified with our affected IPs that the issue is resolved. Feel free to post any further IPs with issues so I can investigate the root cause of those corner case IPs.
I used a vpn and it worked. Now I use the key and I no longer need the vpn. Only needed it to get key.
im getting the Could not resolve the IP specified (136.37.123.217).
I am getting this for 136.32.0.0/11
which includes the person before me
NetRange: 136.32.0.0 - 136.63.255.255
CIDR: 136.32.0.0/11
NetName: GOOGLE-FIBER
NetHandle: NET-136-32-0-0-1
Parent: NET136 (NET-136-0-0-0-0)
NetType: Direct Allocation
OriginAS:
Organization: Google Fiber Inc. (GF)
RegDate: 2015-10-06
Updated: 2015-10-06
Ref: https://rdap.arin.net/registry/ip/136.32.0.0
OrgName: Google Fiber Inc.
OrgId: GF
Address: 1600 Amphitheatre Parkway
City: Mountain View
StateProv: CA
PostalCode: 94043
Country: US
RegDate: 2010-10-08
Updated: 2019-11-01
Ref: https://rdap.arin.net/registry/entity/GF
ReferralServer: rwhois://rwhois.googlefiber.net:8987
OrgAbuseHandle: GFA32-ARIN
OrgAbuseName: Google Fiber Abuse
OrgAbusePhone: +1-650-253-0000
OrgAbuseEmail: abuse@googlefiber.net
OrgAbuseRef: https://rdap.arin.net/registry/entity/GFA32-ARIN
OrgTechHandle: ZG39-ARIN
OrgTechName: Google LLC
OrgTechPhone: +1-650-253-0000
OrgTechEmail: arin-contact@google.com
OrgTechRef: https://rdap.arin.net/registry/entity/ZG39-ARIN
Hey, been trying to generate a key for our Linux VPS and getting the error re not being able to resolve.
Hosting Provider: namecheap
IP: 66.29.139.175
Domain name setup as reverse DNS: gta.rivalclan.gg
Thanks
Hate to necro, but I’m also having this issue. I was planning to do some testing on a private server, but the IP I wanted to use doesn’t work, keymaster “Could not resolve the IP specified”
I went through this thread hoping something would help me fix this situation, but unfortunately, nothing that I’ve seen helps.
If you need my IP to test, shoot me a dm.
I asked a friend to make a pull request Fix for rwhois.googlefiber.net:8987 by FlynnLives · Pull Request #4 · blattersturm/WhoisParser (github.com)
I’m a bit of a loss here.
I do appreciate you helping out with this situation, and I do apologize for my ignorance on the subject
Does your Parser code change the WhoIS return, or does it change what CFX see?
My home IP (198.48.233.10), my work office IP (68.179.113.237), and our DataCenter IP (66.225.152.146) give the same result.
I don’t know if this is a location thing or what.
Also, I don’t know much about coding, so not really sure how to run your Parser as well (I got friends to help, but gotta wait on them)
Still same problem here with this IP : 86.207.135.240
I still with problem with this IP: 191.239.246.120
Don’t bump an ages-old topic with ‘waah, still with problem, plis haaaaalp’.