Router can't find an address when the zone is added into Technitium

[streeyt]

Hi. This is almost certainly me misunderstanding something rather than an issue with Technitium.

My dumb ISP router that I'm forced to use due to its proprietary VOIP, doesn't let me configure a DNS server in its DHCP configuration, so DHCP clients are given the router address of 192.168.1.1 as their "DNS server" . Not a problem, I've configured my local Technitium DNS as the router's DNS server (where a public DNS like 1.1.1.1 would normally be).

This works fine. All my LAN clients have the router IP as their DNS, which hands off resolution to my local Technitium server which in turn responds recursively via 1.1.1.1 for all public addresses that clients need.

However. If I add a zone into my Technitium DNS and add some records, none of my LAN clients can resolve them UNLESS I manually configure the client to explicitly use the IP of the Technitium server as their DNS.

i.e; when a LAN client uses the router as its "DNS" (which then contacts Technitium) records in Technitium zones can't be found. But if I explicitly set the Technitium address as the DNS server on my LAN clients, records in Technitium CAN be found. It's as it the router is refusing to work with my local zones. It works fine using Technitium to lookup external public addresses.

Manually setting DNS on clients isn't really an option as many of them are Android where, depending on brand, setting DNS can be tricky.

Any suggestions would be really welcome please.

Thanks

[ShreyasZare]

Thanks for the post. Does your router allow disabling DHCP Server? If yes then just disable it and use the DHCP Server that is available with the DNS server. This will fix all issues you have.