Dear Roberto,
It is hard to say without seeing the named.conf.local, but are you sure
you have incremented the serial?
Kind regards,
Mirsad
On 12/13/2021 7:24 PM, Roberto Carna wrote:
Dear all, I have BIND 9 and Webmin. One master and one slave using zne
ransfer with TSIG
Everything was Ok
Dear all, I have BIND 9 and Webmin. One master and one slave using zne
ransfer with TSIG
Everything was Ok till today.
When I add or modify a record for zone1.com in the master, the record
in the slave is up to date.
But when I add or modify a record for zone2.com in the master, the
record is
If you update your resolver to 9.16, I think you can do exactly what you
want with the "validate-execpt" option.
{rolls eyes} been there. done that. for exactly the same reason :/
--
--
Do things because you should, not just because you can.
John Thurston907-465-8591
Hello Crist,
This problem you have spotted in your troubleshooting was fixed by the
uplevel sysadmins.
Now I have added bjesomar.srce.hr as the secondary (I don't like the
expressions "master" and "slave") NS for 193.198.186.192/27.
It appears to work. There seem to be more DHCP problems
Hello,
I need to internaly forward domain to different nameserver:
zone "x.local" {
type forward;
forward only;
forwarders {
100.1.2.3;
};
};
when I do this with bind 9.11 (debian 10), I get these messages:
Dec 13 14:26:55 mail named[13112]:
Hello Crist,
P.S.
Thank you again for your time and effort. Your expertise is very much
appreciated. The thingy appears to work snappy !
It is true that domac.alu.hr recognizes only itself as the authoritative
NS for 193.198.186.192/27 zone.
I had to comment out the bjesomar.srce.hr
Hello Crist,
The good news is that it seems that the dynamic DDNS update from DHCP
works!
See here a snap from /var/log/syslog:
Dec 13 07:36:20 domac dhcpd[26031]: DHCPDISCOVER from 1c:66:6d:90:0b:f7
(ALU-ZAG-14) via 193.198.186.193
Dec 13 07:36:20 domac dhcpd[26031]: DHCPOFFER on
7 matches
Mail list logo
