Submitted by merlynx on Sun, 03/28/2010 - 21:07
When trying to add multiple records to DNS zones, setting "new record value" when said value is a names server value, it does not submit the new value correctly to the process.
add_name_server.png is the first step, note, "ns3.lightonthenet.org"
ns1_repeat.png is what happens when this form is submitted - the system saying "ns1.lightonthenet.org" already exists.
The expected behavior would be that the "ns3.lightonthenet.org" would be added OR said value would be noted as "already exists"
Thanks, Jeremy Ciaramella
Status:
Closed (fixed)
Comments
Submitted by merlynx on Sun, 03/28/2010 - 21:12 Comment #1
Similar behavior when dealing with adding Mail Server DNS entries as well. For example...
mail.example.com exists for example.com. I want to add mx.someotherdomain.com and then remove mail.example.com (because the mail for example.com is handled by a different system).
When I try to use this interface (see attached files) I get told that "mail.example.com already exists".
So, one name server entry and one mail entry stops this interface from working...? thanks, -J
Submitted by JamieCameron on Sun, 03/28/2010 - 23:27 Comment #2
In the first case, does it help if you select "Create even if record already exists" ?
That will cause Webmin to add the record even if an NS for the domain already exists, which I presume is the case ..
Submitted by merlynx on Mon, 03/29/2010 - 22:54 Comment #3
...and that's what I did and ended up with with a bunch of duplicate records. Where they MX records already existed (like I said, almost 200 domains) they were duplicated. It would be nice if the form process "saw" that the submitted value of mx.whatever.com already exists and the response would be to skip that record in the process and echo back to the user "mx.whatever.com already exists, skipping" or something akin to that.
Submitted by JamieCameron on Tue, 03/30/2010 - 00:21 Comment #4
Ok, I see now. I will have Webmin never create a record with the same name and value when doing a mass add, which never makes sense. This will be fixed in Webmin 1.520.
Would that solve the problem for you?
Submitted by JamieCameron on Tue, 03/30/2010 - 00:22 Comment #5
Ok, I see now. I will have Webmin never create a record with the same name and value when doing a mass add, which never makes sense. This will be fixed in Webmin 1.520.
Would that solve the problem for you?
Submitted by merlynx on Tue, 03/30/2010 - 09:33 Comment #6
Totally, that would make sense in the UI - thanks!
Submitted by JamieCameron on Tue, 03/30/2010 - 11:10 Comment #7
Great!
Submitted by Issues on Wed, 04/14/2010 - 01:21 Comment #8
Automatically closed -- issue fixed for 2 weeks with no activity.