DNS Settings On Netgear MR314?
DNS Settings On Netgear MR314?
Ok let me try to explain this is a well presented manner:
I have a Netgear MR314 router hooked up to my PC and XBox. I turned off DHCP on my router and manually assigned IP addresses to both of the devices.
I had to set up the XBox in the DMZ area on the router since this was the only workaround that was successful with getting it to work. Well since then my PC often looses it's connection to the internet and I have to power-cycle the router and the cable-modem. (I have RoadRunner by the way.)
If I take the XBox IP out of the DMZ my PC's internet works great for long periods of time. Well I called Netgear tech support and they think it has something to do with the DNS addresses. I have my primary set to my router's IP which is the 192.168.0.1 and left the second one blank. The technician told me to put 4.2.2.2 in as the alternate DNS.
My question is this a bunch of BS? Isn't that 4.2.2.2 a lan IP address?
Should I get actually DNS adresses from RoadRunner and put those in as my primary and secondary? Will my router even allow those values from RoadRunner to be used?
Thanks
I have a Netgear MR314 router hooked up to my PC and XBox. I turned off DHCP on my router and manually assigned IP addresses to both of the devices.
I had to set up the XBox in the DMZ area on the router since this was the only workaround that was successful with getting it to work. Well since then my PC often looses it's connection to the internet and I have to power-cycle the router and the cable-modem. (I have RoadRunner by the way.)
If I take the XBox IP out of the DMZ my PC's internet works great for long periods of time. Well I called Netgear tech support and they think it has something to do with the DNS addresses. I have my primary set to my router's IP which is the 192.168.0.1 and left the second one blank. The technician told me to put 4.2.2.2 in as the alternate DNS.
My question is this a bunch of BS? Isn't that 4.2.2.2 a lan IP address?
Should I get actually DNS adresses from RoadRunner and put those in as my primary and secondary? Will my router even allow those values from RoadRunner to be used?
Thanks
"It's All In The Reflexes."
- YeOldeStonecat
- SG VIP
- Posts: 51171
- Joined: Mon Jan 15, 2001 12:00 pm
- Location: Somewhere along the shoreline in New England
Re: DNS Settings On Netgear MR314?
Should I get actually DNS adresses from RoadRunner and put those in as my primary and secondary? Will my router even allow those values from RoadRunner to be used?
Thanks [/B]
Yes, you can get those DNS servers right from your routers status page of it's web admin when it's connected. Although why did you disable DHCP on the router? No problem leaving it turned on, just assign manual IP's outside the normal DHCP range.
http://www.speedguide.net/read_articles.php?id=177
MORNING WOOD Lumber Company
Guinness for Strength!!!
Guinness for Strength!!!
I thought in order to assign manual IPs I had to turn off DHCP. 
So I plugged my Cable Modem directly into my computer and got the DNS server addresses doing the old "ipconfig /all". I entered those addresses in my PC and XBox DNS server lines and so far it seems to be ok and working great.
My only concern is will those DNS servers always be the same on my RoadRunner? If for any reason I need to cycle down power to the modem will those change?
I still am keeping off the DHCP since I don't think it is affecting my connection one way or another. I just unchecked the box in the DHCP options and the DNS servers in the router configuration are all set to 0.0.0.0 but since there is no checkmark to use DHCP I don't think it matters.
Correct me please if I am wrong on any of this.
**UPDATE**
Very nice article StoneCat. Very informative.
So I plugged my Cable Modem directly into my computer and got the DNS server addresses doing the old "ipconfig /all". I entered those addresses in my PC and XBox DNS server lines and so far it seems to be ok and working great.
My only concern is will those DNS servers always be the same on my RoadRunner? If for any reason I need to cycle down power to the modem will those change?
I still am keeping off the DHCP since I don't think it is affecting my connection one way or another. I just unchecked the box in the DHCP options and the DNS servers in the router configuration are all set to 0.0.0.0 but since there is no checkmark to use DHCP I don't think it matters.
Correct me please if I am wrong on any of this.
**UPDATE**
Very nice article StoneCat. Very informative.
"It's All In The Reflexes."
- YeOldeStonecat
- SG VIP
- Posts: 51171
- Joined: Mon Jan 15, 2001 12:00 pm
- Location: Somewhere along the shoreline in New England
It's no problem at all leaving DHCP on if you do manual IP's on some workstations. Matter of fact, I recommend it. In case you screw something up while trying to setup static IP's, the newbie will have an easier time getting back to the router just by setting IP back to "obtain auto". Just realize that you want to assign IP's to the workstations that are outside of your DHCP range. Meaning, say your router does a DHCP range of 192.168.1.100 to 192.168.1.253....and the router itself takes 192.168.1.1...that leaves you with 192.168.1.2 to 192.168.1.99 to use for your fixed IP's. Also most routers will let you adjust the DHCP range anyways to whatever you like.
One of the reasons for this, is you can end up with conflicts if you assign a workstation an IP address that DHCP would normally hand out. Say that static IP worktstation has an IP of 192.168.1.103. And one day that workstation is turned off....then several other workstations that simply "obtain auto" boot up...first one getting 192.168.1.100, then 192.168.1.101, 102...the the 4th boots up and gets 103. Then later you boot up that fixed IP workstation that has 103...BAM..IP conflict. Yes someone is bound to answer "Well you can just exclude 103 from the DHCP handout list". I'll reply to that "Well why do a bandaide approach, why not do it right in the first place."
To your other questions...rebooting the router will not change the DNS servers, it may change your WAN IP address, ...an ISP will usually have the same DNS servers for a long time. Yes it can happen...it's happened to me once. You'll find suddenly your network cannot surf the internet, it cannot ping domain names, yet you may find it can ping IP addresses on the internet. If that happens, check your routers status tab...see what the DNS servers are. Most ISP's, especially bigger ones, will keep their DNS servers the same IP...and if they change them, they will often still alias the old DNS server IP's to the new ones. The larger ISP's usually realize they have many customers with fixed IP setups...that changing DNS all the time will screw them up.
You can also add your routers IP address as a 3rd DNS server..just in case the first two are no longer there, your computer will query the next one...which is the router, which will just forward the requests to whatever DNS servers it has on it's WAN side. I just prefer to bypass the router (why add another stop)..and go directly to the ISP's DNS servers.
One of the reasons for this, is you can end up with conflicts if you assign a workstation an IP address that DHCP would normally hand out. Say that static IP worktstation has an IP of 192.168.1.103. And one day that workstation is turned off....then several other workstations that simply "obtain auto" boot up...first one getting 192.168.1.100, then 192.168.1.101, 102...the the 4th boots up and gets 103. Then later you boot up that fixed IP workstation that has 103...BAM..IP conflict. Yes someone is bound to answer "Well you can just exclude 103 from the DHCP handout list". I'll reply to that "Well why do a bandaide approach, why not do it right in the first place."
To your other questions...rebooting the router will not change the DNS servers, it may change your WAN IP address, ...an ISP will usually have the same DNS servers for a long time. Yes it can happen...it's happened to me once. You'll find suddenly your network cannot surf the internet, it cannot ping domain names, yet you may find it can ping IP addresses on the internet. If that happens, check your routers status tab...see what the DNS servers are. Most ISP's, especially bigger ones, will keep their DNS servers the same IP...and if they change them, they will often still alias the old DNS server IP's to the new ones. The larger ISP's usually realize they have many customers with fixed IP setups...that changing DNS all the time will screw them up.
You can also add your routers IP address as a 3rd DNS server..just in case the first two are no longer there, your computer will query the next one...which is the router, which will just forward the requests to whatever DNS servers it has on it's WAN side. I just prefer to bypass the router (why add another stop)..and go directly to the ISP's DNS servers.
MORNING WOOD Lumber Company
Guinness for Strength!!!
Guinness for Strength!!!
- YeOldeStonecat
- SG VIP
- Posts: 51171
- Joined: Mon Jan 15, 2001 12:00 pm
- Location: Somewhere along the shoreline in New England