adam/znc
1
0 Fork 0
mirror of https://github.com/znc/znc.git synced 2026-11-03 10:52:22 +01:00
Code Issues 362 Packages Projects Releases Wiki Activity

Separate bindhosts for IPv4 and IPv6 #541

New Issue
Closed
opened 2026-10-05 04:28:39 +02:00 by adam · 7 comments
adam commented 2026-10-05 04:28:39 +02:00
Owner
Copy link
Copy source

This has been talked on IRC often, but I was unable to find issue, so I am opening this one as I am starting to see the point.

My shell gives users own IPv6 addresses for reverse DNS, but IPv4 addresses are all shared. If I set bindhost as that address, I am locked out of IPv4. What I want is

  • IPv6 bindhost:
  • IPv4 bindhost:

If https://github.com/znc/znc/issues/241 was also implemented, I would get my rDNS IPv6 most of time, but when IPv6 doesn't work I would get connected anyway with IPv4. Currently all the networks that I am on have IPv6, but they have various issues such as having only one IPv6 server or the IPv6 connectivity being tunnelled and having random tunnel issues.

This has been talked on IRC often, but I was unable to find issue, so I am opening this one as I am starting to see the point. My shell gives users own IPv6 addresses for reverse DNS, but IPv4 addresses are all shared. If I set bindhost as that address, I am locked out of IPv4. What I want is - IPv6 bindhost: <my own domain> - IPv4 bindhost: <empty> If https://github.com/znc/znc/issues/241 was also implemented, I would get my rDNS IPv6 most of time, but when IPv6 doesn't work I would get connected anyway with IPv4. Currently all the networks that I am on have IPv6, but they have various issues such as having only one IPv6 server or the IPv6 connectivity being tunnelled and having random tunnel issues. <!-- github-sync-id:95814509 -->
adam closed this issue 2026-10-05 04:28:39 +02:00
adam commented 2026-10-05 04:28:40 +02:00
Author
Owner
Copy link
Copy source

You can have a domain which resolves to your IPv6 and your IPv4 at the same time, and use that as bindhost configured in ZNC.
Even without #241 you're connected sometimes via IPv6, sometimes via IPv4 with such setup.
Also, #241 does not cause you to prefer IPv6, in fact it may be vice versa esp. in case of tunnels. It would choose whatever protocol connects faster.

You can have a domain which resolves to your IPv6 and your IPv4 at the same time, and use that as bindhost configured in ZNC. Even without #241 you're connected sometimes via IPv6, sometimes via IPv4 with such setup. Also, #241 does not cause you to prefer IPv6, in fact it may be vice versa esp. in case of tunnels. It would choose whatever protocol connects faster. <!-- github-comment-id:122530610 -->
adam commented 2026-10-05 04:28:41 +02:00
Author
Owner
Copy link
Copy source

Does that work even if my bindhost is x.example.org and IPv4 reverse DNS is y.example.com?

I didn't think about adding records, but I have done that now and I am just wondering that. Also does ZNC have a method for checking itself where does bindhost resolve to as the previously set AAAA-record had TTL of 12 hours?

Does that work even if my bindhost is x.example.org and IPv4 reverse DNS is y.example.com? I didn't think about adding records, but I have done that now and I am just wondering that. Also does ZNC have a method for checking itself where does bindhost resolve to as the previously set AAAA-record had TTL of 12 hours? <!-- github-comment-id:122533402 -->
adam commented 2026-10-05 04:28:42 +02:00
Author
Owner
Copy link
Copy source

ZNC never looks at reverse DNS, it's IRC server's job to do that and show it in hostmask.
ZNC just uses getaddrinfo(). It's the resolver's (and also DNS server's) job to honor TTL.

ZNC never looks at reverse DNS, it's IRC server's job to do that and show it in hostmask. ZNC just uses `getaddrinfo()`. It's the resolver's (and also DNS server's) job to honor TTL. <!-- github-comment-id:122533956 -->
adam commented 2026-10-05 04:28:42 +02:00
Author
Owner
Copy link
Copy source

That appears to work, so I am closing this issue.

That appears to work, so I am closing this issue. <!-- github-comment-id:122635282 -->
adam commented 2026-10-05 04:28:43 +02:00
Author
Owner
Copy link
Copy source

Another question, what happens if the domain points to 0.0.0.0 (A record) and correct address with IPv6? When IPv4 is used, ZNC will act like bindhost was 0.0.0.0?

Another question, what happens if the domain points to 0.0.0.0 (A record) and correct address with IPv6? When IPv4 is used, ZNC will act like bindhost was 0.0.0.0? <!-- github-comment-id:122636108 -->
adam commented 2026-10-05 04:28:44 +02:00
Author
Owner
Copy link
Copy source

Should be like that, yep. But not tested.

Should be like that, yep. But not tested. <!-- github-comment-id:122637949 -->
adam commented 2026-10-05 04:28:44 +02:00
Author
Owner
Copy link
Copy source

I will change it and test it when I restart next time assuming it's after TTL.

I will change it and test it when I restart next time assuming it's after TTL. <!-- github-comment-id:122637990 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/znc#541