> > Hi, > > I am working on a solution to automatically add the required DNS > records > generated by the tool "sipx-dns" to Windows DNS server if applicable. > Basically it uses a open source tool "winexe" and a Windows support > tool > DnsCmd.exe to achieve this. > "winexe" allows Linux users to issue a command to remote Windows > server. > DnsCmd.exe is a windows support tool to interact with Windows DNS and > can be downloaded from Microsoft website. > > For this, some provision needs to be done > > 1) DNS server IP of course > 2) A Windows user credentials with admin privilege (username / > password) > 3) Also indication this is a windows DNS. > > I am looking into about the UI part for provision and integration point > with sipX. > > I am thinking this occurs in both system setup phase (initial value) > and > in sipXconfig (can be changed later). > > In system setup phase, this could be done at the DNS setting phase > (inside sipxecs-setup-system). > Inside sipXconifg, we should have an entry point dedicated for DNS > setting for both Windows or Linux scenarios (Maybe move DNS advisor > there too) > > Comments?
I think the initial setup would be ok however not sure if that is the easiest place to get feedback and make the user experience solid. In sipXconfig in the DNS advisor would be the best place although if we add this the name may need to change. Ideally a nice ability to add this and corresponding warnings and also a way to revert any changes. > > Thanks > Jason > _______________________________________________ > sipx-dev mailing list [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev > sipXecs IP PBX -- http://www.sipfoundry.org/ _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
