IP address for A record not updating

#1
I am trying to change the hosting for our website. I have edited the www A record from the IP address of the old host to that of the new host. However, when I check with whatsmydns.net it still shows the IP address of the old host and the site has not updated to the new one. This has been over 24 hours now. Zoneedit checks show the new host IP address. Any ideas why this has not propagated so that I can access the new site on my new host? Thanks for any advice!
 

sandy neal

Administrator
Staff member
#4
this is the correct IP yes?

dig @ns4.zoneedit.com a www.serveafghanistan.org

; <<>> DiG 9.8.3-P1 <<>> @ns4.zoneedit.com a www.serveafghanistan.org


; (1 server found)

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34862

;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; WARNING: recursion requested but not available


;; QUESTION SECTION:

;www.serveafghanistan.org. IN A

;; ANSWER SECTION:


www.serveafghanistan.org. 300 IN A 185.119.173.105


it looks good at https://www.whatsmydns.net/#A/www.serveafghanistan.org as well.


the IP for the root domain will be 198.199.92.59 as its going through our URL forwarding server.

it appears to be a web server issue and a redirect loop.

wget www.serveafghanistan.org


--2018-12-06 14:25:16-- http://www.serveafghanistan.org/


Resolving www.serveafghanistan.org (www.serveafghanistan.org)... 185.119.173.105


Connecting to www.serveafghanistan.org (www.serveafghanistan.org)|185.119.173.105|:80... connected.


HTTP request sent, awaiting response... 301 Moved Permanently


Location: http://serveafghanistan.org/ [following]


--2018-12-06 14:25:18-- http://serveafghanistan.org/


Resolving serveafghanistan.org (serveafghanistan.org)... 198.199.92.59


Connecting to serveafghanistan.org (serveafghanistan.org)|198.199.92.59|:80... connected.


HTTP request sent, awaiting response... 302 Found


Location: http://www.serveafghanistan.org [following]


--2018-12-06 14:25:18-- http://www.serveafghanistan.org/


Connecting to www.serveafghanistan.org (www.serveafghanistan.org)|185.119.173.105|:80... connected.


HTTP request sent, awaiting response... 301 Moved Permanently


Location: http://serveafghanistan.org/ [following]


--2018-12-06 14:25:18-- http://serveafghanistan.org/


Reusing existing connection to serveafghanistan.org:80.


HTTP request sent, awaiting response... 302 Found


Location: http://www.serveafghanistan.org [following]


--2018-12-06 14:25:18-- http://www.serveafghanistan.org/


Connecting to www.serveafghanistan.org (www.serveafghanistan.org)|185.119.173.105|:80... connected.


HTTP request sent, awaiting response... 301 Moved Permanently


Location: http://serveafghanistan.org/ [following]


--2018-12-06 14:25:19-- http://serveafghanistan.org/


Reusing existing connection to serveafghanistan.org:80.


HTTP request sent, awaiting response... 302 Found


Location: http://www.serveafghanistan.org [following]


--2018-12-06 14:25:19-- http://www.serveafghanistan.org/


Connecting to www.serveafghanistan.org (www.serveafghanistan.org)|185.119.173.105|:80... connected.
 
#9
All solved. The issue was that the domain was constantly redirecting between the non-www and the www version of the domain, which was causing the infinite loop.
 

sandy neal

Administrator
Staff member
#12
you would delete the URL forward for
serveafghanistan.org
and create a Host A record for it pointing to the IP.... thats the DNS side of things everything else is done on your web sever side...
 
Top