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
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.
You did not report back the results of the other 2 troubleshoot actions
that Brian suggested (dig and tcpdump)
These could hold clues to the cause of your problem.
On Tue, 2022-12-06 at 14:33 -0500, Curtis Maurand via Pdns-users wrote:
> OK, just did the upgrade and adjusted the tables accordingly
OK, just did the upgrade and adjusted the tables accordingly. I don't
like the fact that the update clobbered the /etc/init.d/pdns file. We
don't all run distributions with systemd. Systemd is big and buggy, not
to mention the controtions one has to go through to get things to work
properly.
On 06/12/2022 17:41, Curtis Maurand via Pdns-users wrote:
You can use either xyonet.com or cybernexus.net
And the pdns-auth server which you are referring to is ns1.xyonet.com or
ns2.xyonet.com? Or is it neither of these, and is a hidden primary?
FYI, ns2.xyonet.com is not responding at th
You can use either xyonet.com or cybernexus.net
On 12/6/22 12:26, Brian Candler wrote:
On 06/12/2022 17:06, Curtis Maurand via Pdns-users wrote:
On the authoritative server I host a domain that I'll call domain.tld
as the example.
It really helps if you give the real domain, since many pro
On 06/12/2022 17:06, Curtis Maurand via Pdns-users wrote:
On the authoritative server I host a domain that I'll call domain.tld
as the example.
It really helps if you give the real domain, since many problems can be
diagnosed easily by querying the auth nameserver. See
https://blog.powerdns.
Hello,
I've been a pdns user since, well, forever. I abandoned bind long ago.
I currently have a set up where I run an authoritative server on a
virtual machine and I run pdns-recursor on a separate virtual machine.
On the authoritative server I host a domain that I'll call domain.tld as
th
11 matches
Mail list logo
