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.

Sign up for GitHub

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

Jump to bottom

Use standard notation for IPv6 local loopback address ( ::1 instead of 0::1 ) #304

Closed
shoulders opened this issue Dec 2, 2021 · 3 comments · May be fixed by #306
Closed

Use standard notation for IPv6 local loopback address ( ::1 instead of 0::1 ) #304

shoulders opened this issue Dec 2, 2021 · 3 comments · May be fixed by #306
Labels
duplicate known_issue

Kommentare

@shoulders
Copy link

Within the documentation and config files of stubby you use the address 0::1 for the IPv6 local loopback address (which does work) but I cannot find anywhere else that uses this form, everyone use ::1

I think these instances should be changed to keep things easier to read unless there is a technical reason for this.

These are a few that I found
README.md

listen_addresses:
  - 127.0.0.1
  -  0::1

stubby.yml.example

stubby/stubby.yml.example

Line 126 in f105374

- 0::1

@shoulders shoulders mentioned this issue Dec 2, 2021
Öffnen Sie
This was referenced Dec 4, 2021
Öffnen Sie
Öffnen Sie
@ArchangeGabriel
Copy link
Contributor

See getdnsapi/getdns#358.

saradickinson added a commit that referenced this issue Jun 7, 2022
@saradickinson
Minor updates to the config file comments correcting mismatches and c…
d0f5b97 
…larifying defaults - based on feedback in #305 and #304
@saradickinson
Copy link
Contributor

As noted - this is an issue with our parser but I've added a comment directly into the config file to make this clearer

@saradickinson
Copy link
Contributor

I'm closing this since the updated text was in 0.4.1 release but also marking as duplicate of the issue raising the underlying problem

@saradickinson saradickinson closed this as not planned Won't fix, can't repro, duplicate, stale Jan 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
duplicate known_issue
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Quote IP addresses in "listen_addresses" when building JSON string uzlonewolf/stubby
3 participants
@shoulders @ArchangeGabriel @saradickinson