On 07/05/2025 15:16, Nacho Oppo wrote:
I believe I may not have explained the scenario clearly in my previous
messages. Let me try to clarify it with a simplified example, which
might better illustrate the situation:
*
I have a server *A* with IP address *dirip-A*. When this server
connects to |servidor1.dominio.com
<http://servidor1.dominio.com>|, it must resolve to a specific
point-to-point IP: *diripservidor1-serverA*.
*
I also have a server *B* with IP address *dirip-B*. When this one
connects to |servidor1.dominio.com
<http://servidor1.dominio.com>|, it must resolve to a /different/
IP: *diripservidor1-serverB*.
So, depending on the source of the DNS query, the same hostname
(|servidor1.dominio.com <http://servidor1.dominio.com>|) must resolve
to a different IP address.
This is typically known as DNS "views". Some DNS servers, like BIND,
support this concept natively, serving different zones based on the
client IP address.
If that's the entire extent of the problem, and the data is static, you
could just put entries in /etc/hosts on those servers. I'm presuming
it's not.
However, the client also has another public server:
|servidorpublico.dominio.com <http://servidorpublico.dominio.com>|,
and this one *must be resolved via an external DNS resolver* (for
example, Google DNS at 8.8.8.8), as it is not managed internally.
But why does servidor1 have to have a name directly under dominio.com ?
Can't it be
servidor1.int.dominio.com
and then you can do your DNS views magic only for the int.dominio.com
domain? This eliminates the need to have the fallback to public DNS, and
servidorpublico.dominio.com is unaffected.
This feels like an XY problem. "How do I do this really bad thing with
PowerDNS, in order to achieve Y?" when we don't know what Y actually is._______________________________________________
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users
