Hello,
so just stop named and restart pfdns and it should work.

Regards

Fabrice


Le 2013-10-21 18:00, Dell Thornhill a écrit :
Ok - found out some more information:

the 'pfdns' service isn't running per Status > Services.
I clicked "start" and it goes back to stopped.

So I started it from the command prompt (sudo /usr/local/pf/sbin/pfdns start) and it says the following: Couldn't create TCP socket: Address already in use at /usr/lib/perl5/Net/DNS/Nameserver.pm line 90. Net::DNS::Nameserver::new('Net::DNS::Nameserver', 'LocalAddr', 'ARRAY(0x5256338)', 'LocalPort', 53, 'ReplyHandler', 'CODE(0x521e768)', 'Verbose', 0, ...) called at /usr/local/pf/sbin/pfdns line 116 Couldn't create UDP socket: Address already in use at /usr/lib/perl5/Net/DNS/Nameserver.pm line 109. Net::DNS::Nameserver::new('Net::DNS::Nameserver', 'LocalAddr', 'ARRAY(0x5256338)', 'LocalPort', 53, 'ReplyHandler', 'CODE(0x521e768)', 'Verbose', 0, ...) called at /usr/local/pf/sbin/pfdns line 116 Couldn't create TCP socket: Address already in use at /usr/lib/perl5/Net/DNS/Nameserver.pm line 90. Net::DNS::Nameserver::new('Net::DNS::Nameserver', 'LocalAddr', 'ARRAY(0x5256338)', 'LocalPort', 53, 'ReplyHandler', 'CODE(0x521e768)', 'Verbose', 0, ...) called at /usr/local/pf/sbin/pfdns line 116 Couldn't create UDP socket: Address already in use at /usr/lib/perl5/Net/DNS/Nameserver.pm line 109. Net::DNS::Nameserver::new('Net::DNS::Nameserver', 'LocalAddr', 'ARRAY(0x5256338)', 'LocalPort', 53, 'ReplyHandler', 'CODE(0x521e768)', 'Verbose', 0, ...) called at /usr/local/pf/sbin/pfdns line 116
couldn't create nameserver object

So it looks like there's already a DNS server running...?

After a 'netstat -tulpn | grep :53*' *it looks like the named service is listening on 53: tcp 0 0 10.2.6.1:53 <http://10.2.6.1:53> 0.0.0.0:* LISTEN 1215/named tcp 0 0 10.2.5.1:53 <http://10.2.5.1:53> 0.0.0.0:* LISTEN 1215/named tcp 0 0 10.100.100.56:53 <http://10.100.100.56:53> 0.0.0.0:* LISTEN 1215/named tcp 0 0 127.0.0.1:53 <http://127.0.0.1:53> 0.0.0.0:* LISTEN 1215/named


Is that normal? I would imagine that the pfdns service would be in charge? However I do have "named=enabled" in my networks.conf so I dunno. Are they the same thing? Again, not a lot info on either the pfdns or named services in the admin guide.

If I kill the named service and run 'sudo /usr/local/pf/sbin/pfdns start' again it just sits there - nothing happens.

any suggestions would be appreciated.


------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk


_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users


--
Fabrice Durand
[email protected] ::  +1.514.447.4918 (x135) ::  www.inverse.ca
Inverse inc. :: Leaders behind SOGo (http://www.sogo.nu) and PacketFence 
(http://packetfence.org)

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users

Reply via email to