[Dnsmasq-discuss] local domain (dyndns) not resolved

Bernd Prager bernd at prager.ws
Tue Aug 24 19:52:16 UTC 2021


On 8/23/2021 1:16 PM, Simon Kelley wrote:
>
> On 19/08/2021 16:56, Bernd Prager via Dnsmasq-discuss wrote:
>> Hi,
>>
>> I have some troubles in resolving my local domain.
>>
>> (I don't know if it is important, but I use DynDNS as DDNS service which
>> is synchronized by my router.)
>>
>> I can successfully resolve local boxes in my own network as well as
>> global domains:
>>
>>   $ dig loki +short
>> 192.168.1.104
>>
>> $ dig google.com +short
>> 142.250.72.142
>>
>> But my domain does not resolve:
>>
>>   $ dig prager.homeip.net
>>
>> ; <<>> DiG 9.16.1-Ubuntu <<>> prager.homeip.net
>> ;; global options: +cmd
>> ;; Got answer:
>> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7890
>> ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
>>
>> ;; OPT PSEUDOSECTION:
>> ; EDNS: version: 0, flags:; udp: 4096
>> ;; QUESTION SECTION:
>> ;prager.homeip.net.             IN      A
>>
>> ;; Query time: 0 msec
>> ;; SERVER: 192.168.1.2#53(192.168.1.2)
>> ;; WHEN: Thu Aug 19 08:50:03 PDT 2021
>> ;; MSG SIZE  rcvd: 46
>>
>> When I try this from a system outside my own network (e.g. AWS) it does
>> resolve:
>> <snip for dig output and dnsmasq config>
>> local=/prager.homeip.net/
> Is the guilty party. You're telling dnsmasq no to forward queries for
> prager.homeip.net to the upstream DNS server, and the upstream
> nameserver is where that data needs to come from.
>
>
> Simon.

Thank you so much Simon,

That solved it.

Cheers,
-- Bernd




More information about the Dnsmasq-discuss mailing list