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

AWS DHCP Option set domain names separated by 032 when using systemd-networkd #3412

Closed
zmrow opened this issue Sep 5, 2023 · 0 comments · Fixed by #3416
Closed

AWS DHCP Option set domain names separated by 032 when using systemd-networkd #3412

zmrow opened this issue Sep 5, 2023 · 0 comments · Fixed by #3416
Assignees
Labels
area/networking Issues related to networking support or configuration status/in-progress This issue is currently being worked on type/bug Something isn't working

Comments

@zmrow
Copy link
Contributor

zmrow commented Sep 5, 2023

Image I'm using:
aws-k8s-1.28 with systemd-networkd built from #3394

What I expected to happen:
DHCP option set domain-names to be space-separated.

What actually happened:
When testing for #3394, I noticed, domain names are separated by 032 rather than by a space.

DNS Domain: us-west-2.compute.internal032abcdefg.com

This is a known issue when using systemd-networkd/resolved. Further explanation is in the linked issue, but the explanation is:

The issue here is that the VPC DHCP server sends sends the provided list of domains using DHCP option 15, which only supports a single domain name (see RFC 2132 section 3.17). When multiple domain names are provided, they're separated by a space character, which isn't valid in a domain name, so systemd-resolved replaces the space with a decimal encoding of the ascii value.

How to reproduce the problem:

  1. Create a dhcp option set with multiple domain name like:
    test1.com test2.com
  2. Run a new instance connected to the VPC, resolvectl will show the 032-separated domains
@zmrow zmrow added type/bug Something isn't working status/needs-triage Pending triage or re-evaluation labels Sep 5, 2023
@markusboehme markusboehme added status/in-progress This issue is currently being worked on area/networking Issues related to networking support or configuration and removed status/needs-triage Pending triage or re-evaluation labels Sep 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/networking Issues related to networking support or configuration status/in-progress This issue is currently being worked on type/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants