Hi Nick
Would be helpfull to get more infos from you. Like the exacht record you
tried to add, the exact command you tried and the error you got.
Regards
Matthias
On 08/12/2022 02:15, Nick Urbanik via Pdns-users wrote:
Dear Folks,
I am working with DNSEC and in my lab setup I need to add
On 08/12/2022 02.15, Nick Urbanik via Pdns-users wrote:
I am working with DNSEC and in my lab setup I need to add a DS record
to my parent domain, and don't see how to do that.
What do you consider your domain and your parent domain in your setup?
If your domain is example.com, your parent d
Heh, totally missed the error. duh. Thanks for pointing it out. I’ll check out
the hairpinning on the nat. didn’t even think of that.
Sent from my iPhone
> On Dec 7, 2022, at 3:18 PM, Brian Candler wrote:
>
> On 07/12/2022 18:47, Curtis Maurand via Pdns-users wrote:
>> dig doesn't return an
Dear Folks,
I am working with DNSEC and in my lab setup I need to add a DS record to my
parent domain, and don't see how to do that.
I am using PowerDNS version 4.7.2 on Fedora 37 with a BIND backend, using
sqlite using the command:
pdnsutil create-bind-db...
I have tried adding the DS record to
On 07/12/2022 18:47, Curtis Maurand via Pdns-users wrote:
dig doesn't return an error
...
root@sirius:~# dig sirius.xyonet.com
; <<>> DiG 9.16.33-Debian <<>> sirius.xyonet.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 10323
To be clear: SERVF
On Wed, Dec 7, 2022, at 13:47, Curtis Maurand via Pdns-users wrote:
>
> I just added to the recursor.conf forward-zones=xyonet.com=192.168.100.30 and
> that worked. I would now call this solved.
>
The most likely cause is that your router/firewall is not configured properly
for 'hairpin NAT'
Op 7 dec. 2022 om 19:47 heeft Curtis Maurand via Pdns-users het volgende geschreven:
Hello,
Sorry for the delay. I was dealing with multiple problems at once.
The largest and most pressing was whether the server would continue
to run with a couple of broken in
Hello,
Sorry for the delay. I was dealing with multiple problems at once. The
largest and most pressing was whether the server would continue to run
with a couple of broken inodes. Now that that is out of the way.
In answer to Brian's questions.
Both servers are on the same nat'ed subnet.
