Possible bug in creating nameservers and records

M

mxcreep

Verified User
Joined
Feb 3, 2005
Messages
10
Location
Netherlands
The following happened to me twice :

We (switchbox hosting) bought recently 5 new licenses of DA, I reserved 5 ip adresses for them....
Two of the uses adresses ended on .244 and .245

So I installed the server and added an extra ip for that server, I will take the .245 as an example and added .34 as second ip adres for dns usage...

When I tried to add the nameservers the normal way I noticed that DA lists the ip adresses in order of number, so .34 was listed first and .245 as second...
Adding nameservers ended up as 245 as ns2 and 34 as ns1...
I didn't want it that way so I deleted them, edited the name boxes for nameserver names and created ns1 on 245 and ns2 on 34......

Later on (dutch domain registration checks this) we noticed that DA created wrong SOA records, with ns2 in it instead of ns1...
All dutch domains where not transferable to these nameservers because of this...the ns server listed in the SOA record should be the primary nameserver......

I understand why DA adds ns2 as nameserver in the SOA record....that is caused by some kind of template probably....
But the way DA handles this right now it isn't possible for me to get the primary nameserver on a specific ip if there is an other ip with a lower adres...

In my opinion I should be able to tell DA what ip should be used for primary and what for secondary....and not just using numeric order...
 
I'm responding only to point out that there's no such thing as "primary" and "secondary" in nameservers.

The correct nomenclature is master and slave, and whether or not a system is a master or a slave it will have equal precedence when a resolver actually calls for DNS resolution.

So while I can't speak for DA as to why they did it, it doesn't matter to me.

You can always edit your DNS zone files manually.

Jeff
 
You are right about the ability of editting zone files manually...
But I rent servers to customers that pay me for a control panel like DA because they do not understand anything of *nix...
Think it will not be a very wise idea to tell someone like that to edit his zonefiles manually...

In fact if you're able to manage configurations like zone files manually...you don't need a control panel...I never install control panels on servers I manage myself, they only make it harder for me to config a server the way I like it....
But that's not the case....control panels like DA are meant for people who do not like or are not able to manage a linux server themselves...

The fact that resolving ip adresses from a dns configged like this doesn't mean the config is right...maybe it doesn't bother you...but if you had dutch customers registering dutch domains it would bother you...

To continue the editting of zone files manually...this customer immediately created over 100 new domains on his server...really great job to edit them al by hand...
 
There are many things a control panel can do for you besides DNS.

I've asked a principal from a Dutch company who has multiple DA servers to respond to this thread. If there does appear to be a bug I will do whatever I can to get it fixed.

Jeff
 
Hi,

Jeff asked me to take a look at this thread and see if I can solve the issue or at least give some clarity.

Could you supply me with a domainname and the NS records for that domain name so I can check it against the SIDN nameservercheck. Then I'll check it against other tools to check the actual DNS configuration and as a last resort I might ask for access to the DA control panel for that 1 domain so I can see your actual setup.

Kind Regards,
Onno Vrijburg
 
That's not possible anymore...when we found out what was happening I edited all SOA records in the zone files...
After that I cleared the nameservers on both ip's and exhanged them , so ns1 is now .34 and ns2 is now .245
We also changed the nameserver registration itselves so it would fit again to the config in the control panel...
So everything is working properly now, but I had to edit about everything manually because of this...
 
mxcreep said:
That's not possible anymore...when we found out what was happening I edited all SOA records in the zone files...
After that I cleared the nameservers on both ip's and exhanged them , so ns1 is now .34 and ns2 is now .245
We also changed the nameserver registration itselves so it would fit again to the config in the control panel...
So everything is working properly now, but I had to edit about everything manually because of this...
Click to expand...

Can you tell me exactly how it was set up so I can recreate similar conditions on one of my development/test servers and try and figure out what whent wrong. If it's only because the ns1 has a higher number than ns2 also let me know that.

Regards,
Onno
 
Hay Onno,

It was indeed only because of a higher ip number of ns1 than ns2's ip number....
Because of that I changed the names in the nameserver boxes (where you add nameservers)...but that caused the trouble of getting ns2 in the SOA record where ns1 should be in there...

Grtz,

Werner
 
mxcreep said:
Hay Onno,

It was indeed only because of a higher ip number of ns1 than ns2's ip number....
Because of that I changed the names in the nameserver boxes (where you add nameservers)...but that caused the trouble of getting ns2 in the SOA record where ns1 should be in there...

Grtz,

Werner
Click to expand...

Hallo Werner,

I'll build a testsystem and try to confirm this. I'll post the result here.

Regards,
Onno Vrijburg
 
Thanks, Onno.

Since you never said anything to me about the problem I thought you either never saw it, or if you did, you'd made an easy fix for it.

We all appreciate your input; we all benefit from each other's knowledge.

Jeff
 
You must log in or register to reply here.
Back
Top