Hello, My earlier reply to the list is currently held in moderation (I believe because I attached another log which was slightly larger) but named.conf is still actually being overwritten. /etc/named.conf.unmanaged still has our changes, but /etc/named.conf keeps going back to the default. Here is the output of that command:
# /usr/share/sipxecs/cfmodules/sipx 1 | grep unmanaged -unmanaged_ntpd -unmanaged_dhcpd -firewall_unmanaged -sipxdns_unmanaged =sipxdns_unmanaged_0=127.0.0.1 =sipxdns_unmanaged_1=208.201.224.11 =sipxdns_unmanaged_2= =sipxdns_unmanaged_3= Thanks, Alan Worstell A1 Networks - Systems Administrator VTSP, dCAA, LPIC-1, Linux+, CLA, DCTS (707)570-2021 x204 For support issues please email [email protected] or call 707-703-1050 On 10/25/12 3:10 PM, George Niculae wrote: > On Thu, Oct 25, 2012 at 6:15 PM, Alan Worstell > <[email protected]> wrote: >> Hello, >> As Trevor mentioned, replacing /etc/named.conf.unmanaged with our changed >> conf resolved this. I had noticed in sipxagent.log entries about fulfilling >> promises from that file. >> Attached is the log file in question. >> > Thanks, > > could you also provide output for > > /usr/share/sipxecs/cfmodules/sipx 1 | grep unmanaged > > performed on primary? > > George > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
