Op 7 dec. 2022 om 19:47 heeft Curtis Maurand via Pdns-users <pdns-users@mailman.powerdns.com> 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 inodes. Now that that is out of the
way.
In answer to Brian's questions.
Both servers are on the same nat'ed subnet. one at
192.168.100.0/24. The primary name server does have an outside
address. ns1.xyonet.com is 208.105.217.26. port 53 is forwarded to
192.168.100.30.
dig doesn't return an erro
It does., I just doesn't return an address, but
it is actually making the query to the resolver that is adjacent at
192.168.100.20
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
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL:
1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;sirius.xyonet.com. IN A
;; Query time: 0 msec
;; SERVER: 192.168.100.20#53(192.168.100.20)
;; WHEN: Wed Dec 07 13:32:48 EST 2022
;; MSG SIZE rcvd: 46
again, it's only for the locally host domain at 192.168.100.30
I just added to the recursor.conf
forward-zones=xyonet.com=192.168.100.30 and that worked. I would
now call this solved.
On 12/6/22 21:45, Leeflangetje via
Pdns-users wrote:
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. 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. My system is way
more manageable without it. More stable, too. I knew I
needed to do upgrade, debian hasn't upgraded the version in
their repos. I added the powerdns repo to the
sources.list.d/pdns. I digress. I'm now running 4.7.2. It
took a few minutes to get the supermaster/superslave set up
and working.
Things are working from outside and pretty fast, too. It's
internally where things aren't working. the internal
recursor is not resolving anything that is hosted. wierd.
--Curtis
On 12/6/22 12:52, Brian Candler
wrote:
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 the moment. Also,
ns1 is running PowerDNS Authoritative Server 4.4.1, which is
end-of-life, so you ought to look at upgrading it. See https://repo.powerdns.com/
_______________________________________________
Pdns-users mailing list
_______________________________________________
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users
--
Curtis
https://curtis.maurand.com
_______________________________________________
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users
|
_______________________________________________
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users
