128bit
Senior Member
weird problem here, i know but in light of it only showing up after the latest build, i thought i'd post it.
while using guest (2) clients were not able to resolve "some" host names. when "she" mentioned it, i dismissed it since she goes everywhere with no care and may have "eaten" something along the way. all she cares about is getting where she wants to go and pretty much ignores or answers "yes" to everything if it allows her to accomplish the goal. so yeah, that's why she's on guest.
after this 386.4 build, she could no longer reach a local store (harristeeter.com). i let her use my rj45 box (obviously, not on guest) but my wireless box (also not on guest) worked as well using some default dns (103.86.96.100/103.86.99.100). my ac86u does NOT auto-connect to a dns server. today, she had a different hiccup, so i decided to pay some attention.
she had another http/https connect problem that looked like a dns failure. i was able to duplicate the problem on my own wireless box as well. after reconfiguring the client's dns (quad9) everything worked. so i added that same dns address to the rt-ac86u on the lan/wan pages and all the guest clients worked without needing a dns specific remapping. interesting that it never showed on the other ssids, just guest and lastly, when using a vpn app, all clients worked ok since they supply a dns.
so problem solved. just thought i'd share since it was so crazily domain specific. most worked but a select 2 in our case no longer worked. bottom line, folks may want to use another dns other than 103.86.96/99.100 that were defaults on my configuration. other than that, all's well with 386.4.
while using guest (2) clients were not able to resolve "some" host names. when "she" mentioned it, i dismissed it since she goes everywhere with no care and may have "eaten" something along the way. all she cares about is getting where she wants to go and pretty much ignores or answers "yes" to everything if it allows her to accomplish the goal. so yeah, that's why she's on guest.
after this 386.4 build, she could no longer reach a local store (harristeeter.com). i let her use my rj45 box (obviously, not on guest) but my wireless box (also not on guest) worked as well using some default dns (103.86.96.100/103.86.99.100). my ac86u does NOT auto-connect to a dns server. today, she had a different hiccup, so i decided to pay some attention.
she had another http/https connect problem that looked like a dns failure. i was able to duplicate the problem on my own wireless box as well. after reconfiguring the client's dns (quad9) everything worked. so i added that same dns address to the rt-ac86u on the lan/wan pages and all the guest clients worked without needing a dns specific remapping. interesting that it never showed on the other ssids, just guest and lastly, when using a vpn app, all clients worked ok since they supply a dns.
so problem solved. just thought i'd share since it was so crazily domain specific. most worked but a select 2 in our case no longer worked. bottom line, folks may want to use another dns other than 103.86.96/99.100 that were defaults on my configuration. other than that, all's well with 386.4.
