Hi
I am relatively new to RouterOS, being using some RB750 and RB951 on some SOHO clients
Before mikrotik I used to deploy a dns server on my clients for helping clients resolve local resources, I use Windows server on general basis. Now on some clients is just not affordable to deploy win server or bind and I thought I could use routeros static dns feature but found a weird behavior with dns resolution when pushing domain name to my clients through dhcp option.
Let’s say I’m pushing mydomain.local as dns sufix through dhcp option in routeros (IP → DHCP Server → Networks → 192.168.88.0/24 → Domain), routeros device is set as dns server on the network and configure to act as dns forwarder to clients. Everything is working as expected except for a while but then dns resolution for internal resources get messed up
If I use nslookup to to make queries against routeros devices almost every internal resource gets resolved to address 127.0.0.1, this is consistent on routeros dns cache where i can see entries where return address is 127.0.0.1 even for resources that do not exist on the network, for example if I use nslookup to query for host “testhost” (even if no device exist with that name) then routeros anwsers the query with return address 127.0.0.1 and a entry is created in the cache for testhost.mydomain.local
Now, its clear that in using the domain option of DHCP server in the wrong way so I hope you can gave me some clarification
BTW to replicate this behavior you just need to take a fresh routeros (tested with 6.27) and put some domain name in IP → DHCP Server → Networks → 192.168.88.0/24 → Domain
to return to normal just clear that option and do a ip release then renew on client device
Kind Regards