Skip to main content
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Samnz
Getting Started

Issues with setting up DNS

Hi,

 

got a bit tired calling godday! after 3 times calling looks like those phone operator looking to add more minutes on my mobile! they talk about any nonsense which I don't know why! only killing minutes and minutes! 

first time called took 58 minutes and they could not fix it, tomorrow same! 

 

paid for all my hosting per year $180 total but now for twice call nearly more than that as their 0800 does not accept mobile phone in NZ. 

 

now what's happen after setting up the site and off-site dns still I've to type my site without www. and if I add the www. at the begin it does not show anything!

6 REPLIES 6
charminglygeeky
Employee

Hi @Samnz,

Welcome to our forums! We appreciate your feedback. Based on the information you have provided, it sounds like your 'www' CNAME record is incorrect. You will want to make sure that your 'www' CNAME is set to @, here is how to change the record. 

KayJay - GoDaddy | Community Moderator
24/7 support available at x.co/247support

Many thanks, finally someone break the silence of the lamps! it will be appreciate if you simply type in here what I put as CNAME or A record.

for your more information I have already have a CNAME as follow I put in the photo attached, but as it comes with internal server error I put in A recored as 

 

www          ip-address 

 

now I get below:

500 Internal Privoxy Error

Privoxy encountered an error while processing your request:

Could not load template file no-such-domain or one of its included components.

Please contact your proxy administrator.

If you are the proxy administrator, please put the required file(s)in the (confdir)/templates directory. The location of the (confdir) directory is specified in the main Privoxy config file. (It's typically the Privoxy install directory).

the image is what it used to be in my CNAME record but as explain now I change that to A record.

 

Hey @Samnz,

 

Based on the new info so far, I'm not completely sure if the error is DNS related or something else on the hosting side you're pointing the domain name to. If you'd like to get some more suggestions from some of our knowledgeable members here on how to address this, it may help to know some more details. 

 

 

First, what is the domain name you're running into these issues with? Are you hosting with us? If you are, what type of hosting plan? 

 

If the issue is hosting related, a 500 error is usually script related. If the hosting is on our end, it may help to check the error logs for the specific cause of the error message. 

 

Keep us posted if you manage to get this worked out on your own. 

 

CG - GoDaddy | Community Moderator
24/7 support available at x.co/247support
Samnz
Getting Started

Hi,

 

many thanks, I just spent anothe 20 minutes on the phone with your tech and they give me another unsatisfactory reply! firstly domain is xyten.com and it works but if you type www.xyten.com it comes with all error that I explained. 

for your more information my A record used to be like that:

@          166.62.10.184             600 seconds

mail       166.62.10.184             600 seconds

 
but after your tech refer to my registrar company in NZ (domain is off site) although I know it's not related to them because the xyten.com works so dsn is fine, only the CNAME something wrong or cropted. anyway I call the registrar company in NZ and they said oh, DNS is not running by us! you should fix it there but maybe put your www as A record! so I did and now have one more line below A record as attached photo
 
Samnz
Getting Started

anyone could find the problem? I even use some DNS test tool and below is the result:

Begin testing zone www.xyten.com with version 1.3.0.

Delegation

Begin testing delegation for www.xyten.com.

Name servers listed at parent: mns01.domaincontrol.com,mns02.domaincontrol.com

Name servers listed at child: mns01.domaincontrol.com,mns02.domaincontrol.com

Nameserver

Done testing delegation for www.xyten.com.

Begin testing name server mns01.domaincontrol.com.

Begin testing host mns01.domaincontrol.com.

Begin testing address 216.69.185.31.

Done testing address 216.69.185.31.

Begin testing address 2607:f208:206:0:0:0:0:1f.

Done testing address 2607:f208:206:0:0:0:0:1f.

Done testing host mns01.domaincontrol.com.

Name server mns01.domaincontrol.com (216.69.185.31) answers queries over UDP.

Name server mns01.domaincontrol.com (216.69.185.31) answers queries over TCP.

Name server mns01.domaincontrol.com (216.69.185.31) is not recursive.

Name server mns01.domaincontrol.com (216.69.185.31) authoritative for www.xyten.com.

Name server mns01.domaincontrol.com (216.69.185.31) closed for zone transfer of www.xyten.com.

No answer received from 216.69.185.31 when querying for hostname.bind/CH/TXT.

No answer received from 216.69.185.31 when querying for version.bind/CH/TXT.

No answer received from 216.69.185.31 when querying for id.server/CH/TXT.

No answer received from 216.69.185.31 when querying for version.server/CH/TXT.

IPv6 disabled - will not test name server at 2607:f208:206:0:0:0:0:1f

Done testing name server mns01.domaincontrol.com.

Begin testing name server mns02.domaincontrol.com.

Begin testing host mns02.domaincontrol.com.

Begin testing address 208.109.255.31.

Done testing address 208.109.255.31.

Begin testing address 2607:f208:302:0:0:0:0:1f.

Done testing address 2607:f208:302:0:0:0:0:1f.

Done testing host mns02.domaincontrol.com.

Name server mns02.domaincontrol.com (208.109.255.31) answers queries over UDP.

Name server mns02.domaincontrol.com (208.109.255.31) answers queries over TCP.

Name server mns02.domaincontrol.com (208.109.255.31) is not recursive.

Name server mns02.domaincontrol.com (208.109.255.31) authoritative for www.xyten.com.

Name server mns02.domaincontrol.com (208.109.255.31) closed for zone transfer of www.xyten.com.

No answer received from 208.109.255.31 when querying for hostname.bind/CH/TXT.

No answer received from 208.109.255.31 when querying for version.bind/CH/TXT.

No answer received from 208.109.255.31 when querying for id.server/CH/TXT.

No answer received from 208.109.255.31 when querying for version.server/CH/TXT.

IPv6 disabled - will not test name server at 2607:f208:302:0:0:0:0:1f

Done testing name server mns02.domaincontrol.com.

Consistency

Begin testing zone consistency for www.xyten.com.

SOA at address 208.109.255.31 has serial 2016100306.

SOA at address 216.69.185.31 has serial 2016100306.

All SOA records have consistent serial numbers.

All SOA records are consistent among all name servers.

Done testing zone consistency for www.xyten.com.

SOA

Begin testing SOA parameters for www.xyten.com.

Found SOA record for www.xyten.com.

Begin testing host mns01.domaincontrol.com.

Begin testing address 216.69.185.31.

Done testing address 216.69.185.31.

Begin testing address 2607:f208:206:0:0:0:0:1f.

Done testing address 2607:f208:206:0:0:0:0:1f.

Done testing host mns01.domaincontrol.com.

SOA MNAME for www.xyten.com valid (mns01.domaincontrol.com).

SOA MNAME for www.xyten.com (mns01.domaincontrol.com) listed as NS.

SOA MNAME for www.xyten.com (mns01.domaincontrol.com) is authoritative.

IPv6 disabled - will not query SOA MNAME at 2607:f208:206:0:0:0:0:1f

Begin testing email address dns@jomax.net.

Mail exchangers for dns@jomax.net found smtp.secureserver.net,mailstore1.secureserver.net.

Begin testing host smtp.secureserver.net.

Begin testing address 68.178.213.203.

Done testing address 68.178.213.203.

Done testing host smtp.secureserver.net.

Begin testing mail server smtp.secureserver.net (68.178.213.203) with dns@jomax.net.

SMTP banner: *********************************************************************

SMTP testing of smtp.secureserver.net (68.178.213.203) with dns@jomax.net succeeded without errors.

Done testing mail server smtp.secureserver.net (68.178.213.203) with dns@jomax.net.

Begin testing host mailstore1.secureserver.net.

Begin testing address 68.178.213.243.

Done testing address 68.178.213.243.

Done testing host mailstore1.secureserver.net.

Delivery over IPv4 to dns@jomax.net ok.

Delivery over IPv6 to dns@jomax.net could not be done.

Done testing email address dns@jomax.net.

Successful attempt to deliver email for SOA RNAME of www.xyten.com (dns.jomax.net) using dns@jomax.net.

SOA TTL for www.xyten.com too small (600) - recommended >= 3600.

SOA refresh for www.xyten.com OK (28800) - recommended >= 14400.

SOA retry for www.xyten.com OK (7200) - recommended >= 3600.

SOA expire for www.xyten.com OK (604800) - recommended >= 604800.

SOA minimum for www.xyten.com OK (600) - recommended between 300 and 86400.

Done testing SOA parameters for www.xyten.com.

Connectivity

Begin testing connectivity for www.xyten.com.

Name server 208.109.255.31 announced by: 26496

Name server 216.69.185.31 announced by: 26496

Zone announced by ASN: 26496

Zone announced by only one ASN (1).

Name server 2607:f208:0302:0000:0000:0000:0000:001f announced over IPv6 by: 26496

Name server 2607:f208:0206:0000:0000:0000:0000:001f announced over IPv6 by: 26496

Zone announced by IPv6 ASN: 26496

Zone announced by only one IPv6 ASN (1).

Done testing connectivity for www.xyten.com.

DNSSEC

Begin testing DNSSEC for www.xyten.com.

Did not find DS record for www.xyten.com at parent.

Servers for www.xyten.com have consistent extra processing status.

Did not find DNSKEY record for www.xyten.com at child.

No DNSKEY(s) found at child, other tests skipped.

Done testing DNSSEC for www.xyten.com.

Test completed for zone www.xyten.com.

Hi,

 

it's almost a year that I called your support line, test online, post msg and still after nearly a year it's not fix! 

it happened so far I could passed all barrier and automated phone answering system on godaddy and talk to a tech and silly me believed them this time fix!

last time I talk to a tech a day before and he said the same! and said I've fix it.

 

anyway that we could get refund and just go to another hosting? 

I can't spend each time over an hour on the phone from overseas to see if I can talk to someone.

 

I strongly recommend none US customer make sure their considering this support line.

 

right now it's nearly 45min I'm on the line while typing this post! 😞