|
|
|
There's something I've often questioned in my mind, so as I'm about to setup a new router with new ISP, I though it time to find out the answer. Things work for me with no probs but I would still like to understand this one thing.
When setting the TCP/IP properties in Vista, I set things manually so I can give each device on my network a fixed identity (I know I don't need to but hey, I prefer to for an unknown reason!). So I put the IP of each PC in, so 192.168.0.5, or whatever. Also as I've selected the manual option I put the router's IP and netmask in too. In Windows though you also have to then state the DNS IP's. This is where I'm confused, because aren't those settings just about your own local network, for which you wouldn't use a DNS server? In the router/modem settings you also put the DNS server IP's (at least in my current old modem you do), which I would have thought is what's used to obtain the IP of any addresses entered. So what are those IP's needed for in the Windows setup?
I'm sure there is something I'm missing so I'd be grateful for clarification please.
Geoff.
|
|
|
USually just the same IP address as you use for the gateway, i.e. routers IP address.
You can bypass this and specify the IP addresses for any DNS server on the internet
|
|
The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
|
|
|
|
What I don't understand though is why a DNS entry is needed on the PC setup. Is it even used or just ignored?
|
|
Register (or login) on our website and you will not see this ad.
|
|
|
If you've just got a modem (ADSL or dialup) rather than a router, the PC needs to get a DNS value from somewhere... the usual recommendation is to point it at the router, then if you need/want to change it at any time, you only have to do it in one place.
|
|
The author of the above post is a thinkbroadband moderator but it does not constitute an official statement on behalf of thinkbroadband.
|
|
|
Because it is the PC that needs to know where to go to resolve the domain name into an IP address, which is what is used to connect to the servers across the internet.
|
|
The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
|
|
|
|
Ok I'm understanding a little more - So the PC needs it, not the router or modem. So I'm not sure why the numbers are needed in the modem too? Or maybe they aren't, and are only there in case they aren't in the PC? LOL.
|
|
|
Yes, the PC needs to know, but can either get it in 1 of 2 ways :
- Directly from the external, e.g. your ISP's or OpenDNS's, DNSs, by putting these external DNSs in the PC. Then the ones in the router are irrelevant.
- Indirectly via the router, by putting the router's gateway, e.g. 192.168.0.1, in the PC and the external ones in the router.
|
|
|
Normally you let the router get its WAN DNS IP addresses automatically. A router will need them so
a) it can serve requests for DNS look ups from computers on the LAN
b) Do DNS lookups for itself, e.g. to resolve the domain name for the time service it uses to set its clock
|
|
The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
|
|
|
Yes, the PC needs to know, but can either get it in 1 of 2 ways :
- Directly from the external, e.g. your ISP's or OpenDNS's, DNSs, by putting these external DNSs in the PC. Then the ones in the router are irrelevant.
- Indirectly via the router, by putting the router's gateway, e.g. 192.168.0.1, in the PC and the external ones in the router.
After it's looked in the hosts file.
|
|
The author of the above post is a thinkbroadband moderator but it does not constitute an official statement on behalf of thinkbroadband.
|
|
|
Ok I understand far better now. Thanks Gentlemen for explaining it. I wish I'd asked years ago!
Geoff.
|
|
|
|
In addition to all the above you could actually use an alternative to manual config on each PC.
If you want a PC to always have the same IP then the router probably has an option to set an IP address statically for the PC. That way the PC can continue obtaining automatically but you can assign a particular address to a particular device. Netgear and thomson routers do this and any good router should.
It also means that if the DNS servers change you only have to update them on the router (and if it is set to pick them up automatically from the ISP you wouldn't even need to change there).
I use this method on my network and most PCs are statically assigned via the router without messing about with the config on each machine.
|
|
|
You can manually assign an IP and still use the router DNS settings by specifying the router IP as DNS as was already mentioned. That's what I do.
If you can't fix it with a hammer you've got an electrical problem.
|
|
|
|
Yes, but personally I prefer doing it at the router and not changing settings on the PCs. I was offering an alternative not saying that other ways weren't valid.
|
|
|
The part of your post I was taking issue with was...
"It also means that if the DNS servers change you only have to update them on the router"
...as it implies that you have to change every PC on the network if the IP is coded manually and that isn't so.
As you say both ways are perfectly valid. The only reason I do on the PC is because at least one router I've had either didn't offer the "always use this IP" functionality or buried it deeper than I looked.
If you can't fix it with a hammer you've got an electrical problem.
|
|
|
|
Ah, OK, missed that specific point - agreed.
|