pdnsd works fine, but not after reboot

ozar · 2008-04-11 04:25:16

Hey guys, I just installed pdnsd and it works great, except that after each reboot, the server fails.

I've included it in my daemons array right after networking, and on reboot the boot messages show that it's starting successfully, but then it doesn't work and only gives a server failed error message when I run an nslookup or dig search.

Once booted, I can run /etc/rc.d/pdnsd restart and all is working fine again.

Anyone have any idea what the problem might be?

Thanks for any help.

ozar · 2008-04-11 19:47:33

Nevermind, guys... I've removed pdnsd and installed bind instead, and it's working fine.

ozar · 2008-04-11 22:54:49

Sorry for bringing this topic back to life.

Bind is working great, but I started thinking that the cached dns entries available at reboot with pdnsd would still make it a very attractive option, so if anyone does know what could have been the problem described above in the original post, I'd be happy to run pdnsd again and test it to see if we can get it working.

Thanks again for any help.

ozar · 2008-04-12 05:34:53

Just an update...

I've found that if I enable the root servers in the server section, pdnsd works fine after a system reboot. However, it seems to be passing up my ISP's dns servers and going straight to the root servers, at least on the first search.

Is that supposed to happen? Was I supposed to enable the root servers to begin with? The Arch wiki page I followed indicated only that my ISP dns servers needed to be listed and enabled. Anyone know for sure?

Thanks again.

skymt · 2008-04-12 17:38:11

Did you get my email? I asked you to run pdnsd as root and see what errors it prints. I've also discovered since then that pdnsd logs to /var/log/daemon.log, so the relevant contents of that file might also be useful.

ozar · 2008-04-12 18:03:02

skymt wrote:

Did you get my email? I asked you to run pdnsd as root and see what errors it prints. I've also discovered since then that pdnsd logs to /var/log/daemon.log, so the relevant contents of that file might also be useful.

Yes, I did skymt and thanks for that. I got no errors at all and it ran just fine. I had already looked in daemon.log but didn't see anything that led me to a fix.

I've found that if I use the "none" option for uptest in the server section, everything works fine on a fresh reboot. Is there any problem with me using that option? Or would changing some other option fix it, perhaps?

All the permissions seem to be in order on all files and folders related to pdnsd.

Thanks a million for the reply and help.

lynix · 2010-09-01 07:26:28

Very old topic, but same problem

Any update on this? I'll try the fix with "uptest=none", but did anyone find a real solution / explanation?

Pero · 2011-11-11 15:49:27

Still a very old topic, but same problem here ...

Anyone found a solution?

fsckd · 2011-11-11 20:04:07

Welcome to the forums Pero. Yes, it is an old topic and ... you have necro-bumped a necro-bump. Our rules can be found here: https://wiki.archlinux.org/index.php/Forum_Etiquette
Closing.

Arch Linux

#1 2008-04-11 04:25:16

pdnsd works fine, but not after reboot

#2 2008-04-11 19:47:33

Re: pdnsd works fine, but not after reboot

#3 2008-04-11 22:54:49

Re: pdnsd works fine, but not after reboot

#4 2008-04-12 05:34:53

Re: pdnsd works fine, but not after reboot

#5 2008-04-12 17:38:11

Re: pdnsd works fine, but not after reboot

#6 2008-04-12 18:03:02

Re: pdnsd works fine, but not after reboot

#7 2010-09-01 07:26:28

Re: pdnsd works fine, but not after reboot

#8 2011-11-11 15:49:27

Re: pdnsd works fine, but not after reboot

#9 2011-11-11 20:04:07

Re: pdnsd works fine, but not after reboot

Board footer