On the web server make an entry in the hosts file with the domain name as 127.0.0.1 as address.
Are you talking about something else than what I mentioned in my last sentence in the OP?
It may not seem like a router issue, but the router is the only thing that's changed recently, and it was working before, therefore I am led to that conclusion.
It may be wrong, but I don't even know how to debug the issue, so pointers there will also be welcome.
Joined: 13 Aug 2013 Posts: 6870 Location: Romerike, Norway
Posted: Mon Jul 24, 2017 6:33 Post subject:
Didn't use of a hosts file resolve it?
Are all local clients using the router as dns server?
You can add a dnsmasq option on the router so the domain name is resolving to the local address for local machines instead of the public wan address.
Quote:
A, --address=/<domain>[/<domain>...]/[<ipaddr>]
Specify an IP address to return for any host in the given domains. Queries in the domains are never forwarded and always replied to with the specified IP address which may be IPv4 or IPv6. To give both IPv4 and IPv6 addresses for a domain, use repeated -A flags. To include multiple IP addresses for a single query, use --addn-hosts=<path> instead. Note that /etc/hosts and DHCP leases override this for individual names. A common use of this is to redirect the entire doubleclick.net domain to some friendly local web server to avoid banner ads. The domain specification works in the same was as for --server, with the additional facility that /#/ matches any domain. Thus --address=/#/1.2.3.4 will always return 1.2.3.4 for any query not answered from /etc/hosts or DHCP and not sent to an upstream nameserver by a more specific --server directive. As for --server, one or more domains with no address returns a no-such-domain answer, so --address=/example.com/ is equivalent to --server=/example.com/ and returns NXDOMAIN for example.com and all its subdomains.
