discuss Help! DNS problem nobody seems to have answer to

[xn--v4h.com]

We own xn--e5h.com (venus symbol) and for whatever reason our DNS is producing spotty connections: https://dnschecker.org/#A/xn--e5h.com
Not sure if the problem is with Google (and a few others) or with Godaddy (where the domain is) or something else. All I know is NOBODY can identify the problem and where it is. Can any one of you help? Thanks!

See more: https://twitter.com/PeaceSymbol_Com/status/884379506890420224

@Grilled copying you since you might have an idea?

 

[namesilo]

Your problem is very likely that the two name servers in use by your domain (NS75.DOMAINCONTROL.COM and NS76.DOMAINCONTROL.COM) are each handing out a different IP when queried for your domain. See the DIG results below for proof. In short, NS75.DOMAINCONTROL.COM is handing out 184.168.221.2 while NS76.DOMAINCONTROL.COM is handing out 50.63.202.5. My advice is to show the DIG results below to Godaddy and ask why their 2 name servers are handing out different IPs as this is very uncommon and typically indicative of a problem.

Regarding which IP to use, 199.34.228.55 is an IP from Weebly's system (they have several IPs). You will want to ask Weebly which IP is correct for you since I believe only certain IPs are used for https if you require that and have it configured.

Here are the dig results:

dig a xn--e5h.com @NS75.DOMAINCONTROL.COM

; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.62.rc1.el6_9.4 <<>> a xn--e5h.com @NS75.DOMAINCONTROL.COM
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32871
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;â.com. IN A

;; ANSWER SECTION:
â.com. 600 IN A 184.168.221.2

;; AUTHORITY SECTION:
â.com. 3600 IN NS ns76.domaincontrol.com.
â.com. 3600 IN NS ns75.domaincontrol.com.

-------------------------------------------------

dig a xn--e5h.com @NS76.DOMAINCONTROL.COM

; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.62.rc1.el6_9.4 <<>> a xn--e5h.com @NS76.DOMAINCONTROL.COM
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29986
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;â.com. IN A

;; ANSWER SECTION:
â.com. 600 IN A 50.63.202.5

;; AUTHORITY SECTION:
â.com. 3600 IN NS ns76.domaincontrol.com.
â.com. 3600 IN NS ns75.domaincontrol.com.

 

[Dmytro]

You have a DS record (needed for DNSSEC). Right now domain xn--e5h.com has NS:

ns75.domaincontrol.com
ns76.domaincontrol.com

These NS have zone xn--e5h.com on it and return RR records (A, MX). But the domain doesn't resolve right now because you also have DS record which is not properly configured. Try to delete this DS record.

Here the article how you can add DS, try to delete it in the same place - https://ua.godaddy.com/help/add-a-ds-record-23865

Updating domain records takes about 24 hours.

 

[Jurgen Wolf]

So what is your problem, a few and different A-records (IPs)???
No any issue here... this is normal and used for the load balancing purposes...

 

[xn--v4h.com]

You have a DS record (needed for DNSSEC). Right now domain xn--e5h.com has NS:

ns75.domaincontrol.com
ns76.domaincontrol.com

These NS have zone xn--e5h.com on it and return RR records (A, MX). But the domain doesn't resolve right now because you also have DS record which is not properly configured. Try to delete this DS record.

Here the article how you can add DS, try to delete it in the same place - https://ua.godaddy.com/help/add-a-ds-record-23865

Updating domain records takes about 24 hours.

Man, you are supremely brilliant. Thank you again!

You have a DS record (needed for DNSSEC). Right now domain xn--e5h.com has NS:

ns75.domaincontrol.com
ns76.domaincontrol.com

These NS have zone xn--e5h.com on it and return RR records (A, MX). But the domain doesn't resolve right now because you also have DS record which is not properly configured. Try to delete this DS record.

Here the article how you can add DS, try to delete it in the same place - https://ua.godaddy.com/help/add-a-ds-record-23865

Updating domain records takes about 24 hours.

Want to let you know this WORKED!!! Didn't have to wait 24 hours, just a few minutes. Thank you so much. You solved something that so many people have flat out couldn't figure out.

Thanks so much everyone for your trying to help. You guys continue to amaze me.

 

[Lox]

check for dns soa problems https://mxtoolbox.com/domain/xn--e5h.com/

 

[Jurgen Wolf]

You may also use intodns.com for the detailed report...

 

[Lox]

did you properly setup forward or mask your domain

 

[Lox]

check GD https://www.godaddy.com/help/manually-forward-or-mask-your-domain-422

 

[Jurgen Wolf]

GoDaddy just rotates many IPs...
That's why you see these so-called by you "spotty connections"...

 

[Jurgen Wolf]

If you want the stable connections - buy the dedicated IP...

 

[Jurgen Wolf]

Also you may try another DNS-provider:
NS1.com
CloudNS.net
etc.

 

[Chris Hydrick]

Sonshi.com is business class, which Venus symbol is being forwarded to. So do I use (for example) 199.34.228.55 provided from Godaddy -or- my special IP address provided from Weebly to set up the forward from Godaddy?

Ahhh - the saga continues!

I assume you can use the 199 addresses. This assumption is based off not seeing custom IP's for properly forwarding URLS.org and Peace Symbol. Peace Symbol uses Moniker Weebly IP and URLs uses Google Weebly IP. Thus, the assumption to go ahead and use GoDaddy Weebly IP (If you haven't already)

If that doesn't work, try the IP given to you in Weebly settings.... Mind you the update can supposedly take 24-48 hours.

 

[Jurgen Wolf]

@namesilo
As I already said, these (and many other) IPs are in permanent rotation by GoDaddy...
And such behaviour is common in terms of load balancing...

 

[Chris Hydrick]

Your problem is very likely that the two name servers in use by your domain (NS75.DOMAINCONTROL.COM and NS76.DOMAINCONTROL.COM) are each handing out a different IP when queried for your domain. See the DIG results below for proof. In short, NS75.DOMAINCONTROL.COM is handing out 184.168.221.2 while NS76.DOMAINCONTROL.COM is handing out 50.63.202.5.

I suspected a NameServer error at first, but then realized OP had changed NS several times to GoDaddy Defaults.

@xn--v4h.com Did you try adding either your custom Weebly IP or the 199 IP to your A Host as previously mentioned?

 

[Jurgen Wolf]

Because ~99% of people don't use DNSSEC and don't think about it...

 

[xn--v4h.com]

Because ~99% of people don't use DNSSEC and don't think about it...

And then there's the .01% who use it but don't know what the hell it is (me!)

 

[xn--v4h.com]

@Joe Styler Do you have an answer to our problem? I've placed 3 calls into Godaddy and every time they say they can connect from Arizona but when I explained that it's not connecting everywhere they simply didn't understand what I was talking about.

 

[Lox]

Quite of ISPs ignores time period (DNS TTL). So cached record getting updated every two to three days.

 

[xn--v4h.com]

Quite of ISPs ignores time period (DNS TTL). So cached record getting updated every two to three days.

It has been three WEEKS.

 

[xn--v4h.com]

check for dns soa problems https://mxtoolbox.com/domain/xn--e5h.com/

Thanks, yes there are problems but there is zero answer as to why much less a solution.

 

[xn--v4h.com]

You may also use intodns.com for the detailed report...

Thanks, this report says all I'm missing is an MX record but the issue goes beyond that. Perhaps I'm wrong.

 

[xn--v4h.com]

So what is your problem, a few and different A-records (IPs)???
No any issue here... this is normal and used for the load balancing purposes...

Is this normal? http://www.isitdownrightnow.com/xn--e5h.com.html

 

[xn--v4h.com]

check GD https://www.godaddy.com/help/manually-forward-or-mask-your-domain-422

Yes I tried that and manually inserted the IP. Didn't work.

 

[xn--v4h.com]

Told you guys, not so simple, sorry! Google's not responding, Godaddy's not responding. It's ridiculous.