| New Shaw hookup; curious about provided Cisco DPC3825 Hey guys!
Forgive me if I show ignorance here with this question:
I was given the Cisco DPC3825 for a new 20Mb hookup (promotion right now). In hooking things up to my network, and replacing my trusty Netgear wireless router with this Cisco (I was on Telus, with just a plain old Speedtouch modem with no wifi), I find that I can assign static IP's and gateway to devices internally, as I am used to, but assigning the static DNS server to the Cisco IP (192.168.1.1) does not work?
So, example would be for Device 1:
IP = 192.168.1.2
Subnet = 255.255.255.0
Gateway = 192.168.1.1 (Cisco modem/router)
DNS = 192.168.1.1 (does not work!)
In fact, what I have had to do is look at the Shaw assigned DNS servers within the Cisco interface, and assign those DNS servers manually to each internal network device if I want it to access the internet...
Is it normal that this Cisco modem/router does not smoothly respond to DNS requests sent to it by devices on its internal IP?
Again, every single router/modem I have ever used, whether Shaw or Telus or whatever...has always been just fine with assigning devices connected to it its internal IP as DNS, and thereafter DNS resolves fine on those devices...
Help me out here fellas...am I on drugs or what? |
|
jtl999Classified CEO
join:2012-11-24 | Use Shaw live chat or »ohmsblog.teamohms.org/2012/06/ho···825.html
for bridge mode |
|
| You are better off, if you have your own router that works well for you, to have your modem put into bridge-mode, and continue to use your Netgear router.
--
Yes, I am not employed and looking for IT work. Have passport, will travel. |
|
|
|
| reply to somedude
I don't think that modem supports dns relay hence the need to specify alternate dns servers. If shaw's addresses are too hard to remember, you can always use google dns at 8.8.8.8 |
|
| Well, thats just weird...wouldn't you say? Not to support DNS relays...thats the very first device (and I have been through a few in various cities and various ISP's) that I have EVER seen that does this...hah!
Anyway, I am ok with the router otherwise...I turn everything off in terms of firewall and such, I have no need for that...and it forwards ports comfortably...
Any other good reasons to switching this thing into bridge mode and putting my old router back in place? (I kind of like the idea of one less device plugged in all the time...trying to be power conscious...) |
|
| If it works for you, then no, leave it in Gateway mode. |
|
twixt
join:2004-06-27
North Vancouver, BC
1 edit | reply to somedude
said by somedude :Well, thats just weird...wouldn't you say? Not to support DNS relays...thats the very first device (and I have been through a few in various cities and various ISP's) that I have EVER seen that does this...hah!
Anyway, I am ok with the router otherwise...I turn everything off in terms of firewall and such, I have no need for that...and it forwards ports comfortably...
Any other good reasons to switching this thing into bridge mode and putting my old router back in place? (I kind of like the idea of one less device plugged in all the time...trying to be power conscious...)
Hi, somedude. Some routers have an option to enable/disable DNS relay. If the router supplied to you has DNS relay disabled for whatever reason - this could be the problem.
Google "DPC3825" and click on the Cisco support website for that router.
Download the User Guide PDF.
Open the PDF and go to Page 33. See the item: LAN Static DNS (Domain Name Server) 1-3
According to the documentation, DNS relay is the default if those fields are unpopulated. Thus, unless there is info in there and that info is incorrect - I would assume that either something else in the router is misconfigured, the consequence of which is a failure to support DNS relay - or the router is defective - or there is a misconfiguration in the Cisco Automatic Query for the DNS values from the cable Head End unit such that those values are not properly autopopulated during the modem/router initialization process.
Note: Cisco have their own "custom weirdness" when it comes to authentication. If support for the Cisco custom-queries has not been properly implemented on the Head End for your particular Cable Segment - this may be the cause of the problem. This is certainly worth either a call to Shaw Tech Support, or a post in the "Ask a Shaw Rep" thread.
Hope this helps. |
|
