SixXS::Sunset 2017-06-06

announing namesever for ipv6 only autoconf clients
[de] Shadow Hawkins on Sunday, 02 November 2008 13:06:20
Hi,... i'm on linux and i wonder how can a autoconf client (ipv6 only) find out, what nameserver to use? Is radvd on the router side able to announce a nameserver to the client? (or zebra)? Or is there another daemon for this? Thanks! best regards
announing namesever for ipv6 only autoconf clients
[ch] Jeroen Massar SixXS Staff on Sunday, 02 November 2008 13:51:26
You would need a RFC5006 compliant RA-server and RA-client (which thus mostly means kernel...). For Linux see http://rdnssd.linkfanel.net/ Otherwise you can of course go to DHCPv6 which solves all of that and a lot more.
announcing nameserver for ipv6 only autoconf clients
[de] Shadow Hawkins on Tuesday, 04 November 2008 17:42:15
Hi,... i try to use radvd and dhcp6s together with no luck. The clients (vista) can successfully configure their addresses, but can't get the ns from dhcp6s. I can't figure out why. Any suggestion on this? When i use radvd for the ns address, with option "RDNSS $ipv6-addr { };", the vista clients are getting correctly their ipv6 nameserver address. But i want to use radvd/dhcp6s or zebra/dhcp6s, rather than only radvd. any suggestion is welcome best regards
announcing nameserver for ipv6 only autoconf clients
[ch] Jeroen Massar SixXS Staff on Tuesday, 04 November 2008 20:57:52
Why would you want to use Zebra? (I do hope you mean Quagga in any case as the Zebra code is very very very outdated and broken). As for why it doesn't work, you will have to provide the config files, wireshark dumps and other details, otherwise people who will be reading this will just be guessing in the wild. I have to note that I didn't ever bother with anything else but simple RAs as the DNS server is already configured with IPv4 DHCP, and RAd addresses are more or less static too, thus that works for me(tm).
announcing nameserver for ipv6 only autoconf clients
[de] Shadow Hawkins on Friday, 07 November 2008 22:35:44
Hi,... oh yes, i mean quagga. Sry. I'm just searching around, what combination of software will fit my needs best. What i simply want to archive is, that i have nothing to do on the client side. In my current ipv4 enabled net, it works very fine with bind and dhcpd for windows and linux clients. I can provide all needed network informations through my dhcpd to make the client happy and get resolvable hostnames. I only have to put the MAC and a hostname in my central config for dhcpd. I'm just a little confused about the concept of providing the same information to ipv6 clients. (and for the future to ipv6-only clients) Am i right, if i say, that current development stage of e.g. dhcp6s can't do this? Sorry for bad english, but i hope you catch my thoughts. :-) best regards
announcing nameserver for ipv6 only autoconf clients
[ch] Jeroen Massar SixXS Staff on Monday, 10 November 2008 09:53:30
You can use: IPv4-only: DHCPv4 IPv6-only: RA + RADDNS (RFC5006) IPv6-only: RA + DHCPv6 IPv4+IPv6: DHCPv4 + RA IPv4+IPv6: DHCPv4 + DHCPv6 It just depends on what you really need and what matches your wishes more.
announcing nameserver for ipv6 only autoconf clients
[de] Shadow Hawkins on Tuesday, 18 November 2008 13:36:58
Thank you, Jeroen! I've got it to work finally. I use now "radvd" for Prefix-Announcement and "dhcp6s" for providing the nameserver information only. (together with "dhcpd" and "bind" on the ipv4 side). Works fine with Windows Vista and Windows Server without doing any work on the client side. :-) The only thing is, that Windows always decided to use a "fe80::" as ipv6 default gateway address, which imho *should* be the Global ipv6 address of the router. (?) Anyway, it works for now. Another thing is, that i'm unsure about the usage of the /64 and /48 Subnet Address for the dhcp6s. For radvd is is clearly "prefix 2001: ... ::/64", but dhcp6s is the same? For example, is this correct for a /48 sixxs subnet? pool { range 2001: ... ::0002 to 2001: ... ::0010/64; prefix 2001: ... ::/48; } Thank you very much! best regards Stefan --
announcing nameserver for ipv6 only autoconf clients
[ch] Jeroen Massar SixXS Staff on Tuesday, 18 November 2008 14:31:00
The only thing is, that Windows always decided to use a "fe80::"
as ipv6 default gateway address, which imho *should* be the
Global ipv6 address of the router. (?)
No, using fe80:: is fine there. IPv6 has built-in 'alive' checks thus this way it can easily be verified that the next hop (though both link-local and global would work) is alive and can be used for routing packets instead of just trying to send them to a blackhole.

Please note Posting is only allowed when you are logged in.
Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker