Infinite DName-Resolution #619
-
So, here's my setup: This way I hoped, that I could resolve any DHCP hostname in dynamic.host.tld through both hostname.host.tld or hostname.domain.tld, without needing to create CName records for each and every dynamic host. This would also allow adding records to host.tld, which are automatically resolveable on domain.tld. The issue is, that the Dns Server (11.1.1) seems to resolve for the shortest zone name available. A For these records:
Is this wrong expectation on my side, or wrong implementation in the Dns server? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Thanks for that post. With DNAME, the entire sub-tree of the domain gets delegated to the configured domain name in the record. Which means you cannot have anything under that name in the I tried the same config on my test setup and used the built-in DNS Client to test and it is resolving as expected. It seems that I will add some kind of validation for this to prevent such config scenarios that can cause issues. |
Beta Was this translation helpful? Give feedback.
Thanks for that post. With DNAME, the entire sub-tree of the domain gets delegated to the configured domain name in the record. Which means you cannot have anything under that name in the
host.tld
zone. So, the config where you are trying to do a DNAME for a subdomain name wont work. The other DNAME record that you have in thedomain.tld
is fine though.I tried the same config on my test setup and used the built-in DNS Client to test and it is resolving as expected. It seems that
dig
is capable of using DNAME record which is causing it to synthesize the infinite CNAME records on its own. The DNS Client built into the DNS server is not capable of processing DNAME so it ignores them and jus…