Hello,
For anyone interested I found a solution to this problem. Here is a link to a thread at RaspberryPi.org where all the gory details are given with great verbosity.
In summary:
- I was trying to access the NextCloudPi on a Pi on the same LAN as my Windows 7 laptop using a domain name that was resolving to the external ip address of my router rather than the local ip address of the pi running NCP and dnsmasq.
- I think this was because my router isn’t able to do NAT Loopback at all.
- dnsmasq was set up correctly all along…
- Such is my current understanding: The reason was because Windows 7 prefers IPv6 over IPv4. I changed the Primary DNS server in my router to be the local IP of my Pi but nevertheless the ipconfig /all command in Windows showed it was (likely?) sending all requests through my router to an IPv6 DNS server with preference over the dnsmasq IPv4 DNS server so requests were never going to my Pi, which has dnsmasq running on it, where they would have been redirected by dnsmasq to the local ip of my Pi.
- One solution was to turn off IPv6 altogether in the router and this did solve the problem.
- Another solution was to switch the IPv6 addressing type in my router to SLAAC… I don’t know why this works it just does.
- I am thinking of giving my Pi a static IPv6 address because dnsmasq can be configured to be an IPv6 DNS server… just to see if it will then play nice with my router under IPv6 (at least on my LAN).
Thank you to everyone who helped me,
Flex