Raspberry PI as local name resolution

Let’s say that I have:

  1.   Home Internet router 
    
  2.   Raspberry pi
    
  3.   Laptop
    
  4.   Desktop
    

Let’s say that all three computers are connected directly to the Home Internet router.

My idea is the following:

  1.   Turn off DHCP server on Home internet router and set its IP address to 192.168.5.1
    
  2.   Set fixed IP for raspberry to 192.168.5.2
    
  3.   Install samba on raspberry with wins support = yes, name resolve order = wins lmhosts hosts bcast
    
  4.   Install DHCP server on raspberry for range 192.168.5.100 - 192.168.5.150, default gateway of 192.168.5.1, netbios-name-servers 192.168.5.2, domain-name-servers 192.168.5.1
    

I am expecting that when I turn on laptop or desktop, dhcp server on raspberry will provide to them an IP address from the pool, default gateway 192.168.5.1 and wins server 192.168.5.2.

As both of he computers are registered by wins server, I will have local name resolution by wins server, and if the wins server cannot resolve some name, dns name resolution from the Home Internet router will take over the request.

Will this setup provide the name resolution for the whole home network as well as for the Internet?

A there any potential problems?

How you are doing name resolution for your local network and outside world?

Regards

I’m not sure OSMC’s network manager connman is gonna easily allow you to integrate a dhcp server.

Why not let the router handle everything? Using 2 devices to do the work of one doesn’t make sense.

My internet router is very stupid. It can only provide IP addresses from its dhcp server address pool, and that is all it can do.
Its dhcp server doesn’t have an option to serve a fixed IP address.
How to solve home network (local) name resolution without introducing new device and/or service?

The simplest way would be to use fixed IP addresses and put them in the hosts file, and then replicate that host file to every local computer.

I would like to automate this process a bit.

Well name resolution is DNS and not DHCP topic (evenso they are very often the same as in DNSMASQ). So are you saying your router is even so dumb that it does not provide local DNS resolution? That would be really “dumb”. Which model is it?

If you really want to make the Pi the master in your network, maybe not to wise as it is not the most stable device, then look into DNSMASQ.

The router is Technicolor TC7200.20, on which I have non admin (user) access.

I believe that this is the proper url:
http://www.technicolor.com/en/solutions-services/connected-home/broadband-devices/cable-modems-gateways/tc7200-tc7300

Yes it doesn’t provide local DNS resolution.

For example, when I ssh to the my rpi1, I can ping it by using ping rpi1. From every other computer (regardless of the OS) on the same home network ping rpi1 doesn’t work.

Than as suggested look at setting up dnsmasq https://wiki.debian.org/HowTo/dnsmasq

Have you tried rpi1.local?

I did, but with no success.

It could work. Thanks.