I own a domain wedemeier.eu. Now i created some subdomains like home.wedemeier.eu or jupiter.wedemeier.eu. The first points to a subdomain of myfritz.net to dynamically resolve my dynamic IP address (DynDNS). The latter points to the local IP address 10.0.0.52.
When I enter the DNS server (1.1.1.1) in my Macs System configuration manually, everything works fine. But I have do this with every device in the network. Without the 1.1.1.1 my WIFI router works as the DNS server. And everything (google.com, cloudflare.com…) works well, but not the entries I mentioned above. What am I doing wrong? Am I missing some thing? I would expect, that the entries should be propagated to the public, so that everybody in the world can reach the ip addresses, without the need, to use 1.1.1.1?
Who can stick my nose in the correct direction?
Greetings from Berlin
That won’t be possible. The address in the RFC1918 range are not accessible from the public internet. They exist for use in private networks and the same subnets are in use in private networks all over the world. This makes it impossible for any public routers to know which one you are hoping to reach.
It looks like it does.
I found that while looking to see if you could run an authoritative internal DNS zone on your router. I didn’t find an answer to that question. I was looking for details on that possibility since it would be the easiest way to run your own internal zone in site. Even though I do, not everyone wants to stand up their own internal DNS infrastructure for home use.
@Cyb3r-Jak3: that was the blocker. I have to insert every domain, i want to point to such a local ip address. Now everything works as expected.
@epic.network What i meant, was not to reach the server behind the ip address, but to resolve the domain name to that local ip address. but thank you anyway to point that out. My own authoritative DNS server is way more, than i need. For me it is enough to use the 1.1.1.1 and now I know how it works in my private network. So thank you again
