Hi everyone,

is it possible to make MT devices aware of a Domain Search List?

Context: I have a FW that acts as DHCP server and sends the local domain as default and also as Domain Search List via DHCP. It seems like the MT devices don't pick that information when configured as DHCP clients. As a result I can't ping all other devices in the local network just by their hostname (FQDN works fine).

Questions: Is there a way to make this work? And is it possible to set a FQDN on a MT device, not just an "identity"?

Thanks!

Why does everyone want to make RoS a Windows construct??

If you mean dyndns name, then MT can resolved these.

caveat: I have no idea what fqdn means or how to use it?

I have no idea what fqdn means or how to use it?

Fully Qualified Domain Name
https://en.wikipedia.org/wiki/Fully_qua ... omain_name

@ chaosphere64

Context: I have a FW that acts as DHCP server and sends the local domain as default and also as Domain Search List via DHCP. It seems like the MT devices don't pick that information when configured as DHCP clients. As a result I can't ping all other devices in the local network just by their hostname (FQDN works fine).

hmm, I'm not that deep in exploring dhcp-dns in routeros, and I don't know which DHCP-dns client software that MT used, but I think you have a good point

as for this,

Questions: Is there a way to make this work? And is it possible to set a FQDN on a MT device, not just an "identity"?

hmm, interesting. never tried that myself,
how about try to put the identity as ie. router1.example.org (and the same for the rest) - and then try to ping other devices hostname in the example.org domain - with and without dns server. see what is the results?

just a thought

Option 119 is the "domain-search" ISC-DHCP number/option-name with description for "Client Domain Search."