Custom DNS' dynamic setup not resolving

1

I have a MIAB setup that uses the custom DNS. I have a few subdomains that require the dynamic DNS feature that comes with MIAB’s custom domains. For example, curl -X PUT --user me@box.example.com:yourpassword https://box.example.com/admin/dns/custom/raspberrypi.mydomain.com updates the IP addresses and I can see the IP of raspberrypi.mydomain.com in the admin area.

However, when I dig raspberrypi.mydomain.com, I have NXDOMAIN. When I ping it, I get “Name or service not known”.

This device is not behind a NAT as I am testing.
Do anyone have an idea what’s going wrong? Thanks for your help :smile:

2

You might be getting an old cached DNS answer. The only fix for that is to wait until the caches clear - hours, but not days - the joys of DNS :roll_eyes:

You can force dig to get the answer from your box:

dig @mydomain.com raspberrypi.mydomain.com

3

Thanks.Turns out the issue wasn’t with MIAB at all or caching, dynamic DNS was working. The problem was delegation. The parent domain (mydomain.com) did not complete the delegation of raspberrypi.mydomain.com to my box’s nameservers, so it never resolved publicly. Once the domain owner added the proper NS records pointing to my MIAB, everything worked right away.