Skip to content

plugin/forward: fix parsing error when handling TLS+IPv6 address#7848

Merged
yongtang merged 1 commit into
coredns:masterfrom
yangsenzk:fix_forward_split
Feb 25, 2026
Merged

plugin/forward: fix parsing error when handling TLS+IPv6 address#7848
yongtang merged 1 commit into
coredns:masterfrom
yangsenzk:fix_forward_split

Conversation

@yangsenzk

@yangsenzk yangsenzk commented Feb 9, 2026

Copy link
Copy Markdown
Contributor

1. Why is this pull request needed and what does it do?

fix plugin/forward bug: when handling TLS+IPv6 config like forward . tls://::1%example.net ..., the ipv6 host will not be correctly parsed, but got weird [::1:853. The cause is there is a function splitZone not support ipv6 format.
2026-02-10_09-29-42

2. Which issues (if any) are related?

3. Which documentation changes (if any) need to be made?

no

4. Does this introduce a backward incompatible change or deprecation?

no

@yangsenzk yangsenzk marked this pull request as draft February 11, 2026 10:01
@yangsenzk yangsenzk force-pushed the fix_forward_split branch 5 times, most recently from 3878af5 to bb66f9e Compare February 12, 2026 10:03
@yongtang

Copy link
Copy Markdown
Member

@yangsenzk Would you mind to fix the DCO issue:

https://github.com/coredns/coredns/pull/7848/checks?check_run_id=63369998286

You can use

git commit -s [--amend]

@yongtang

Copy link
Copy Markdown
Member

@yangsenzk I see the PR is still in draft mode. Is it trashy to be reviewed now?

@yangsenzk

Copy link
Copy Markdown
Contributor Author

@yongtang sry, i'm on vacation. i will make more tests.

@yangsenzk yangsenzk marked this pull request as ready for review February 24, 2026 03:19
@yangsenzk

Copy link
Copy Markdown
Contributor Author

@yongtang I have made some unit tests and real test, it can work properly now.
image

Signed-off-by: yangsenzk <yangsen.zk@qq.com>
@yongtang yongtang merged commit 5b7da1f into coredns:master Feb 25, 2026
11 checks passed
yongtang pushed a commit to yongtang/coredns that referenced this pull request Mar 18, 2026
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

Successfully merging this pull request may close these issues.

2 participants