Dotnetpanel Forums

I have a lot of issues regarding dns in dnp 2.4.1 and this thread is to sort my issues. I am already in touch with Feodor, but as I said, I just want to use this as a summary in order to allow me a follow up.

1. DNP passes a wrong zone file content to SimpleDNSPlus
• the soa responsible person is missing
• parenthesis at the end of the soa record are missing
• the ttl is placed in front of the ns record, sdns does not seem to like that
2. When creating a new website for a given domain, the very same thing is happening because DNP updates that zone while creating the website
3. When creating a website, DNP is updating the zone but
• it does not check if there already are records matching the record type, it simply adds new records
• it should check if there already is a record that needs to be updated rather than added
• this can cause double * / A records pointing to different locations

All those issues lead to broken dns zones and therefor unresponsive websites. Please fix those ASAP.

 We are looking at migrating to DNP over the next month and use SimpleDNS with around 700+ zones in it, so try to keep it as clean as possiable. This type of bug doesn't sound good at all. Is there any word from Feodor as to when this maybe fixed?

Not yet, no.

I think 1 and 2 are based on zones which were converted from simpledns v4 to v5. At least with my upgrade i had the same issues. With new zones and upgrading them i have none of these issues whatsoever.

3 is indeed a issue; it's possible to add similar dns records.

Frans

I can confirm that there is a bug for imported zones created in SimpleDNS. Bug will be fixed asap.

 maybe this is good moment to add support for API password in SimpleDNS?

Yep, but it can't be added as a hot fix.

Hello

Today I had a customer add a record into his dns zone, after this the zone file got "corrupted" or unreadable by simpledns, this resulted in my customers domain being down for a whole day. DNP could still read the content and displayed it fine in the zone editor, the file itself looked like when you save files under unix and try to open them in windows.

What can I do? First I would like some info about how can I disable dns zone editor for ALL my existing customers. This is a quite serious problem and Im not sure if its dnsplus's fault or dnp. Last time I had an issue both parts refused to talk to eachother to solve it.

Regards

Daniel

Bought yesterday a whole load of licenses for DNP to move over to it as soon as we can.

However have just hit a real show stopper, which we wish we had tested before purchasing, as just set DNP up with our production SimpleDNS servers which have around 700 DNS zones.

After entering a test domain and let DNP create a zone record for it and within about 5 minutes the primary DNS server started crashing, after removing the zone DNP created the server went back to normal.

This is a real show stopper. Is there any word when these issues with SimpleDNS will be fixed as simply can not put DNP into production until this is fixed.

We are working on it.

So, the steps to reproduce for your case is just create a new zone from DNP, right? And it is SimpleDNS 5? Please clarify.

Feodor

If you want I can send you the zone that gets corrupted when adding a new record? I have noticed it only happends with a few select zones, if I add the record manually via simpledns5 gui it works however this record does not show in dnp...

Regards

Daniel

 Yes it is SimpleDNS 5 and the DNS zone was created in DNP.

 Although the primary DNS server did crash again once more after removing the zone in the early hours of the morning so could be a bug in SimpleDNS which was updated to the latest release only a few days ago.

SimpleDNS did send of a number of crash reports to JH Software and I have contacted their support about this so hopefully the issue will be fixed.

I've set the SimpleDNS service Recovery to Auto Restart and with a secondary DNS srever as well it should course to many issues while the problem is resolved.

 I getting the same corruption issue as others in this topic have pointed out.

 Seems that DNP isn't correctly updating the DNS zone correctly and is messing up the part shown in bold so SimpleDNS can not load in the DNS zone. 

;$; Updated with DotNetPanel DNS API 4/18/2008 2:18:17 PM
@        IN SOA    ( ns1.webwizhost.com. 2008041803 10800 600 604800 3600
@        A    84.45.xx.xx
@    3600    NS    ns1.webwizhost.com.
@    3600    NS    ns2.webwizhost.com.
*        A    84.45.xx.xx
www        A    84.45.75.xx
@        A    84.45.xx.xx
*        A    84.45.xx.xx

I can update the incorrect part myself in notepad which then allows it to load into SimpleDNS. The incorrect part should look like:-

 @        IN SOA    ( ns1.webwizhost.com.
              hostmaster.webwizforums.com.
              2008040412  
              1200        
              600         
              777600     
              3600       )

 I beleive I have norrowed down this issue.

It seems that if a DNS zone is created, edited, etc. within DNP then there is no problem.

However, if a DNS zone is imported into DNP or is edited in SimpleDNS then when DNP goes to write to the zone file it becomes corrupted. 

In our case we havent imported any zone, however we have upgraded from simpledns4 to simpledns5.

Regards

Daniel