Assigning Ip's question

[tsunami2311]

I am assuming

If I assign IP via the device (PC/laptop etc) Router list device as Static in the GUI ?( also manual putting DNS server) this will also override the bellow settings.

and

If I assign IP via the router Lan- DHCP Manually Assigned IP around the DHCP list and leave the device on automatic the router will list the device as manual in the gui? ( DNS servers on router for lan and wifi)

I been doing the first thing for better part of 20+ years on any thing wired, Is there any performance hit from the dns server done by router vs having them specified on the actual device or anything else If i just let router handle it all?

 

[sfx2000]

As long as your Static IP's are outside of the DHCP scope you should be fine....

In other words - if DHCP scope is 192.168.1-100 to 192.168.1.150, go above or below that range, staying in the same subnet...

My method is for servers and things that are always on, is not to rely on static IP reservations inside DHCP for the most part, but I have an HP OfficeJet printer that works better in DHCP land with certain services - and for that one device, I have a reservation in the DHCP config...

 

[ColinTaylor]

Is there any performance hit from the dns server done by router vs having them specified on the actual device or anything else If i just let router handle it all?

If you are assigning the same DNS server to the client in both cases then there isn't a difference in performance. The client ascertains what DNS server to use only when it is powered on.

 

[tsunami2311]

so from performance stand point it don't really mater, and Static vs Manual dont really matter either so long as static/manual ip are not within DHCP range.

I have general set my DHCP range to start after the wired and other device I choose to specify IP on which is usual (xxx.xxx.xx1 ~ xxx.xxx.xxx.xx8), I do some time forget to change the DHCP range when I update FW, cause as of late i been just manual put setting back, instead of using the NVRAM program but i never seen it cause issue

 

[ColinTaylor]

so from performance stand point it don't really mater, and Static vs Manual dont really matter either so long as static/manual ip are in DHCP range.

Correct, there's no performance difference.

If you set an IP address statically on the client it must be outside the DHCP range.
If you reserve an IP address in DHCP on the router (Manual Assignment) then it should be inside the DHCP range.

 

[tsunami2311]

well all this time I have had it set on the wired client and the manual ip assignment on the router to same ips and change my DCHP range to be out side of client/manual assigments..

Even when I just let router assign the manual ip and put clients on automatic it assigned the right ip to right device and they were not in DHCP range.

 

[ColinTaylor]

well all this time I have had it set on the wired client and the manual ip assignment on the router to same ips and change my DCHP range to be out side of client/manual assigments..

Even when I just let router assign the manual ip and put clients on automatic it assigned the right ip to right device and they were not in DHCP range.

Yes, you can do Manual Assignment that way and it will still work. It's just not the way ASUS expects you to do it. Different router manufacturers do it different ways.

The only thing you must do is assign static addresses (set on the client) outside the DHCP range.

 

[tsunami2311]

I got one last question in about DNS

IF the DNS server is specified On the router, does that mean the router handles the DNS requests on the router for the clients? or does it just tell the client to use the specified DNS server and client handles the request?

 

[ColinTaylor]

It can be either way depending on how you have setup DHCP.

The DHCP server can give the client its own IP address for DNS (i.e. 192.168.1.1) or it can give an external address (i.e. 8.8.8.8).

If the client uses the routers DNS server (192.168.1.1) it will normally be quicker because the router can cache upstream DNS queries.

 

[tsunami2311]

I not sure I following you

If setting from the client is better to specify 192.168.1.1 for DNS or 208.67.222.222 , 208.67.220.220?

When I set clients to Automatic , 208.67.222.222 , 208.67.220.220 ,192.168.1.1 are specified in that order for DNS set by the router.

Are you saying to better set it to 192.168.1.1 on client side?

 

[john9527]

I got one last question in about DNS

IF the DNS server is specified On the router, does that mean the router handles the DNS requests on the router for the clients? or does it just tell the client to use the specified DNS server and client handles the request?

Easy way to remember....
- If you specify servers on the WAN page, they will be used by dnsmasq on the router and the router address will be sent to the clients to be used as the DNS server
- If you specify servers on the LAN/DHCP Server page, those server addresses will be sent to the clients to be used as the DNS Servers, bypassing the router dnsmasq

Generally, it's better to use the first option so that the router can act as a cache for the DNS requests.

 

[tsunami2311]

So I should only be setting my DNS servers via WAN and leave DHCP DNS blank? and that make all clients use that DNS server regardless of wired/wireless? and make it all handled by router vs clients

 

[john9527]

So I should only be setting my DNS servers via WAN and leave DHCP DNS blank? and that make all clients use that DNS server regardless of wired/wireless? and make it all handled by router vs clients

That would be my recommendation for the general case and the way I run (I actually specify no addresses so that the router will automatically use my ISP DNS servers in dnsmasq). Then, if you look at the clients, they will show the router address as their only DNS server.

EDIT: One other thing. If you are using any scripts that rely on ipset domains, you have to use the WAN DNS server setup. The router dnsmasq must see the DNS requests in order to populate the ipsets.

 

[tsunami2311]

So If I do static ip on the clients the setup would look like

Connection-specific DNS Suffix:
Description: Realtek PCIe GBE Family Controller

DHCP Enabled: No
IPv4 Address: 192.168.1.2
IPv4 Subnet Mask: 255.255.255.0
IPv4 Default Gateway: 192.168.1.1
IPv4 DNS Server: 192.168.1.1
IPv4 WINS Server:
NetBIOS over Tcpip Enabled: No

 

[john9527]

So If I do static ip on the clients the setup would look like

Connection-specific DNS Suffix:
Description: Realtek PCIe GBE Family Controller

DHCP Enabled: No
IPv4 Address: 192.168.1.2
IPv4 Subnet Mask: 255.255.255.0
IPv4 Default Gateway: 192.168.1.1
IPv4 DNS Server: 192.168.1.1
IPv4 WINS Server:
NetBIOS over Tcpip Enabled: No

That looks right to me...

BTW, if you want, you can also enable the router as the WINS server on the USB/Server/Samba page.

 

[tsunami2311]

actual nvm with last question thank for the info

 

[RMerlin]

Using the router as the DNS for all the clients allows those clients to resolves LAN hostnames, in addition to having the router act as a local cache.

 

[tsunami2311]

So assing DNS in the WAN either auto or manual is recommend and as such 192.168.1.1 for dns server when doing static is what recommend which what the router will assign threw DHCP to anything done automatic, short of DNS also having DNS assigned via the DHCP tab in which case it would the 192.168.1.1 + the other DNS servers automaticl assigned and listed in the windows tcp/ip stats.

Thanks for all the help.