Just to clarify, the configuration I was referring to was supposed to have a
master and slave DNS server for private zones (only two DNS servers) but
something happened during/after upgrade and they both showed master (actually
rndc -s 127.0.0.1 -r zonestatus ) reported master and the other pri
Hi Greg.
So somebody referenced this KB article because presumably it was
tangentially relevant, but I don't know that the OP is working with
standby infrastructure (good question!). All they say is that after an
upgrade all servers were masters.
The amount of direct relevance of the article
Hi Fred.
No, the sense is correct.
Imagine you have a server with a secondary zone of (say) "example.com",
which transfers data for that zone from a primary somewhere. The secondary
loads data received during a zone transfer straight into memory and uses it.
It is optional for the secondary to also
Spamhaus’s servers are sending back responses that do not answer the question.
Named is doing QNAME minimisation using NS queries and rather than the servers
sending back a NODATA response for the empty non-terminal names they are
sending back the NS records for the top of the zone.
I suggest
Hi,
I have a fedora38 server with bind-9.18.17 and receiving the following log
entries for virtually every query (where "mykey" is my registered spamhaus
DQS key):
07-Sep-2023 14:30:13.608 lame-servers: FORMERR resolving '
mykey.hbl.dq.spamhaus.net/NS/IN': 66.42.94.100#53
07-Sep-2023 14:30:13.625
Re-reading the KB article referenced below...
On Tue, 5 Sep 2023, Leroy Tennison via bind-users wrote:
[...] I'm assuming i can use
https://kb.isc.org/docs/managing-manual-multi-master to "demote" one of
them but is there anything to look for concerning possible
inconsistencies and how do I
6 matches
Mail list logo
