Jump to content
RESET Forums (homeservershow.com)

Network Setup – Router LAN – DHCP Settings


doliveira
 Share

Recommended Posts

Hi,
 
I’m setting up my small office network and on my server I will use the “Windows Server 2012 R2 Essentials”.
 
As router I use the TP-Link TL-ER5120 and im in the phase of setting up the router and I don’t know if I must fill the fields “Default Gateway” and “Default Domain” as you can see on the image I have attached to this thread.
 
On my network it will be the server to handle the DNS, but it will be the Router to handle the DHCP.
 
So can someone please look at the image and tell me if I should leave that 2 fields in blank or should o fill them.
 
I was thinking on putting my domain name in the “Default Domain” as: mydomain.local. Should I do that?
 
Feel free to share you advice.
 
Thanks

router-settings-2.jpg

Edited by doliveira
Link to comment
Share on other sites

Any paticular reason you are not going to dish DHCP out from the server??

 

By default the gateway should be the router address (I am assuming that is the internet connection) unless you are utilising a transparent proxy but given your question I would think not.

 

Domain name is dependent on how your setting up the rest of the network, are you setting it up on a domain controller or not?

 

honestly I would utilise the DHCP service on the server, it is will give you more flexibility long term

Link to comment
Share on other sites

Any paticular reason you are not going to dish DHCP out from the server??

 

By default the gateway should be the router address (I am assuming that is the internet connection) unless you are utilising a transparent proxy but given your question I would think not.

 

Domain name is dependent on how your setting up the rest of the network, are you setting it up on a domain controller or not?

 

honestly I would utilise the DHCP service on the server, it is will give you more flexibility long term

 

Hi @ShadoePeo,

 

The only reason DHCP is being managed by the router instead of the server is because i have a small office and the server is nor turned on 24x7. To save electric bill i only turn on the server when i need. So this was why i have put DHCP to be managed by the router.

 

I was afraid that with the server turn off, i could not connect clients and friends compyters when they come on to my office with the server turned off. Or its possible and i should have DHCP managed and working on the server instead of having it on the router?

 

Please advise me.

 

Thanks

Link to comment
Share on other sites

Leave DHCP on the router for the exact reason you explained.

 

Hi jmwills,

 

Just to clarify: 

 

If my server was turned on always 24x7, the best thing is to have the DHCP running on the server. But because my server is not turned on 24x7, i'm firced to have thye DHCP running on the router, correct?

 

Thanks

Link to comment
Share on other sites

Either way, I'd run DHCP on the router.

 

Hi Can you tell me the pros vs cons of having the DHCP running on the router instead of in the server?

 

Thanks

Link to comment
Share on other sites

The only reason DHCP is being managed by the router instead of the server is because i have a small office and the server is nor turned on 24x7. To save electric bill i only turn on the server when i need. So this was why i have put DHCP to be managed by the router.

 

There's your reason for leaving it on the router.  Besides, if you have clients over, the only way for them to connect, if you leave it on the server, would be through a wired connection as the server would have no wireless capabilities.

Link to comment
Share on other sites

The DHCP service on the server is eminantly more configurable than the one on the DHCP server depending on what you are going to do long term, more than 2 DNS servers, Boot options, automatic proxy configuration (WPAD, although this is almost exclusively I.E., WebKit based browsers and Firefox tend to use DNS based AutoProxy) Time Server assignment, multiple search domains, all these are possible with the DHCP service in Windows and it is most likely not able to be done on the router.

 

But if you are going to turn the server off the router is the best option. However you stated above that you were going to run DNS on the server and DHCP on the router, this will cause issues DNS resolution issues unless the server is on, if you are going to do this do it as a secondary at least then you will have an external primary. However if you are utilising internal DNS names through a secondary zone assignment then you may return the wrong DNS resolution if there is an equivalent name somewhere in the wild on the primary (i.e. help.me.com external exists and points to 222.222.222.222 but internally you want it to go to 172.16.1.12 then if you do not use your server as primary the external resolution is likely to be sent through not the internal as the external is primary, using the internal on the server as primary you are going to get delay on DNS resolution when the server is off as the machine will try the primary first, and then falls back to the secondary, yes I know this is a gross simplification)

 

In your case I would be putting the router in as Default gateway (192.168.0.1 in your case) and whatever domain you are utilising for internal resolution in the Default Domain box (as I am assuming this is going to be the "search domain" option in DHCP), or blank if you are not utilising one.

Link to comment
Share on other sites

But if you are going to turn the server off the router is the best option. However you stated above that you were going to run DNS on the server and DHCP on the router, this will cause issues DNS resolution issues unless the server is on, if you are going to do this do it as a secondary at least then you will have an external primary. However if you are utilising internal DNS names through a secondary zone assignment then you may return the wrong DNS resolution if there is an equivalent name somewhere in the wild on the primary (i.e. help.me.com external exists and points to 222.222.222.222 but internally you want it to go to 172.16.1.12 then if you do not use your server as primary the external resolution is likely to be sent through not the internal as the external is primary, using the internal on the server as primary you are going to get delay on DNS resolution when the server is off as the machine will try the primary first, and then falls back to the secondary, yes I know this is a gross simplification)

 

In your case I would be putting the router in as Default gateway (192.168.0.1 in your case) and whatever domain you are utilising for internal resolution in the Default Domain box (as I am assuming this is going to be the "search domain" option in DHCP), or blank if you are not utilising one.

 

Hi ShadowPeo,

 

Thanks for your help and advices. As said before i will have DHCP running on the Router and DNS running on the Server, only because my server is not turned on 24x7.

 

So i will try to use the following settings on my router LAN > DHCP settings:

 

Default Gateway: 192.168.0.1  (this is my router IP)

Default Domain: myoffice.local (this is my windows network domain name)

Primary DNS: 192.168.0.10 (this is my server IP)

Secondary DNS: 192.168.0.1 (this is my router IP)

 

I think that settings up this way, when my server in turned ON all my office computers will use the server as DNS and when the server is turned OFF all the my office computers will use the router as DNS.

 

So what do you guy's think of the settings i listed above?

 

Thanks

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...