Re: Zone Transfers Being Refused

2023-07-31 Thread duluxoz
feel obligated to reply outside your normal working hours. On 31. 7. 2023, at 9:51, duluxoz wrote: Hi Ondřej, Sorry, force of habit (re: "example.com"). External Secondary DNS Server (ns1.mjb-co.com): ~~~ acl "bogusnets" { !"internal_hosts"; 0.0.0.0/8;

Re: Zone Transfers Being Refused

2023-07-31 Thread duluxoz
????????"; }; server 192.168.1.10/32 {     keys "ddns-key"; }; server 192.168.1.20/32 {     keys "ddns-key"; }; server 192.168.2.10/32 {     keys "ddns-key"; }; server 192.168.2.11/32

Zone Transfers Being Refused

2023-07-31 Thread duluxoz
Hi All, Hoping someone can help with this: I've got a primary dns server on an internal network (192.168.2.10/24) and an external secondary dns server on the dmz network (192.168.1.10/24). The gateway for each (ie the router) is 192.168.x.1. The external domain is dynamic, with dnssec set up

Re: Requesting Update-Policy Statements Sanity Check, Please

2023-02-04 Thread duluxoz
Thanks Mark - that was the issue :-) I really, really appreciate the help Cheers Dulux-Oz On 04/02/2023 23:21, Mark Andrews wrote: Add DHCID to the list of record types permitted to be updated by the DHCP server. -- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe fro

Re: Requesting Update-Policy Statements Sanity Check, Please

2023-02-04 Thread duluxoz
t;name": "1.168.192.IN-ADDR.ARPA.",     "key-name": "update.key",     "dns-servers": [{"ip-address": "192.168.2.3"}]     },{     "name": "2.168.192.IN-ADDR.ARPA.",

Requesting Update-Policy Statements Sanity Check, Please

2023-02-02 Thread duluxoz
Hi All, I'm pretty new to configuring Bind and so it would be great if someone(s) could just check my code re: the update-policy zone command(s) below - thanks in advance. For the first zone (a regular internal forward-lookup zone) I'd like to be able to update (from Kea via ddns) the zone w

lame-servers: info: no valid RRSIG resolving

2023-01-26 Thread duluxoz
Hi All, Sorry for asking what is almost certainly a "noob" question, but I'm seeing a lot of "lame-servers: info: no valid RRSIG resolving './NS/IN':" messages in our auth_servers.log for the DNS Root Servers' IPv4 addresses. Is this normal, or do we have an issue that we need to resolve. T