<html><head>
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
</head><body style="font-family: tt;" bgcolor="#FFFFFF" text="#000000"><div
style="font-family: tt;"><br>Hi Bert, Fred, List,<br><br>An anycasted
nameserver cluster could benefit from this. Initiating an axfr from
from a nameserver that is not topologically closest to the master just
results in a<br>failed axfr attempt since the answer does not come back
to the slave making the initial request.<br><br><br>Gary Shaver<br>Hurricane
Electric<br><blockquote style="border: 0px none;"
cite="mid:B8989C25-8F43-49EF-832C-D5DE9080572D@netherlabs.nl"
type="cite"><div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div
style="display:table;width:100%;border-top:1px solid
#EDEEF0;padding-top:5px"> <div
style="display:table-cell;white-space:nowrap;vertical-align:middle;width:100%">
<a moz-do-not-send="true" href="mailto:bert.hubert@netherlabs.nl"
style="color:#737F92
!important;padding-right:6px;font-weight:bold;text-decoration:none
!important;">bert hubert</a></div> <div
style="display:table-cell;white-space:nowrap;vertical-align:middle;">
<font color="#9FA2A5"><span style="padding-left:6px">July 5, 2012 3:00
PM</span></font></div></div></div><div
style="color:#888888;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody"><div><!----><br>Interesting.
The original use case was where the outside world would never be talking
to that master, or at least not taking the initiative to do so. So the
outside world would think the nproxy IP address was the slave, and
nproxy would then relay that to the real slave, which would reach out
over TCP to make it happen. I think some NAT trick is used to make sure
that the outgoing traffic appears as the address that was notified.<br><br>If
you want to have this integrated, what exactly is your use case? Better
protection for the hidden master? <br><br>Please don't get me wrong, I
get the impression what you want is reasonable, but I can't quite wrap
my head around your exact requirements.<br><br>Please let us know!<br><br>
Bert<br> PowerDNS<br><br>_______________________________________________<br>Pdns-users
mailing list<br><a class="moz-txt-link-abbreviated" href="mailto:Pdns-users@mailman.powerdns.com">Pdns-users@mailman.powerdns.com</a><br><a class="moz-txt-link-freetext" href="http://mailman.powerdns.com/mailman/listinfo/pdns-users">http://mailman.powerdns.com/mailman/listinfo/pdns-users</a><br><br><br>!DSPAM:4ff60e6d270271029916480!<br><br></div></div><div
style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div
style="display:table;width:100%;border-top:1px solid
#EDEEF0;padding-top:5px"> <div
style="display:table-cell;white-space:nowrap;vertical-align:middle;width:100%">
<a moz-do-not-send="true" href="mailto:rom@twister.dyndns.org"
style="color:#737F92
!important;padding-right:6px;font-weight:bold;text-decoration:none
!important;">Fred Wittekind</a></div> <div
style="display:table-cell;white-space:nowrap;vertical-align:middle;">
<font color="#9FA2A5"><span style="padding-left:6px">July 5, 2012
11:18 AM</span></font></div></div></div><div
style="color:#888888;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="content-type">
<font size="-1"><font face="Arial">I'm working on deploying pdns,
and we had intended to use native replication
(mysql-replication).<br>
<br>
Our idea was to have one master dns server that sits behind a
firewall, and our public facing servers replicate from it. This
works well for 90%+ of the domains we host. We do have a few we
have to slave from our clients though.<br>
<br>
My original plan was to have nproxy sit on the public facing
name servers to forward the notify to the master dns server
behind the firewall, the master then does the axfr from our
client's server, populates mysql with the new zone info, that
then replicates out to the public facing servers.<br>
<br>
Then I got this error when trying to start nproxy (IP address
censored):<br>
</font></font>nproxy: Fatal: Binding socket for incoming packets
to 'a.b.c.d:53': Address already in use <br>
<br>
Which of course makes sense after seeing it, pdns is already binding
to the same IP/port.<br>
<br>
So, my question is this... Can the functionality of nproxy be
rolled into pdns so that pdns itself can forward the notify to
another instance of pdns (on the master server), or can nproxy and
pdns be made to work on the same IP. I looked into trying to see
if I could get iptables to split out the notify messages to a
different destination IP so I could put nproxy on a different IP
than pdns, but, I didn't figure out a good (reliable) way to do
this.<br>
<br>
Any help would be appreciated.<br>
<br>
Fred Wittekind<br>
!DSPAM:4ff5da85151923326710967!
<div>_______________________________________________<br>Pdns-users
mailing list<br><a class="moz-txt-link-abbreviated" href="mailto:Pdns-users@mailman.powerdns.com">Pdns-users@mailman.powerdns.com</a><br><a class="moz-txt-link-freetext" href="http://mailman.powerdns.com/mailman/listinfo/pdns-users">http://mailman.powerdns.com/mailman/listinfo/pdns-users</a><br></div></div></blockquote><br></div></body></html>