https://community.extremenetworks.com/t5/extremeswitching-exos-switch/router-discovery-dnssl-in-xos-15-6-3-1p9-broken/m-p/17641#M614 I updated my BD8806s from 15.4.something to 15.6.3.1p9<BR /> I had this in my vlan config:<BR /> configure vlan DC_Techs router-discovery ipv6 add dnssl dc.local<BR /> configure vlan DC_Techs router-discovery ipv6 other-config-flag on<BR /> enable router-discovery ipv6 vlan DC_Techs<BR /> together with other things, like "add rdnss", "add prefix", etc, for IPv6 autoconfiguration<BR /> <BR /> Suddenly - after the upgrade - I get errors in my logs like:<BR /> <NETTOOLS.ROUTERADV.LKUPDNSSLSFXFAIL> MSM-A: DNSSL Suffix Lookup failed for received Router Advertisement on vlan DC_Techs from fe80::204:96ff:fe8f:c9ea with a DNSSL suffixYes, the "with a DNSSL suffix" *is* the last part of the line. It doesn't let me know what the suffix is that 'failed', but at this time I can only assume it's really an empty/blank/0 suffix <span class="lia-unicode-emoji" title=":disappointed_face:">😞</span><BR /> <BR /> Did a "show router-discovery DC_Techs" on my 8806s - looks fine, has "dc.local" showing on both.<BR /> <BR /> Thought, "ok, let's just kill the dnssl entry" by doing:<BR /> # configure vlan DC_Techs router-discovery ipv6 delete dnssl dc.local <BR /> Error: The specified DNS Suffix is not configuredSay what? OK, "configure.... delte dnssl all" - that worked.<BR /> Tried to add and delete by name - same thing.<BR /> <BR /> I still have a pair of 8806s running 15.5.2.9 where I can add and delete dnssl domain names by name just fine, and where neither errors happen at all, and "sh router-discovery vlan DC_Techs" yields the same output as on the 15.6.3.1 BDs.<BR /> <BR /> I know that Windows doesn't even understand IPv6's dnssl advertisements, and we usually hand-roll our Unix/Linux boxes, so it doesn't matter all that much - I just wanted to point out something rather odd.<BR /> <BR /> Adding and deleting rdnss entries by specifying the addresses works just fine.<BR /> <BR /> Frank<BR /></NETTOOLS.ROUTERADV.LKUPDNSSLSFXFAIL> Sat, 05 Mar 2016 01:38:00 GMT Frank 2016-03-05T01:38:00Z https://community.extremenetworks.com/t5/extremeswitching-exos-switch/router-discovery-dnssl-in-xos-15-6-3-1p9-broken/m-p/17641#M614 I updated my BD8806s from 15.4.something to 15.6.3.1p9<BR /> I had this in my vlan config:<BR /> configure vlan DC_Techs router-discovery ipv6 add dnssl dc.local<BR /> configure vlan DC_Techs router-discovery ipv6 other-config-flag on<BR /> enable router-discovery ipv6 vlan DC_Techs<BR /> together with other things, like "add rdnss", "add prefix", etc, for IPv6 autoconfiguration<BR /> <BR /> Suddenly - after the upgrade - I get errors in my logs like:<BR /> <NETTOOLS.ROUTERADV.LKUPDNSSLSFXFAIL> MSM-A: DNSSL Suffix Lookup failed for received Router Advertisement on vlan DC_Techs from fe80::204:96ff:fe8f:c9ea with a DNSSL suffixYes, the "with a DNSSL suffix" *is* the last part of the line. It doesn't let me know what the suffix is that 'failed', but at this time I can only assume it's really an empty/blank/0 suffix <span class="lia-unicode-emoji" title=":disappointed_face:">😞</span><BR /> <BR /> Did a "show router-discovery DC_Techs" on my 8806s - looks fine, has "dc.local" showing on both.<BR /> <BR /> Thought, "ok, let's just kill the dnssl entry" by doing:<BR /> # configure vlan DC_Techs router-discovery ipv6 delete dnssl dc.local <BR /> Error: The specified DNS Suffix is not configuredSay what? OK, "configure.... delte dnssl all" - that worked.<BR /> Tried to add and delete by name - same thing.<BR /> <BR /> I still have a pair of 8806s running 15.5.2.9 where I can add and delete dnssl domain names by name just fine, and where neither errors happen at all, and "sh router-discovery vlan DC_Techs" yields the same output as on the 15.6.3.1 BDs.<BR /> <BR /> I know that Windows doesn't even understand IPv6's dnssl advertisements, and we usually hand-roll our Unix/Linux boxes, so it doesn't matter all that much - I just wanted to point out something rather odd.<BR /> <BR /> Adding and deleting rdnss entries by specifying the addresses works just fine.<BR /> <BR /> Frank<BR /></NETTOOLS.ROUTERADV.LKUPDNSSLSFXFAIL> Sat, 05 Mar 2016 01:38:00 GMT https://community.extremenetworks.com/t5/extremeswitching-exos-switch/router-discovery-dnssl-in-xos-15-6-3-1p9-broken/m-p/17641#M614 Frank 2016-03-05T01:38:00Z https://community.extremenetworks.com/t5/extremeswitching-exos-switch/router-discovery-dnssl-in-xos-15-6-3-1p9-broken/m-p/17642#M615 Hi Frank,<BR /> I'd recommend that you open a case with GTAC for this one. It sounds like it will need further review so it can be sent to engineering.<BR /> <BR /> Thanks,<BR /> -Drew<BR /> Mon, 07 Mar 2016 22:12:00 GMT https://community.extremenetworks.com/t5/extremeswitching-exos-switch/router-discovery-dnssl-in-xos-15-6-3-1p9-broken/m-p/17642#M615 Drew_C 2016-03-07T22:12:00Z