Project

General

Profile

Actions

Bug #514

closed

dnscache does not start after reboot; but starts after "save" on GUI

Added by Henrik Kaare Poulsen about 15 years ago. Updated almost 15 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
DNS Server
Target version:
-
Start date:
04/16/2010
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Affected Version:
2.0
Affected Plus Version:
Affected Architecture:

Description

Installed pfSense-2.0-BETA1-20100415-2300; setup with several OPT interfaces in bridge with LAN.
Then added tinyDNS package around 20100416 14:00 UTC.

Configured tinyDNS with a local server on 127.0.0.1 and caching for the bridge address.
Resolving using the local bridge address does not work.

Reboot.
Resolving using the local bridge address still does not work.

On the GUI select "Services -> DNS Server -> Settings"; change nothing; click "save"
Now resolving using the local bridge address does work.

This is consistent:
After reboot resolving does not work; then after touching the GUI resolving works again.

After reboot:

# ls /var/run/service/
axfrdns    tinydns

# ps auxww | grep dns
root      22906  0.0  0.2  1572   808  ??  S     2:52PM   0:00.01 supervise tinydns
root      23142  0.0  0.2  1572   772  ??  S     2:52PM   0:00.01 supervise dnscache0
Gdnslog   23620  0.0  0.1  1584   712  ??  S     2:52PM   0:00.02 multilog t ./main
Gdnscache 23679  0.0  0.4  4340  2208  ??  S     2:52PM   0:00.04 /usr/local/bin/dnscache
Gdnslog   24447  0.0  0.1  1584   712  ??  S     2:52PM   0:00.02 multilog t ./main
Gtinydns  29795  0.0  0.2  1696   800  ??  S     2:52PM   0:00.02 /usr/local/bin/tinydns

# netstat -f inet -nal
tcp4       0      0 192.168.YYY.254.53      *.*                    LISTEN
udp4       0      0 127.0.0.1.53           *.*                    
[...]

# cat /etc/resolv.conf 
domain mydomain.lan
nameserver 193.XXX.153.164
nameserver 194.XXX.134.83

# dig @127.0.0.1 ns.mydomain.lan
WORKS

# dig @192.168.YYY.254 ns.mydomain.lan
TIMES OUT

After GUI select "Services -> DNS Server -> Settings"; change nothing; click "save"

# ls /var/run/service/
axfrdns        dnscache0    tinydns

# ps auxww | grep dns
root      22906  0.0  0.2  1572   808  ??  S     2:52PM   0:00.01 supervise tinydns
root      23142  0.0  0.2  1572   808  ??  S     2:52PM   0:00.01 supervise dnscache0
Gdnslog   23620  0.0  0.1  1584   712  ??  S     2:52PM   0:00.02 multilog t ./main
Gdnslog   24447  0.0  0.1  1584   712  ??  I     2:52PM   0:00.02 multilog t ./main
Gtinydns  41772  0.0  0.2  1696   800  ??  S     2:56PM   0:00.02 /usr/local/bin/tinydns
root      42562  0.0  0.2  1572   772  ??  S     2:56PM   0:00.01 supervise dnscache0
Gdnscache 42872  0.0  0.4  4340  2224  ??  S     2:56PM   0:00.04 /usr/local/bin/dnscache
Gdnslog   43123  0.0  0.1  1584   712  ??  S     2:56PM   0:00.02 multilog t ./main

# cat /etc/resolv.conf
domain mydomain.lan
nameserver 192.168.YYY.254

# netstat -f inet -nal
tcp4       0      0 192.168.YYY.254.53      *.*                    LISTEN
udp4       0      0 192.168.YYY.254.53      *.*                    
udp4       0      0 127.0.0.1.53           *.*                    
[...]

# dig @192.168.YYY.254 ns.mydomain.lan
WORKS

# dig @127.0.0.1 ns.mydomain.lan
WORKS

Actions #1

Updated by Henrik Kaare Poulsen about 15 years ago

I can confirm that this bug (and workaround) is still found in 20100421 03:15 snapshot with tinyDNS package installed around 20100421 18:00 UTC.

Actions #2

Updated by Henrik Kaare Poulsen about 15 years ago

Any news or comments on this issue?

Actions #3

Updated by Chris Buechler almost 15 years ago

  • Category set to DNS Server
Actions #4

Updated by Chris Buechler almost 15 years ago

  • Status changed from New to Resolved

fixed in the latest package

Actions

Also available in: Atom PDF