Godaddy Domain Forwards Are Not Resolving for SONIC Users

Web hosting discussion, programming, and shared and dedicated servers.
7 posts Page 1 of 1
by yronwode » Wed Nov 13, 2019 4:54 pm
Hi there! I have had domains registered at Godaddy.com for years and set up forwards to domains hosted at Sonic.net for years, properly, and until just the last few months these have worked fine for us.

Sometime recently, however, people in my local area network informed me that these domains (which we use for customer service, as easy-to-say-on-the-phone browser directions) no longer resolved to their target, and with some research (asking people at Godaddy, then various friends throughout the world) i found out that only SONIC.NET techs and people in my LAN (also dependent upon Sonic's lookup) were unable to get them to resolve properly.

I also tested other forwards set up at Godaddy and hosted at Sonic and i found out that i had the same browser problem (tried more than one browser too) where it would hang and never resolve, despite the fact that i could analyze it through sites like http://www.whatsmydns.net and http://digwebinterface.com showing up as targetting and resolving consistently to an IP which i could not myself thereafter get to, even though i could get to the targets when putting them into my URL bar directly.

Here are three of the domains i'm talking about (i presume the problem isn't domain-specific, however, but somehow related to forwarding in general or just between Sonic.net and Godaddy.com):

http://www.rootworkers.com
resolves to http://www.readersandrootworkers.org

http://www.candleministry.org
resolves to http://www.missionaryindependent.org/candle-services.html

and
http://www.conjurecandles.net
resolves to http://www.candlesandcurios.com

The second domain is complicated by the fact that at some point in time i think we had hosting for it and it had a re-direct to the page in question. I suspect we do NOT need this DNS-Only-with-redirect if we are just forwarding from a registration at Godaddy (and i will discontinue it, if so).

Thank you for your help in advance,
by joemuller » Thu Nov 14, 2019 1:04 pm
Hi Nagasiva,

Each of those 3 domains are (at least initially) pointed at IP address 184.168.131.241, which is a virtual IP that GoDaddy uses for their redirect services. You are also correct about candleministry.org still having DNS with a redirect set up - that may be causing some issues, so I've removed it for you on Sonic's side.

There are two tools that are useful for tracking down issues with redirect behavior - the first is URLvoid's HTTP Response Headers tool. Using the header tool, you can see where any simple redirects are taking place (see the 'Location:' part). If you're comfortable with command-line tools, you can get the same data using 'curl' -- here's an example with conjurecandles.net:

Code: Select all

# curl -I -L conjurecandles.net
HTTP/1.1 301 Moved Permanently
Server: nginx/1.12.2
Date: Thu, 14 Nov 2019 20:58:58 GMT
Content-Type: text/html; charset=utf-8
Connection: close
Location: http://www.candlesandcurios.com

HTTP/1.1 200 OK
Date: Thu, 14 Nov 2019 20:58:58 GMT
Server: Apache/1.3.41 (Unix) mod_auth_pam/1.1.1 FrontPage/5.0.2.2635 PHP/4.4.9
Last-Modified: Wed, 16 Jan 2013 06:58:25 GMT
ETag: "e5517d-1e5e-50f64f91"
Accept-Ranges: bytes
Content-Length: 7774
Content-Type: text/html


I was able to get all 3 domains to load correctly (including the expected redirect behavior) on my workstation (which is using Sonic's DNS (resolver) servers. If you're still seeing some odd behavior, try pulling up a new window/tab and toggling developer mode in your web browser (usually the F12 key) and look at the Network tab, then navigate to the site directly via the address/URL bar - you should see a 301 or 302 response as one of the first entries in the network activity.

Hope this helps you track down the issue - feel free to post a reply or private message if the problem persists.

-- Joe M
I'm a proud employee of Sonic.net! :-)
by yronwode » Fri Nov 15, 2019 3:50 pm
Hi Joe,

I am unsure how my activities might assist matters as long as your Sonic.net Tech Support personnel with whom i am chatting also cannot get to the sites as redirects or forwards. For many years previous to now i had no problems with it and neither did the tech support personnel at Sonic.net.

Godaddy personnel have no difficulty getting to the target domains. I thought perhaps they were the problem, but then my friends in different parts of the world also had no problems, so it appears to be restricted to just me and Sonic.net.

I don't see how your instructions in the above help me to fix my problem of properly getting to the targets involved. Perhaps i'm missing something. I just (again) completely cleared my Firefox cache and cookies and reset it so as to dump its history of sites and attempted to get to http://www.rootworkers.com and it still hung indefinitely.

Are you saying that i should be able to fix this here on my computer without your help to do something in the background and that if i contacted Tech Support again they'd be able to get to the site whereas previously they could not? Perhaps i need explicit instructions. I am somewhat confused. Thanks!
by sysops » Fri Nov 15, 2019 4:58 pm
They all redirect fine for me on Sonic's network. Problem solved? Try clearing your browser cache, they're notorious for caching old redirects.

Code: Select all

curl -Lv http://www.rootworkers.com
* Rebuilt URL to: http://www.rootworkers.com/
*   Trying 184.168.131.241...
* TCP_NODELAY set
* Connected to www.rootworkers.com (184.168.131.241) port 80 (#0)
> GET / HTTP/1.1
> Host: www.rootworkers.com
> User-Agent: curl/7.58.0
> Accept: */*
>
< HTTP/1.1 301 Moved Permanently
< Server: nginx/1.12.2
< Date: Sat, 16 Nov 2019 01:02:25 GMT
< Content-Type: text/html; charset=utf-8
< Transfer-Encoding: chunked
< Connection: close
< Location: http://www.readersandrootworkers.org
<
* Closing connection 0
* Issue another request to this URL: 'http://www.readersandrootworkers.org'
* Rebuilt URL to: http://www.readersandrootworkers.org/
*   Trying 209.204.175.65...
* TCP_NODELAY set
* Connected to www.readersandrootworkers.org (209.204.175.65) port 80 (#1)
> GET / HTTP/1.1
> Host: www.readersandrootworkers.org
> User-Agent: curl/7.58.0
> Accept: */*
>
< HTTP/1.1 301 Moved Permanently
< Date: Sat, 16 Nov 2019 01:02:26 GMT
< Server: Apache/1.3.41 (Unix) mod_auth_pam/1.1.1 FrontPage/5.0.2.2635 PHP/4.4.9
< Cache-Control: private, must-revalidate, max-age=0
< Expires: Thu, 01 Jan 1970 00:00:00 GMT
< Vary: Accept-Encoding,Cookie
< X-Powered-By: PHP/5.2.11
< X-Vary-Options: Accept-Encoding;list-contains=gzip,Cookie;string-contains=yronwode_mw_mediawiki_Token;string-contains=yronwode_mw_mediawiki_LoggedOut;string-contains=yronwode_mw_mediawiki__session
< Last-Modified: Sat, 16 Nov 2019 01:02:26 GMT
< Location: http://www.readersandrootworkers.org/wiki/Association_of_Independent_Readers_and_Rootworkers
< Transfer-Encoding: chunked
< Content-Type: text/html; charset=utf-8
<
* Ignoring the response-body
* Connection #1 to host www.readersandrootworkers.org left intact
* Issue another request to this URL: 'http://www.readersandrootworkers.org/wiki/Association_of_Independent_Readers_and_Rootworkers'
* Found bundle for host www.readersandrootworkers.org: 0x5595d8cb8a50 [can pipeline]
* Re-using existing connection! (#1) with host www.readersandrootworkers.org
* Connected to www.readersandrootworkers.org (209.204.175.65) port 80 (#1)
> GET /wiki/Association_of_Independent_Readers_and_Rootworkers HTTP/1.1
> Host: www.readersandrootworkers.org
> User-Agent: curl/7.58.0
> Accept: */*
>
< HTTP/1.1 200 OK
Proud Sonic customer since 1999. Ask me about internet privacy, VPN, anonymity and security.
by yronwode » Sat Nov 16, 2019 5:13 pm
I cleared my Firefox cache and tried again and still no luck.

Weird that you can use it now but i still cannot.
by yronwode » Fri Dec 06, 2019 10:40 pm
Odd, it took a bit of time, but now these are resolving perfectly as before. I did not go through and purge all the caches or browser histories, but i did talk with your Customer Service and they reset Sonic's settings in a way i don't understand. Whatever took place, or whatever you did as a whole resolved the matter within a week for all of the domains, and i'm grateful.

Thanks!
by yronwode » Tue Jun 09, 2020 12:39 pm
And today they are again not resolving. I checked with folks outside my network and everybody but my LAN cannot get this domain to resolve properly:

http://www.candleministry.com

This despite my cache clearing (Chrome 83.0.4103.97: OSX 10.10.5; Dual-Fusion)

Any ideas?
7 posts Page 1 of 1

Who is online

In total there are 2 users online :: 1 registered, 0 hidden and 1 guest (based on users active over the past 5 minutes)
Most users ever online was 700 on Thu Jun 18, 2020 12:00 pm

Users browsing this forum: Bing [Bot] and 1 guest