| View previous topic :: View next topic |
| Author |
Message |
afdev
n00b
Joined: 19 Dec 2023
Posts: 49
|
 Posted: Wed Feb 21, 2024 5:57 pm Post subject: PDNS doesn't receive any DNS request |
 |
|
Hi all,
I have inherited a production server where it was installed PDNS as DNS server.
After a reboot during a kernel upgrade, the DNS server doesn't work anymore...
All the company websites are hosted there and now they are unreachable.
I was trying to get it fixed, but I don't know anymore where should I look.
If someone please could help me out of this, many thanks in advance.
After the reboot it failed to start, I had a socket conflict with postgresql.
| Code: |
# /etc/init.d/pdns start
* /run/postgresql: correcting mode
* Starting PostgreSQL 12 ... [ ok ]
* /run/postgresql: correcting mode
* Socket conflict.
* A server is already listening on:
* /run/postgresql/.s.PGSQL.5432
* HINT: Change PGPORT to listen on a different socket.
* ERROR: postgresql-13 failed to start
* Starting PowerDNS Authoritative Server ...
* Failed to start PowerDNS Authoritative Server [ !! ]
* ERROR: pdns failed to start
|
After that I have managed to solve the problem, stopping the PG 12 and start the 13 one.
But PDNS was not starting, because this time I have found out the backend was not specified in /etc/powerdns/pdns.conf
So, I have setup it:
That's strange, because before the rebooting it was working.
I have checked and I don't have a table for pdns, so I assume postgresql was not used as backend.
If I stop the service and run it standalone I don't see any request coming in.
And of course ping, nslookup, etc... don't work to resolve any domain.
| Code: |
# pdns_server --control-console --loglevel=5
Feb 21 16:58:53 Loading '/usr/lib64/powerdns/pdns/libbindbackend.so'
Feb 21 16:58:53 This is a standalone pdns
Feb 21 16:58:53 UDP server bound to 0.0.0.0:53
Feb 21 16:58:53 UDP server bound to [::]:53
Feb 21 16:58:53 TCP server bound to 0.0.0.0:53
Feb 21 16:58:53 TCP server bound to [::]:53
Feb 21 16:58:53 PowerDNS Authoritative Server 4.3.1 (C) 2001-2020 PowerDNS.COM BV
Feb 21 16:58:53 Using 64-bits mode. Built using gcc 9.3.0 on Oct 12 2020 07:46:06 by portage@obsidian.ad-notam.net.
Feb 21 16:58:53 PowerDNS comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it according to the terms of the GPL version 2.
Feb 21 16:58:53 PowerDNS Security Update Mandatory: Upgrade now, see https://doc.powerdns.com/authoritative/security-advisories/powerdns-advisory-2022-01.html
Feb 21 16:58:53 Creating backend connection for TCP
Feb 21 16:58:53 About to create 3 backend threads for UDP
% Feb 21 16:58:53 Done launching threads, ready to distribute questions
|
Any help will be highly appreciated, thank you. |
|
| Back to top |
|
 |
freke
l33t
Joined: 23 Jan 2003
Posts: 977
Location: Somewhere in Denmark
|
| Posted: Wed Feb 21, 2024 6:52 pm Post subject: |
|
|
| I don't know neither pdns nor postgresql - but is network interface(s) up and running as per expected? (ie. ifconfig -a) |
|
| Back to top |
|
|
szatox
Advocate
Joined: 27 Aug 2013
Posts: 3139
|
| Posted: Wed Feb 21, 2024 7:50 pm Post subject: |
|
|
| Quote: | | I have checked and I don't have a table for pdns, so I assume postgresql was not used as backend. |
Why not start with looking ad pdns's config file instead?
There is like a dozen of supported backends, and pdns allows for some setups which can be described as either brilliant or retarded, depending solely on the person asked.
Also: logs. Pdns should log the reason why it failed. In fact, this is the first thing to check, config comes in the second.
_________________
Make Computing Fun Again |
|
| Back to top |
|
|
afdev
n00b
Joined: 19 Dec 2023
Posts: 49
|
| Posted: Wed Feb 21, 2024 8:14 pm Post subject: |
|
|
Yes,
the network was up and running.
In the meanwhile I have "solved" the issue... I have configured the DNS zone using the webinterface of the domains registrar.
szatox,
yes, looking in the logs is the first thing I did, but I didn't find any entry apart of the few lines already posted.
I had a look at the /var/log/messages.
I had a look at the configuration, but I didn't find the location of the log specified there, so I assumed it was logged in the messages.
Anyway, since now the emergency is resolved in some way, I would close the topic.
Thank you. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Networking & Security
