![]() ![]() ![]() |
|
tkayed:kenkeniff: Do they give you an option in their control panel to add more domains or sub-domains to your site?
no. only the site address, which is hypnobirthing.kiwi.nzkenkeniff: In that case your best bet is to find a DNS host that does URL forwarding for individual sub-domains and setup the ones you need as previously described (so you don't need to rely on the random Geekzoner's servers being up 24/7).
do you or anyone else recommend or even know of any NZ-based services that I can use for the DNS host? And if so, does that mean I need to point nameservers and then setup DNS zones with that provider, correct?
tkayed: well they are supposed to work, but they are saying it is an issue with .kiwi.nz - which is a subdomain, and they don't deal with subdomains the same as top-level domains. AND they usually don't have a problem with .co.nz domains, put apparently plenty of people do have this issue with subdomains (paraphrased from Weebly).
This was my post to their facebook page after getting no response from my original support ticket: https://www.facebook.com/photo.php?fbid=10203445288599381&set=o.5855802471&type=1
I have since been dealing specifically with one of their support persons via email.
weebly: "It does seem like its coming from the new kiwi domains from what we have seen here so far. The co.nz, etc domains are working without this redirect for most users."
and in response to my question about .co.nz domains:
weebly: "We have countless Weebly users that are utilizing these domains some don't need the redirect while others do. These domains are treated like subdomains. If it ended in .za instead of kiwi.za you would already be working."
If there are plenty of people with this issue, I can't find any sources on the web.
mattwnz: It sounds like they are telling you rubbish, or the people you are communicating with don't know their stuff. They may just be following a flowchart. You need to escalate it. .kiwi.nz is at the same level as .co.nz. Also on the same level as .com.au.
kenkeniff: Have you tried setting your domain to "www.hypnobirthing.kiwi.nz" in Weebly and seeing if that and "hypnobirthing.kiwi.nz" loads properly?
Remember to point your WWW A-record back to Weebly first.
tkayed:mattwnz: It sounds like they are telling you rubbish, or the people you are communicating with don't know their stuff. They may just be following a flowchart. You need to escalate it. .kiwi.nz is at the same level as .co.nz. Also on the same level as .com.au.
That has been my opinion as well, but as someone without a strong footing in IT it's been hard for me to argue the point.
Me: "A CNAME record should definitely work. ".kiwi.nz" domains should be no different than ".co.nz" or ".govt.nz" so shouldn't require any special treatment. BUT ".kiwi.nz" is part of a new series of domain names recently put forward here in NZ by InternetNZ and ICANN - could that be the problem at the Weebly end? It has been suggested that it is a DNS server issues, but I have several domains with 1stDomains and they all work fine with A-record (root) and CNAME (www) setups."
Weebly: "While I can't speak to ICANN or the newness of a domain series, using a CNAME as your WWW alias will work - however the A record should as well. At this point you definitely need to speak to your registrar and have them troubleshoot why your WWW version is not talking to your website."
mattwnz: It sounds like they are telling you rubbish, or the people you are communicating with don't know their stuff. They may just be following a flowchart. You need to escalate it. .kiwi.nz is at the same level as .co.nz. Also on the same level as .com.au.
mattwnz: If I do a traceroute on the www version it traces to 192.185.186.227 . If I do a trace on the non www version it traces to pages-custom-5.weebly.com . So it looks like the servers at 192.185.186.227 aren't setup for your domain. .kiwi.nz domains have been around for quite a while, so won't have anything to do with it.
tkayed:mattwnz: It sounds like they are telling you rubbish, or the people you are communicating with don't know their stuff. They may just be following a flowchart. You need to escalate it. .kiwi.nz is at the same level as .co.nz. Also on the same level as .com.au.
That has been my opinion as well, but as someone without a strong footing in IT it's been hard for me to argue the point.
Me: "A CNAME record should definitely work. ".kiwi.nz" domains should be no different than ".co.nz" or ".govt.nz" so shouldn't require any special treatment. BUT ".kiwi.nz" is part of a new series of domain names recently put forward here in NZ by InternetNZ and ICANN - could that be the problem at the Weebly end? It has been suggested that it is a DNS server issues, but I have several domains with 1stDomains and they all work fine with A-record (root) and CNAME (www) setups."
Weebly: "While I can't speak to ICANN or the newness of a domain series, using a CNAME as your WWW alias will work - however the A record should as well. At this point you definitely need to speak to your registrar and have them troubleshoot why your WWW version is not talking to your website."
Geoff E
kenkeniff:mattwnz: It sounds like they are telling you rubbish, or the people you are communicating with don't know their stuff. They may just be following a flowchart. You need to escalate it. .kiwi.nz is at the same level as .co.nz. Also on the same level as .com.au.
.co.nz has been around a lot longer; as I mentioned I wouldn't be surprised if Weebly are incorrectly parsing the .kiwi.nz domains when they're trying to match them to a root domain on file.
I'm 70% sure this will be a bug in their platform as it's happening at that level.
|
![]() ![]() ![]() |