The RFC for Name Servers state that one hostname can only point to one IP qddress.
A round robin server have a script that continuously update the entries, but it is really a patch solution for a DNS service, because DNS records are allowed to be cached in the RFC, so there is no guarantee that you DNS based round robin works.
Many ISP DNS resolvers also refuse to accept low TTL values, so everything under 2 hours are a risk of failing.
Which rfc is that?
I think that Ubiquiti does use DNSMasq. The problem is not the DNS server itself but updating the data, which is why I rely on DHCP and don’t modify the DNS capabilities. It works with everything … except for the MQTT broker address. May be an HA bug in failing to use the DNS? If you know where to find the source code, i can look.
And yes, DHCP seems to be able to have duplicate records for IP and MAC, but I haven’t researched it.
ISP … another conversation but what’s in my house stays in my house and I maintain my own zone files externally.
Brother nodes may not have the same label, although the same label can be used
for nodes which are not brothers.
I’m not a DNS expert, so I may be off base, but I thought you could have multiple A records for a given Name (the RFC1034 shows an example), and DNS load-balancers picks one of the A records to respond to.
You are actually right.
Seems a bit contradicting though, but the DNS protocol was purposely made vague by the authors, so it could flex to the situation. I guess this is a grey area and due to the vagueness only the specific implementation knows how to adopt to the presence of multiple records for same node.
I believe that statement is referring to the text name, not the record details. E.G.
pony.example.com
and
pony.store.example.com
are acceptable separate domain names because they are different levels of the tree structure.
Yeah, but then pony.example.com and pony.example.com would not be acceptable and they seems to be according to wmakers reference.