New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create SOA - Question #44

beza2000 opened this Issue Nov 26, 2013 · 2 comments


None yet
2 participants

beza2000 commented Nov 26, 2013

I don't understand.
What is the validate when I create a SOA?
Fields are evaluated from the top down. If the upper field is wrong, all the lower fields are invalidate.
Field Master Server can't write the real server - only one name without points. Otherwise is wrong.
Field Email Address - you can't write a real address - only one name without points. Otherwise is wrong.
Am I missing something?
Can I read somewhat about the criteria for the correctness of SOA in facileManager?.


This comment has been minimized.


WillyXJ commented Nov 27, 2013

Yeah, the validation of SOA is a bit weak and confusing and needs to be improved. It also looks like the help file needs to be updated to address the SOA as well.

The key is the bottom field "Append Domain" which will automatically append the domain (or zone name) to the master server and email address. So, if you enter '' for master server and leave Append Domain to 'yes' then the result ends up being '' (assuming '' is the zone name) which is 'invalid' and the same applies to the email address. So, you can either enter 'ns1' for the master server and 'username' for the email address and append the domain automatically so both become '' and '' respectively. Or you can enter the full master server name and email address, but set Append Domain to 'no' (just remember to end them with a period).

I hope this helps and I'll leave this issue open until improvements are added to the code for the next release.


This comment has been minimized.


WillyXJ commented Dec 4, 2013

SOA validation and help files have been updated and will go out with the next release. You can either wait for the release or manually apply the changes found in 612bfec.

@WillyXJ WillyXJ closed this Dec 4, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment