Jump to content

Search the Community

Showing results for tags 'dns settings'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Welcome to ProcessWire
    • News & Announcements
    • Showcase
    • Wishlist & Roadmap
  • Community Support
    • Getting Started
    • Tutorials
    • FAQs
    • General Support
    • API & Templates
    • Modules/Plugins
    • Themes and Profiles
    • Multi-Language Support
    • Security
    • Jobs
  • Off Topic
    • Pub
    • Dev Talk

Product Groups

  • Form Builder
  • ProFields
  • ProCache
  • ProMailer
  • ProDrafts
  • ListerPro
  • ProDevTools
  • Likes
  • Custom Development

Categories

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 1 result

  1. Hi Guys, I wanted to reach to everyone in the community to see if someone has come across this issue. We have a client that had a website built in PHP. We provided our client with a new website built on ProcessWire. Our client has their domain name registered with register.com and their old website was built by another developer who was hosting the website in a virtual server at gandi.net. The DNS settings were as follows: Domain name was pointed to the gandi.net in order to display the website files. The MX records were pointed to Google servers for company emails. The Name servers were as is which is the stock register.com name servers. We were not able to speak with the old developer to setup a time to update the files so we were asked by our client to move forward without contacting the old developer. How we setup the new website: In order to avoid down time of the email accounts and not having to setup new MX records on another host, we simply setup our clients new website on GoDaddy shared hosting and changed the A record in their register.com DNS settings to point to the new hosting account. Basically, an IP change. Everything else they had stayed the same, meaning we did not change the MX records and we did not change the name servers. Here is the issue: Some website visitors are seeing the new website, some are seeing the old website. We first thought it was due to browser caching or the propagation did not fully complete when they tried to visit the website. After telling our client to wait until the new DNS settings or try to clear their cache, we thought they were all good to go. Now our client is contacting us saying that the issue is still happening. So we contacted register.com and had them resubmit the new DNS settings again, basically the same IP change we did. Result: Some users are still seeing the old website on certain routers. We are also seeing the old website on certain routers we use and the new site on other routers. Can anyone provide some guidance? Has anyone seen this issue before? We even pinged the website and it shows the correct server, we also used whatsmydns.net to see what the site is coming up as across the world and we also see the correct server. Lastly, we sent the url to our partners in Germany and they see the new website and not the old one. This is honestly the oddest issue I have seen and unsure as to why this is going on? Here is our clients site: medstarlab.com
×
×
  • Create New...