mirror of
https://github.com/nsupdate-info/nsupdate.info.git
synced 2026-04-25 08:35:56 +03:00
[GH-ISSUE #230] related host: related AAAA-hosts should have an additional A-Record #202
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#202
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 @hensing on GitHub (Dec 27, 2015).
Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/230
An option to inherit the A record from the related host would be great, e.g., related.sub.example.com inherits the A-record from sub.example.com.
@ThomasWaldmann commented on GitHub (Dec 29, 2015):
Nice feature if you port-forward base.dom:port -> host.base.dom:port, then you can just use host.base.dom with port and it works, no matter whether it uses v4 or v6.
But: if you can't use the same port on base.dom (v4) as on host.base.dom (v6), you can not avoid connecting to the v4 address any more and your connection will only work in 50% of the cases.
Thus, this requires an option and the default should be off.
@ThomasWaldmann commented on GitHub (Dec 29, 2015):
Hmm, I guess this is already possible, just maybe not obvious:
Try setting the v4 interface id to 0.0.0.0 then you should get an A record that is main address + 0.0.0.0 == main address.
So, if that solves your issue, maybe it should be made more obvious / better documented?
@hensing commented on GitHub (Dec 29, 2015):
that's exactly what I was looking for