Plugin category: IP Limit Minecraft version: 1.16.4 Paper Suggested name: LimiterIP What I want: limit create accounts from 1 a unique IP address, the limit would be 3 accounts per 1 unique IP address, in the plugin conifg it would be possible to change to any number of accounts from 1 unique IP address.The command /limitip check <Nick> would be to check the IP of that nickname, and how many accounts on the same IP he did. The limit could be changed with the command / limitip set <limit_numbers_account_on_1_IP> Ideas for commands: /limitip reload /limitip check <nick> /limitip set <limit_numbers_account_on_1_IP> Ideas for permissions: limitip.reload limitip.check limitip.limitset limitip.* When I'd like it by: as soon as possible would be much appreciated
This is probably not a good idea, most people's IP address changes all the time. For example most ISPs have a pool of IP addresses they will assign to their clients. Every time someone "resets their router" they loose the connection, their old IP address, and then given a new one from the pool. The new one you get, might be someone's old IP address that already has 3 registered accounts, or you could just keep "resetting your router" making as many accounts as you want. To end up with the same IP every time, you have to usually ask your ISP to do so (static IP), and they usually charge extra for it. Having changing IP addresses is a good thing for privacy and security, people can not target you directly, or track your behavior the same way they would if you just kept the same number. That is why we have DNS and domain names, you can type in example.com, and it will go find out what the current IP address for example.com is.
Good morning @ForbiddenSoul, I hope that you are well and it is a pleasure to meet you. I apologise if I have misinterpreted your reply, however DNS is not able to discover the current IP address of a server automatically as you have described unless software is installed on the server to detect whenever the IP address changes and subsequently contact the nameserver to update the record. This solution is not recommended as end users may experience intermittent connection issues during the process as nameserver record updating is generally not immediate. DNS is only able to translate the domain name into an IP address that has been specified in the nameserver records. Accordingly, most people, organisations, and government agencies who are able to run a dedicated line to their servers will have a static IP address to solve the above issues and reduce work for the system administrators.
Yes this is correct @BB563780. It is up to the client to handle IP changes of their machine to the DNS server. This can be done automatically through the Operating System, which it often is for ISP domains that correspond to addresses(a reverse WHOIS lookup will tell you these domains if there are any), if the machine is part of a Domain or Active Directory, other third party software, or manually through something like a web control panel. Despite the DNS server not automatically discovering your IP, it will let traffic directed to your Domain end up at the (hopefully current) address(es) registered with the DNS so that clients will maintain connectivity. The static IP address we both mention solves the problem of a changing address, but as I stated is usually an extra payment that your ISP requires. This will also reduce your security and privacy, but is something that larger organizations must deal with. For example DNS typically use a static address, as connectivity gets difficult if you have to lookup the IP address associated NS1.example, but you are expecting to get that answer from the unknown IP address of NS1.example. This is when clients will use a static IP like 8.8.8.8 (Google public DNS) to determine what the IP address of NS1.example is. The point I am trying to make here is unless every single one of the players connecting to your server has taken the extra steps, and paid the extra money for a static IP, it will be a dynamic IP. Temp bans of IP addresses is fine, it will stop other accounts from the same location from connecting. Limiting the amount of accounts made to 3 from a specific address has potential problems, as your IP at the time of connecting to the server for the very first time may have already been used up by someone else, and if you wish to circumvent the system, you can easily do so by renewing your IP address, being able to register another 3 accounts.
I agree. Another issue to consider regarding special treatment based on IP address for @Steveq7 is carrier-grade NAT that allows multiple end users to be assigned the same IP address simultaneously. It is common practice for internet service providers to subscribe carrier-grade NAT by default to residential end users due to the scarcity in IPv4 addresses as we have exceeded the protocol's original capacity in the 1980's of connecting four billion end users and only some of them have the offer available to opt out.
