A-Record Change, Short Term Fix - Forwarding to New Server

We recently had a new website developed.  The developer is hosting the revampped site on a different web-server with a different IP address.  We made the A-record change about 30 hours ago but it doesnt looks like it has fully propogated yet.  

2 questions -
Is there a short term fix the developer could setup by forwarding requests from to the old server IP to the new web-server?

Are there any utilities/web-sites I can use to check the status of the A-record propogation?

Thanks!
MohonkAsked:
Who is Participating?
 
fosiul01Commented:
you can check all the dns query here


http://www.intodns.com/mohonk.com

you need to speak with the Dns provider on this issue


bellow is SOA record

The SOA record is:
Primary nameserver: cbru.br.ns.els-gms.att.net
Hostmaster E-mail address: rm-hostmaster.ems.att.com
Serial #: 7
Refresh: 10800
Retry: 3600
Expire: 604800   1 weeks
Default TTL: 86400


its looks like serial  number is same on both server..

i will advise to speak with provider and ask them why it h as not update yet.

it could be the intrface you trying it actually does not work ( i would not think that.. but you know problem can happen)
0
 
fosiul01Commented:
We made the A-record change about 30 hours   :

A record change should not take that long.. but if Dns provider set long time in SOA record then it might take very long.

go to this site

squish.net

check the A record of that domain

and tell me what you see the time under

www.domain.      60      IN      A      78.22.66.44

0
 
MohonkAuthor Commented:
Results
 
50.0% Answered from cmtu.mt.ns.els-gms.att.net (12.127.16.69)
www.mohonk.com.      86400      IN      A      66.23.99.13
 

50.0% Answered from cbru.br.ns.els-gms.att.net (199.191.128.105)
www.mohonk.com.      86400      IN      A      66.23.99.13


66.23.99.13 is the OLD IP.
0
Cloud Class® Course: Ruby Fundamentals

This course will introduce you to Ruby, as well as teach you about classes, methods, variables, data structures, loops, enumerable methods, and finishing touches.

 
xtermCommented:
Both of the authoritative servers for mohonk.com below return the old IP with a full 86400 TTL:

;; AUTHORITY SECTION:
mohonk.com.             86400   IN      NS      cbru.br.ns.els-gms.att.net.
mohonk.com.             86400   IN      NS      cmtu.mt.ns.els-gms.att.net.

Your A record has not been changed.

You can't use a .htaccess access redirect to send the users to the new site unless it can be accessed by IP, or a different name, because obviously the clients are caching the old A lookup if they get to the new site.
0
 
xtermCommented:
FYI, 86400 = 24 hrs, so if you made it 30 hrs ago, either you or the provider probably forgot to update the serial # in the zone.
0
 
MohonkAuthor Commented:
We dont have the option in the registrar page to update a serial #.  What exactly is that?  We can open a ticket with the registrar to ask.
0
 
xtermCommented:
It looks like your domain name is hosted by activeregistrar - I've never used them, so I don't know what their web interface looks like.  But in DNS server zone files or databases (that is what is actually stored by your registrar that you don't see) they have a serial number which needs to be incremented to at least one number higher when changes are made.  This signals the DNS server that the zone needs to be reloaded when the server reloads (and also signals the secondary server to re-transfer the zone)

Do you see any field anywhere that flags the zone to be reloaded?
0
 
MohonkAuthor Commented:
For some reason our initial A-Record change did not work.  The registrar had to re-apply it.

Thanks for all the help!
0
 
xtermCommented:
That is exactly what I told you in comment #37250323 above.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.