Redirecting the IP address to name

Hello.

I have created 3 bridges.
I set them ports (Bridge → Ports): Ether11 for Bridge1, Ether12 for Bridge2 and Ether13 for Bridge3.
And I made DHCP Setup for each one (IP → DHCP Server): 192.168.11.0/24, 192.168.12.0/24, 192.168.13.0/24.

Everything works great but I want to do redirecting a specific IP address.
Let it be 192.168.12.120 - I can ping this IP adress from computer with IP adress 192.168.11.120.
Now I need to achieve the same by pinging host-name, for example: ping my_computer, so summarizing:
“ping my_computer” should be the same action as “ping 192.168.12.120”

I thought I can achieve it by a command:

/ip dns static add address=192.168.12.120 name=my_computer

but I was wrong, still searching for a solution.

Thank you.

Use “pc.local” as name instead of “my_computer” and try again

Indeed, after adding

my_computer.local

everything works.
Is it possible to achieve this without

.local

?

IMHO, no, you need both, hostname and domain name.
Something about this problem here
https://superuser.com/questions/1211416/static-dns-records-set-in-router-seem-to-be-ignored

In C:\Windows\System32\drivers\etc there’s a file

hosts

.
I can add

192.168.12.120 my_computer

to achieve the intended goal, although I would prefer to achieve it from the Mikrotik level

Why you dont want the “.local” ???

Because I have disc mapped to a name

my_computer

.

If PCs get IP setup ftom DHCP server, then set domain name to “local” … I guess ROS won’t complain if you execute /ip dhcp-server network set [ find ] domain=“local” … You have to force PCs to re-lease DHCP settings (unplugging network cable or fisabling wireless interface gor 10 seconds will do the trick).

Mkx if he does it that way then “.local” can be skipped ?

Domain name property tells clients to append configured value to host names if they don’t appear to be FQDN. If, for example, domain name is set to “example.com” and user enters “host” (e.g. ping host), then client will ask DNS server to resolve “host.example.com”. I’m not sure about how many dots have to be in particular part for client to consider it regular and valid … e.g. if user typed ping host.subdomain, would client ask DNS server to resolve host.subdomain.example.com or host.subdomain? I’m sure @4drik will test and tell us :wink:

Mkx that is great… i had neved used the domain field inside the dhcp server…