I know the A record was on the old Nameserver because the website worked (including ping, etc...)?
On the new Nameserver (i.e. in the GoDaddy interface) I could see the A record and I didn't change anything when they did their "refresh". ?I after I changed GoDaddy's DNS records for the domain, their system didn't send out the right info to the Authoritative Server until I had them do the manual refresh. ?I don't think it was a propagation problem like they said.
I think my real questions are:
- When a DNS cache server needs to pull new records, does it pull individual record types like all the MX records but not the A records, or does it pull all the DNS records? ?(My theory is that it would pull all)
- If you change the Nameservers for a domain name is it fair to say that you would either get the old A records or the new ones and not have missing records? Since the new DNS info would replace the old, I don't see how the system would come back with a "missing" record, unless the new information sent to the Authoritative server was messed up.
Does that make sense?
Click and Create
Ranked by the Houston Business Journal as
"One of the Largest Web Design Firms in Houston"
2400 Augusta Ste 369
Houston, TX 77057
On Sun, Dec 12, 2010 at 6:38 PM, Lester <[address removed]>
I would wonder what evidence you have that the new A record was ever
there? ?For example, maybe you entered it into a web form but forgot to
press the "save" button, or the save action was silently lost.
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
This message was sent by Lester ([address removed]) from The Houston Web Technology Meetup Group.
To learn more about Lester, visit his/her member profile: http://www.meetup.com/webtechnologydesign/members/3928603/
To unsubscribe or to update your mailing list settings, click here: http://www.meetup.com/webtechnologydesign/settings/
Meetup, PO Box 4668 #37895 New York, New York[masked] | [address removed]