Kinda crazy idea, but there can be a special DNS server, which returns different PTR record for the IP, depending on which ZNC's user/network is connecting currently from that IP, so that each IRC connection has own vhost.
Of course, that requires that NS record links to this DNS server. And TTL should be very small.
The DNS server can be a ZNC module, with port 53 forwarded to it, or it can communicate with ZNC via some protocol...
Kinda crazy idea, but there can be a special DNS server, which returns different PTR record for the IP, depending on which ZNC's user/network is connecting currently from that IP, so that each IRC connection has own vhost.
Of course, that requires that NS record links to this DNS server. And TTL should be very small.
The DNS server can be a ZNC module, with port 53 forwarded to it, or it can communicate with ZNC via some protocol...
<!-- github-sync-id:3816334 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Kinda crazy idea, but there can be a special DNS server, which returns different PTR record for the IP, depending on which ZNC's user/network is connecting currently from that IP, so that each IRC connection has own vhost.
Of course, that requires that NS record links to this DNS server. And TTL should be very small.
The DNS server can be a ZNC module, with port 53 forwarded to it, or it can communicate with ZNC via some protocol...
Hm, the right way is to use IPv6. One vhost per address is enough, because there're many IPv6 addresses around.