mirror of
https://github.com/nsupdate-info/nsupdate.info.git
synced 2026-04-25 16:45:55 +03:00
[GH-ISSUE #467] Question: Sub-subdomain hosts without having to add each subdomain as availiable domain first? #342
Labels
No labels
bug
bug
duplicate
easy
easy
enhancement
enhancement
invalid
needs help
pull-request
scalability
security
task
urgent
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nsupdate.info-nsupdate-info#342
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @abclution on GitHub (Jul 27, 2020).
Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/467
Hi @ThomasWaldmann , long time no chat! Hope you are safe and healthy! Finally getting some time to play with nsupdate again.. 👍
On to my question. Sorry, not really sure what it is called, let me explain.
I have added a dyn capable domain, greatdomain.com
The interface lets me add a host, xxxx.greatdomain.com.
I would like to add a host, yyyy.xxxx.greatdomain.com,
without having to first add xxxx.greatdomain.com as a separate dynamic capable domain, first.
If I try to create yyyy.xxxx.greatdomain.com without adding xxxx.greatdomain.com as a domain first I get this error.
As far as I can tell, I can dynamically create these sub.sub.domain.com through the bind nsupdate as it just gets filed under the primary domain zone.
I can accept there may be reasons for this, but it sure would be helpful to know what they are for my own understanding?
Thanks!
@ThomasWaldmann commented on GitHub (Jul 28, 2020):
The software is built with the assumption that there exists a dynamic domain (llike
nsupdate.info) and that there are hosts added to / removed from that domain.Introducing subdomain levels in between could have unwanted consequences and maybe even bad security consequences, so this is no easy change.
E.g. if one user only adds
foo.barand another user addsbarto the same base domain - because browser assume there is a relationship between domain and hosts or domain, subdomain and hosts. There is only the publicsuffix list declaring otherwise and we can't assume people would use that appropriately (esp. not if malicious).