Skip to content

Instantly share code, notes, and snippets.

@jwigal
Created December 3, 2015 15:36
Show Gist options
  • Save jwigal/795777fd84063ba66d39 to your computer and use it in GitHub Desktop.
Save jwigal/795777fd84063ba66d39 to your computer and use it in GitHub Desktop.

Issue with 1and1 account: our website uses 1and1 to host DNS, but we host the website itself on another server.

When I navigate to the website (firetrainingunlimited.com) the site was showing up as a 1and1 domain landing page.

Customer support technician says that it looks fine to him, the page was coming up correctly without a landing page.

They ask me to dump my cache, clear cookies, and restart my computer. No resolution. Same issue happening on multiple computers, and multiple devices.

1and1 control panel that allows me to manage the domain is not working, and is throwing a 500 error.

I indicate that it looks like a DNS issue. I'm seeing a long IPv6 IP address when I use curl on the command line.

I'm also seeing headers that indicate the page is being served by Apache, we use nginx.

I ask technican to look at DNS, he indicates that it is pointing at the correct IPv4 address.

I was asked to restart my computer a second time, at which time I asked to speak to a supervisor. This never happened.

After 40 minutes I end the call, come back later that evening to look at the control panel and DNS settings.

When I looked, it appears that the "A" record is pointing at the correct server, but there is an "AAAA" record that is still pointing at the 1and1 landing page server. I was on an IPv6 network, which is why I was seeing the problem, and he wasn't.

The agent should have seen the AAAA record and noticed that it was pointing at 1and1 rather than our server.

I removed the AAAA record, but this should have been resolved on the call rather than me trying to figure it out on my own.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment