generic Posted February 12, 2007 Share Posted February 12, 2007 my dns servers are ns., ns1, ns2., etc. When I try to update the ns records to show in the proper order in whmcs it keeps defaulting to show ns1. first then ns. second. It wont hold ns. as number 1 dns server. 0 Quote Link to comment Share on other sites More sharing options...
webresellers Posted February 12, 2007 Share Posted February 12, 2007 order doesn't matter... 0 Quote Link to comment Share on other sites More sharing options...
generic Posted February 13, 2007 Author Share Posted February 13, 2007 thanks for your opinion.... still this should be corrected... 0 Quote Link to comment Share on other sites More sharing options...
Willx Posted February 13, 2007 Share Posted February 13, 2007 Can ya explain that better please.. You mean ns2 is your primary but it says ns1 is first? if so maybe its set to show things that are num first.. Like dns1 dns2 ..ns1 ns2 ...dnsi1 dnsi2.. and so on 0 Quote Link to comment Share on other sites More sharing options...
generic Posted February 13, 2007 Author Share Posted February 13, 2007 even though I entered the following order ns.mydomain.com ns1.mydomain.com it shows up in the admin panel as ns1.mydomain.com ns.mydomain.com 0 Quote Link to comment Share on other sites More sharing options...
s1rk3ls Posted February 14, 2007 Share Posted February 14, 2007 WHMCS is getting this info via the registrar API from your domain registrar. I've entered DNS servers directly via the registrars web interface before and when querying WHOIS later, discovered they are not in the same order I entered them. There is no such thing as a truly primary/secondary/tertiary hierarchy in DNS (DNS server selection will always be made at random from the servers available to distribute the load, you can't have all your DNS requests always hit a single server and failover if it's unavailable) Aside from aesthetics, this is a non issue - even then, it would be with the registrar not WHMCS. 0 Quote Link to comment Share on other sites More sharing options...
webresellers Posted February 14, 2007 Share Posted February 14, 2007 sounds like the fields are being sorted by accending order to me.... try adding ns3 on the 1st line , and ns2 on the 2nd line, do they switch? 0 Quote Link to comment Share on other sites More sharing options...
Dominic Posted February 14, 2007 Share Posted February 14, 2007 Your naming is wrong anyway, to be frank. "ns.domain.com" and then "ns1.domain.com" makes absolutely no sense. ns0 - ns1 - ns2 ns1 - ns2 - ns3 ns[ no number ] just doesn't make sense if you want to use numerical sequencing...because it has no number 0 Quote Link to comment Share on other sites More sharing options...
generic Posted February 14, 2007 Author Share Posted February 14, 2007 Your naming is wrong anyway, to be frank. "ns.domain.com" and then "ns1.domain.com" makes absolutely no sense. thanks, i will redo my server just for you. 0 Quote Link to comment Share on other sites More sharing options...
WHMCS CEO Matt Posted February 14, 2007 WHMCS CEO Share Posted February 14, 2007 Back to the original issue, can you confirm which domain registrar this occurs with? Matt 0 Quote Link to comment Share on other sites More sharing options...
Dominic Posted February 15, 2007 Share Posted February 15, 2007 Your naming is wrong anyway, to be frank. "ns.domain.com" and then "ns1.domain.com" makes absolutely no sense. thanks, i will redo my server just for you. Just mentioned so you could see why it might be that way, dunno if it's classed as a bug or not 0 Quote Link to comment Share on other sites More sharing options...
generic Posted February 15, 2007 Author Share Posted February 15, 2007 enom 0 Quote Link to comment Share on other sites More sharing options...
PPH Posted February 15, 2007 Share Posted February 15, 2007 I get the same behavior at enom itself. When I first started with them with ns1.nameserver.com and ns2.nameserver.com NS2 defaults to the 1st field. And with API running, of course it is the same way in WHMCS. 0 Quote Link to comment Share on other sites More sharing options...
Webdomain.com Posted February 16, 2007 Share Posted February 16, 2007 I'll second this behavior. We also use Enom. Even if our Nameservers are correctly defined as NS1 as primary and NS2 as second they still appear in the other way in WHMCS (NS2 as primary and NS1 as secondary). 0 Quote Link to comment Share on other sites More sharing options...
Juanzo Posted November 26, 2009 Share Posted November 26, 2009 Sorry to bring up this old post but this happens to us too. Any feedback or suggestion? 0 Quote Link to comment Share on other sites More sharing options...
Juanzo Posted November 26, 2009 Share Posted November 26, 2009 Just to update, this is something related to Enom and has to do with this. 0 Quote Link to comment Share on other sites More sharing options...
pdn Posted June 10, 2010 Share Posted June 10, 2010 I´ll second this too. I know it´s not a big problem for me but my customers don´t know that. 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.