<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 07/05/2025 15:16, Nacho Oppo wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAABgbgUQrLd=cRrPTNPtLvkfAy6v2MTNx385LfPUNHvWUWpnxg@mail.gmail.com">
<p class="gmail-">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:</p>
<ul>
<li class="gmail-">
<p class="gmail-">I have a server <strong>A</strong> with IP
address <strong>dirip-A</strong>. When this server connects
to <code><a href="http://servidor1.dominio.com">servidor1.dominio.com</a></code>,
it must resolve to a specific point-to-point IP: <strong>diripservidor1-serverA</strong>.</p>
</li>
<li class="gmail-">
<p class="gmail-">I also have a server <strong>B</strong>
with IP address <strong>dirip-B</strong>. When this one
connects to <code><a href="http://servidor1.dominio.com">servidor1.dominio.com</a></code>,
it must resolve to a <em>different</em> IP: <strong>diripservidor1-serverB</strong>.</p>
</li>
</ul>
<p class="gmail-">So, depending on the source of the DNS query,
the same hostname (<code><a href="http://servidor1.dominio.com">servidor1.dominio.com</a></code>)
must resolve to a different IP address.</p>
</blockquote>
<p>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.<br>
</p>
<p>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.<br>
</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:CAABgbgUQrLd=cRrPTNPtLvkfAy6v2MTNx385LfPUNHvWUWpnxg@mail.gmail.com">
<p class="gmail-">However, the client also has another public
server: <code><a href="http://servidorpublico.dominio.com">servidorpublico.dominio.com</a></code>,
and this one <strong>must be resolved via an external DNS
resolver</strong> (for example, Google DNS at 8.8.8.8), as it
is not managed internally.</p>
</blockquote>
<p>But why does servidor1 have to have a name directly under
dominio.com ? Can't it be</p>
<p>servidor1.int.dominio.com<br>
</p>
<p>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.<br>
</p>
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.
</body>
</html>