![]() |
|
|||||||
| Chit Chat Public Talk about any thing you want! This forum is public. |
![]() |
|
|
Thread Tools | Search this Thread | Display Modes |
|
|
|
#1
|
|||||||||||
|
|||||||||||
|
I would like to know if I am the only person having problem with hsphere.cc nameservers.
The SOA records of ns1 and ns2 are not matching up. On ns2 the nameservers are still. ns2.anthill.co.za internet address = 216.157.129.251 ns3.anthill.co.za internet address = 216.157.131.129 Witch is the wrong IP's? I cannot register new domains in the .co.za webspace anymore since they are very strict on this kind of thing. We need more control over our nameservers. Gerhardus |
|
#2
|
||||
|
||||
|
There were a number of notices sent out regarding this. Those IP addresses have not been correct for quite some time now. Here are the correct IP addresses to use:
ns.hsphere.cc: 216.157.145.10 ns1.hsphere.cc: 216.157.145.11 ns2.hsphere.cc: 216.157.145.12 ns3.hsphere.cc: 216.157.145.13 You will probably need to login to your reseller control panel and your service domain's domain registrar to update these. |
|
#3
|
|||||||||||
|
|||||||||||
|
Can you DIG it?
#dig @ns2.anthill.co.za clientdomain.co.za soa ns2.anthill.co.za. 86400 IN A 216.157.145.12 ns3.anthill.co.za. 86400 IN A 216.157.145.13 opposed to: #dig @ns3.anthill.co.za clientdomain.co.za soa ns2.anthill.co.za. 36312 IN A 216.157.129.251 ns3.anthill.co.za. 36312 IN A 216.157.131.129 but why. and yes I know what the new servers IP's are. I have been told a thousand times. Gerhardus |
|
#4
|
|||||||||||
|
|||||||||||
|
anthill.co.za Nameserver (NS) IN 16 hrs. ns1.anthill.co.za
anthill.co.za Nameserver (NS) IN 16 hrs. ns2.anthill.co.za anthill.co.za Nameserver (NS) IN 16 hrs. ns1.anthill.co.za anthill.co.za Nameserver (NS) IN 16 hrs. ns2.anthill.co.za ns1.anthill.co.za Host address (A) IN 7 hrs. 216.157.145.11 ns2.anthill.co.za Host address (A) IN 7 hrs. 216.157.129.251 A different result again, that was querying ns3. You can always host the DNS elsewhere if your not able to do what you want. I'd submit a trouble ticket though if you want to get any further with this as the forums aren't really the "1st line" for direct technical support from Vortech. |
|
#5
|
|||||||||||
|
|||||||||||
|
Quote:
The forums is my last hope. I have tried everything, tickets, live chat, emails and I always get the same reply. "ns.hsphere.cc: 216.157.145.10 ns1.hsphere.cc: 216.157.145.11 ns2.hsphere.cc: 216.157.145.12 ns3.hsphere.cc: 216.157.145.13" duh, I know what the nameservers are I've been working with nameservers for 5 years. As for hosting the DNS somewhere else, why should I? I pay for the service right? Anyway thanx for the reply. glad to to somebody that did'nt just give the answer from the FAQ ![]() |
|
#6
|
||||
|
||||
|
i got same result as brangwyn done
![]()
__________________
I Love Cambodia ![]() |
|
#7
|
|||||||||||
|
|||||||||||
|
According to DNSReports you do have the wrong IP address registered at the ROOT for the domain
Your NS records at the parent servers are: ns2.anthill.co.za. [216.157.129.251] [TTL=86400] [US] ns1.anthill.co.za. [216.157.145.11] [TTL=86400] [US] These must be updated at your Registrar and is probably what Tech support has been telling you, this info doesn't come from Vortech, it comes from the root .co.za Zone servers. Most registrars let you register your child nameservers and set the IP etc for them, this is not the same as setting the nameservers for the domain. If you believe you've done this ok, then you should be talking to the .co.za registry, my bet is that if you have updated it their system has somehow broken down and not updated the root nameservers correctly (I've seen this happen numerous times before where they report one IP, but theres a totally different IP at the root nameserver still). This also look very weird but is probably just a result of the nameserver issue. Your www.anthill.co.za A record is: www.anthill.co.za. A 216.157.154.11 [TTL=86400] [US] The "A" record for the domain is actually pointing at the nameserver ! Last edited by Brangwyn : 11-19-2004 at 02:58 AM. |
|
#8
|
|||||||||||
|
|||||||||||
|
I just tried this.
I signed up for a new client of mine dmracing.co.za All looked well, in the CP I have the following nameservers. Name Servers ns2.anthill.co.za -> 216.157.145.12 ns3.anthill.co.za -> 216.157.145.13 So after checking the info on the servers I registered with those servers and IP's Right so I registered the domain with the .co.za registrar, after registering it I went to have a look at what they got from the nameservers. ns2.anthill.co.za internet address = 216.157.129.251 ns3.anthill.co.za internet address = 216.157.131.129 this is what they got. Why? |
|
#9
|
|||||||||||
|
|||||||||||
|
Becuase ns2/ns3.anthill.co.za are loaded with your Registrar with that IP address (at least thats how most other TLD's work the nameservers are defined as child nameservers of the domain anthill.co.za with their respective IP address). Now whether they are wrong becuase it hasn't been updated by you, or becuase your registrar screwed up the changes when you updated them with the new IP who knows. But from everything I've been able to ascertain about that domain I would definitely say the problem lies with the registrar and not with Vortech DNS, which I suspect is precisely what tech support has been telling you as well.
If you look at the DNSReport for that domain you'll see it's getting the A records for your ns1 and ns2 from [These were obtained from ns0.coza.net.za] thats the .co.za ROOT nameservers so that to me indicates where the incorrect records reside. Last edited by Brangwyn : 11-19-2004 at 06:19 AM. |
|
#10
|
|||||||||||
|
|||||||||||
|
According to co.za you actually have to specify these IP's when you register the domain with them
http://co.za/trouble/trouble.html When the dmracing.co.za domain was registered what IP addresses were supplied for the nameservers? |
|
#11
|
|||||||||||
|
|||||||||||
|
I specifically specified
ns2.anthill.co.za -> 216.157.145.12 ns3.anthill.co.za -> 216.157.145.13 the segment from my submission. ------------snip------------------------- 6a. Primary server FQDN: ns2.anthill.co.za 6b. Primary server IP address: 216.157.145.12 6e. Secondary server FQDN: ns3.anthill.co.za 6f. Secondary server IP address: 216.157.145.13 ------------------------snip--------------------------------- |
|
#12
|
|||||||||||
|
|||||||||||
|
Right, so the problem is with your service domains child nameserver registration like I said above. I would strongly suggest you consider contacting your registrar and getting them to check things out at the root zone nameserver level.
When I query ns0.coza.net.za i get the following anthill.co.za Nameserver (NS) IN 1 days ns1.anthill.co.za anthill.co.za Nameserver (NS) IN 1 days ns2.anthill.co.za anthill.co.za Nameserver (NS) IN 1 days ns1.anthill.co.za anthill.co.za Nameserver (NS) IN 1 days ns2.anthill.co.za ns1.anthill.co.za Host address (A) IN 1 days 216.157.145.11 ns2.anthill.co.za Host address (A) IN 1 days 216.157.129.251 Clearly the ns2 A record is incorrect, and so is the ns3 record ns3.anthill.co.za Host address (A) IN 1 days 216.157.131.129 anthill.co.za Nameserver (NS) IN 1 days ns1.anthill.co.za anthill.co.za Nameserver (NS) IN 1 days ns2.anthill.co.za ns1.anthill.co.za Host address (A) IN 1 days 216.157.145.11 ns2.anthill.co.za Host address (A) IN 1 days 216.157.129.251 Last edited by Brangwyn : 11-19-2004 at 07:25 AM. |
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | Search this Thread |
| Display Modes | |
|
|