rjohnk join:2013-10-26 Eden Prairie, MN |
rjohnk
Member
2013-Oct-26 4:20 pm
[Qwest] DNS Servers not working in Transparent Bridge ModeSet up: Actiontec C1000a as Transparent Bridge to WDAC1300 as router.
I put alternative DNS servers in primary and secondary section of the WD, along with the PPPoE info. Rebooted both devices.
Centurylink's default DNS servers still hold.
If I use the Actiontec as the router and input alternative DNS servers on the modem itself, the DNS works.
The WD Router worked with the alternative DNS servers when hooked up to a Zoom modem using Comcast.
Any ideas? |
|
linicxCaveat Emptor Premium Member join:2002-12-03 United State |
linicx
Premium Member
2013-Oct-26 5:44 pm
Presuming Quest is a phone company and Comcast is the cable company the two do not use the same technology. I am not a tech, I am a CL residential user. They have tightened up security.
The new modems like the C1000a have a router built in for security reasons. When my new modem was installed I had the CL router bypassed to use mine.
For what it's worth, I had a ton of problems with router failures on CL until I switched to ASUS R10+early in 2011. |
|
|
TAZ to rjohnk
Anon
2013-Oct-26 6:23 pm
to rjohnk
This has nothing to do with either the C1000A in bridge mode or "tightened up security" on CL's part.
CL/Q uses PPPoE for IP and DNS resolver assignment. Comcast uses DHCP for that. Both providers will assign their own DNS resolvers to the authenticating device (in this case, your router). The WD router is assigning its own clients IPs and DNS resolvers via DHCP. It has the choice of passing on the provider-supplied resolvers or supplying the user-configured ones.
It sounds like the WD router has a bug where it's not allowing a manual override of the resolvers if they're assigned via PPPoE. If that's the case (and from your post I cannot imagine any other possibility), you wouldn't have run into this with Comcast because they don't use PPPoE. When you switch the C1000A to routing mode, the C1000A is using DHCP to assign IPs and DNS resolvers to internal network clients (and obviously, its override function works properly).
The blame for this lies entirely with WD, not any other party.
Solutions: 1) ensure the WD router firmware is up-to-date; if it is or if the issue persists after an update, contact them and report the issue to them 2) as a temporary solution, you can manually set the DNS resolvers on each of your endpoints. A bit of work, but until WD fixes it (if they ever do; who knows what their support is like on this) it'll work. |
|
rjohnk join:2013-10-26 Eden Prairie, MN |
rjohnk
Member
2013-Oct-26 11:45 pm
Thanks. I had a hunch it would come to that. I have sent in a ticket to WD. |
|
|
TAZ
Anon
2013-Oct-27 12:27 am
One quick thing to try, what if you set the resolvers after the PPPoE session is started? That might override it. If it did you'll have to do it every time the session is reset but that's really rare in my experience. |
|