Notify...
Michael Kohne
mhkohne at discordia.org
Fri Jul 27 11:45:03 UTC 2001
Is it normal for secondary name servers to send NOTIFY when they update? I
thought only the primary should do that.
A quick perusal of RFC 1966, especially section 3.10 seems to indicate that
I'm correct - is there something I should be doing in order to make sure
that the secondaries don't do this?
(the domain in question is sonictech.com)
sample of the message from my log files:
Jul 26 11:31:39 ultra named[21233]: rcvd NOTIFY(sonictech.com, IN, SOA)
from [207.8.186.11].1037
Jul 26 11:31:39 ultra named[21233]: NOTIFY(SOA) for non-secondary name
(sonictech.com), from [207.8.186.11].1037
Jul 26 11:46:22 ultra named[21233]: rcvd NOTIFY(sonictech.com, IN, SOA)
from [207.8.186.2].1714
Jul 26 11:46:22 ultra named[21233]: NOTIFY(SOA) for non-secondary name
(sonictech.com), from [207.8.186.2].1714
Note that 207.8.186.2 is one of the known slave name servers. The other is
unknown to me, but clearly owned by my ISP - I assume it's one of their
name servers that I know nothing about.
Also note that ns1.sonictech.com and ns2.sonictech.com are two separate
interfaces (DSL & 56K modem) on the same computer, which is the primary DNS
server for sonictech.com.
I'm primarily concerned with figuring out whether this is correct or not -
if not, I'll try to get them to fix it, if so, then I just want to know
what's up.
Thanks!
Michael Kohne mhkohne at discordia.org
3000 lbs of wood, 300 foot per minute - DO NOT get in the way.
More information about the bind-users
mailing list