Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Doesn't work properly with punycode domains #3

Closed
Nothing4You opened this issue Jun 29, 2019 · 1 comment
Closed

Doesn't work properly with punycode domains #3

Nothing4You opened this issue Jun 29, 2019 · 1 comment

Comments

@Nothing4You
Copy link

Adding a new record works:
example.xn--gja.com. 300 IN A 10.0.0.1

nsupdate commands queued:
server localhost
zone xn--gja.com
update add    example.xn--gja.com. 300 IN A 10.0.0.1
send
answer

next edit contains this:

example.ǁ.com.            300   IN A     10.0.0.1

deleting this results in:

nsupdate commands queued:
server localhost
zone xn--gja.com
update delete example.ǁ.com. IN A 10.0.0.1
send
answer

which obviously fails:

update failed: NOTZONE

tested using version 1.2 on debian.

can't even workaround for editing by replacing the name with the punycode name in the temp zonefile, as it'll think i've removed the entries with non-punycode.

@Nothing4You
Copy link
Author

bind 9.14.0 introduced noidnout.
Note that debian stable currently ships with 9.10.3.

@df7cb df7cb closed this as completed in cfd3a2f Jul 28, 2019
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

No branches or pull requests

1 participant