On 05.05.18 09:52, Blason R wrote:
OK So wondering if I have master in cloud wanted to know which port should
I open for slave which is behind corporate firewall and if I set as below
then my slaves will start listening on port 2034? I am bit confused on
port
numbers for NOTIFY messages and NOTI
Absolutely that is TCP/53 required for Zone Xfer right?
On Sat, May 5, 2018 at 10:34 PM, Matus UHLAR - fantomas
wrote:
> On 05.05.18 09:52, Blason R wrote:
>
>> OK So wondering if I have master in cloud wanted to know which port should
>> I open for slave which is behind corporate firewall and i
On 05.05.18 09:52, Blason R wrote:
OK So wondering if I have master in cloud wanted to know which port should
I open for slave which is behind corporate firewall and if I set as below
then my slaves will start listening on port 2034? I am bit confused on port
numbers for NOTIFY messages and NOTIF
OK So wondering if I have master in cloud wanted to know which port should
I open for slave which is behind corporate firewall and if I set as below
then my slaves will start listening on port 2034? I am bit confused on port
numbers for NOTIFY messages and NOTIFY-UPDATED [i.e. AXFR/IXFR]
also-noti
This gets much more involved the further downstream you go.
For example, when a downstream slave (true or stealth) provides transfers
to a further downstream slave (true or stealth), the notify options can get
a bit messy.
Bottom line is it requires some detailed analysis and probably some
pictur
On 04.05.18 06:21, Bob McDonald wrote:
This is my understanding of how Current (ver. 9.8 and above) ISC Bind
works. It may or may not apply to older versions of ISC Bind and/or DNS
resolver programs from other sources. This is only MY understanding. You
are welcome to disagree and point out the f
This is my understanding of how Current (ver. 9.8 and above) ISC Bind
works. It may or may not apply to older versions of ISC Bind and/or DNS
resolver programs from other sources. This is only MY understanding. You
are welcome to disagree and point out the folly of my understanding.
There are seve
On 04/05/2018 10:02, Blason R wrote:
> Ok -My question was about port number if not explicitly defined then it
> sends update on port TCP/53
No. BIND sends NOTIFY messages over UDP to port 53 by default. You can
change the port, but not the transport.
Regards,
Anand
_
Ok -My question was about port number if not explicitly defined then it
sends update on port TCP/53
On Fri, May 4, 2018, 12:15 PM Dns Admin wrote:
> Hi Blason,
>
> My understanding is that if there is no "notify no;" statement, then bind
> will send notifies to all name servers for a given zone.
Hi Blason,
My understanding is that if there is no "notify no;" statement, then
bind will send notifies to all name servers for a given zone.
Also notify pertains too the notification of name servers not included
in zone data.
Kind Regards Peter
On 04/05/2018 05:51, Blason R wrote:
Hi,
Hi,
So I was playing with these two statements and wanted to know something on
also-notify.
also-notify by default will update slaves about delta changes on port
TCP/53 if not explicitly set right?
e.g.
also-notify {10.0.1.2; "notify-them" port 2034;};
__
11 matches
Mail list logo
