Feature #1836
RFC 5006 support for DNS from RAs
| Status: | New | Start date: | 09/01/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | 2.1 | |||
| Affected version: | 2.1-IPv6 | Affected Architecture: |
Description
Need RFC 5006 support for DNS from RAs
Associated revisions
Now that our rtadvd binary supports RDNSS we can tack the search domain and DNS servers onto the stack.
Ticket #1836
Add proper validation to the services_rtadvd_configure() to only pick up the IPv6 nameservers if any
Ticket #1836
Update radns to latest version that builds fine
It helps ticket #1836
History
#1
Updated by Seth Mos over 1 year ago
Found this client which is even listed in the FreeBSD ports, dump the info into our filesystem and the rest is picked up automatically.
http://hack.org/mc/hacks/radns/
I also found patches that apply to FreeBSD for rtadvd support. That shouldn't be too hard.
http://lists.freebsd.org/pipermail/freebsd-bugs/2011-April/043904.html
http://opal.com/jr/freebsd/rdnss/
Part of those are already integrated into FreeBSD HEAD.
Maybe our rtadvd is already new enough to configure those DNS server addresses.
I've added the radns port to our build. It's not in the FreeBSD port system yet so it's a pfPort for now.
#2
Updated by Seth Mos over 1 year ago
rtadvd service support committed. should fix both dns server and rtadvd clients to get the same information.
radns client on hold for now until pfport is fixed. the uid and gid values radns don't exist on the builder
#3
Updated by Seth Mos over 1 year ago
- Status changed from New to Feedback
Client support not added yet, pfPort for it doesn't build because of uid missing that the client uses.
#4
Updated by Renato Botelho 2 months ago
- Status changed from Feedback to New
radns was updated and now builds fine