RFC1918 not allowed?

1

Are RFC1918 A records not allowed or ignored?

I created a subdomain.mydomain.com A record with something like 192.168.1.2

That was 5 days ago, but if a do a nslookup for subdomain.mydomain.com, I get no result from ns1.desec.io

So I was wondering if RFC1918 records are not allowed or simply ignored?
If yes, why? :slight_smile: And why is the WebGUI not hindering me doing so?

Reasoning for using it:
I have a webserver with a valid cert, done by ACME DNS challenge.
I will never use the 443 port from outside of my office, only locally.
But I will use some different port 9000 for an application on that machine that is reachable only by IPv6.

Since my Fritz.Box is pretty primitive and does not allow for firewall rules based on the IPv6 static source prefixes, I have to allow all incoming IPv6 traffic over that port. That is why I would like to not have a public AAAA record of that subdomain.

2

Hi KapernMagIchNicht,

Please send an email to support with the specific domain name so we can investigate.

Thanks,
Peter

2 Likes
3

Not only is Peter extremely fast and helpful, his first guess in the support mail is spot on!
The “issue” was fritz.box DNS rebind protection. Anyone else having this, go to

Heimnetz → Netzwerk → Netzwerkeinstellungen

scroll down to

DNS-Rebind-Schutz

and insert under Hostnamen-Ausnahmen your domain like subdomain.mydomain.com

Thanks again for the excellent support!

3 Likes