DNS Redirection issue
Well, I am lost... I was trying to transfer my WordPress server (on Ubuntu 18.04) from Azure to AWS. I used ManageWP to do this, but had issues with logging in. So I created a new blank WordPress server that I named dev.mydomain.com. and successfully cloned the server.
I then wanted to remove the "dev." entry in DNS and just use my "www." name. There are three A records in my DNS zone that point to my server: "www", "*" and "@".
But regardless of which browser I use or browser cache I flush I keep getting redirected to "dev.mydomain.com". I am pretty certain that this is a server or DNS issue. I have gone to the extent of deleting the WordPress content and creating a static html file for the server. It's just a standard .htaccess file for WordPress with no obvious redirects in it, and I deleted it for the static page.
Even when I point my DNS back to the Azure servers the "dev." keeps coming back. To make the site work I need to put a "dev" serveralias in the Apache Virtual Hosts table. My DNS is hosted through GoDaddy and I have searched everywhere for a phantom A or CName entry for "dev."
I hope there is someone that can enlighten me?
apache2 dns virtualhost
asked Jan 19 at 18:57
Ivar HyngstromIvar Hyngstrom
11
add a comment |
Well, I am lost... I was trying to transfer my WordPress server (on Ubuntu 18.04) from Azure to AWS. I used ManageWP to do this, but had issues with logging in. So I created a new blank WordPress server that I named dev.mydomain.com. and successfully cloned the server.
I then wanted to remove the "dev." entry in DNS and just use my "www." name. There are three A records in my DNS zone that point to my server: "www", "*" and "@".
But regardless of which browser I use or browser cache I flush I keep getting redirected to "dev.mydomain.com". I am pretty certain that this is a server or DNS issue. I have gone to the extent of deleting the WordPress content and creating a static html file for the server. It's just a standard .htaccess file for WordPress with no obvious redirects in it, and I deleted it for the static page.
Even when I point my DNS back to the Azure servers the "dev." keeps coming back. To make the site work I need to put a "dev" serveralias in the Apache Virtual Hosts table. My DNS is hosted through GoDaddy and I have searched everywhere for a phantom A or CName entry for "dev."
I hope there is someone that can enlighten me?
apache2 dns virtualhost
asked Jan 19 at 18:57
Ivar HyngstromIvar Hyngstrom
11
It's probably not DNS. DNS has no mechanism for rewriting names. It's almost certainly either a browser cache issue (try private mode or a different browser), or a www-server configuration issue.
– vidarlo
Jan 19 at 20:21
add a comment |
Well, I am lost... I was trying to transfer my WordPress server (on Ubuntu 18.04) from Azure to AWS. I used ManageWP to do this, but had issues with logging in. So I created a new blank WordPress server that I named dev.mydomain.com. and successfully cloned the server.
I then wanted to remove the "dev." entry in DNS and just use my "www." name. There are three A records in my DNS zone that point to my server: "www", "*" and "@".
But regardless of which browser I use or browser cache I flush I keep getting redirected to "dev.mydomain.com". I am pretty certain that this is a server or DNS issue. I have gone to the extent of deleting the WordPress content and creating a static html file for the server. It's just a standard .htaccess file for WordPress with no obvious redirects in it, and I deleted it for the static page.
Even when I point my DNS back to the Azure servers the "dev." keeps coming back. To make the site work I need to put a "dev" serveralias in the Apache Virtual Hosts table. My DNS is hosted through GoDaddy and I have searched everywhere for a phantom A or CName entry for "dev."
I hope there is someone that can enlighten me?
apache2 dns virtualhost
asked Jan 19 at 18:57
Ivar HyngstromIvar Hyngstrom
11
Well, I am lost... I was trying to transfer my WordPress server (on Ubuntu 18.04) from Azure to AWS. I used ManageWP to do this, but had issues with logging in. So I created a new blank WordPress server that I named dev.mydomain.com. and successfully cloned the server.
I then wanted to remove the "dev." entry in DNS and just use my "www." name. There are three A records in my DNS zone that point to my server: "www", "*" and "@".
But regardless of which browser I use or browser cache I flush I keep getting redirected to "dev.mydomain.com". I am pretty certain that this is a server or DNS issue. I have gone to the extent of deleting the WordPress content and creating a static html file for the server. It's just a standard .htaccess file for WordPress with no obvious redirects in it, and I deleted it for the static page.
Even when I point my DNS back to the Azure servers the "dev." keeps coming back. To make the site work I need to put a "dev" serveralias in the Apache Virtual Hosts table. My DNS is hosted through GoDaddy and I have searched everywhere for a phantom A or CName entry for "dev."
I hope there is someone that can enlighten me?
apache2 dns virtualhost
apache2 dns virtualhost
asked Jan 19 at 18:57
Ivar HyngstromIvar Hyngstrom
11
asked Jan 19 at 18:57
Ivar HyngstromIvar Hyngstrom
11
asked Jan 19 at 18:57
Ivar HyngstromIvar Hyngstrom
11
asked Jan 19 at 18:57
Ivar HyngstromIvar Hyngstrom
11
asked Jan 19 at 18:57
Ivar HyngstromIvar Hyngstrom
11
11
It's probably not DNS. DNS has no mechanism for rewriting names. It's almost certainly either a browser cache issue (try private mode or a different browser), or a www-server configuration issue.
– vidarlo
Jan 19 at 20:21
add a comment |
It's probably not DNS. DNS has no mechanism for rewriting names. It's almost certainly either a browser cache issue (try private mode or a different browser), or a www-server configuration issue.
– vidarlo
Jan 19 at 20:21
It's probably not DNS. DNS has no mechanism for rewriting names. It's almost certainly either a browser cache issue (try private mode or a different browser), or a www-server configuration issue.
– vidarlo
Jan 19 at 20:21
It's probably not DNS. DNS has no mechanism for rewriting names. It's almost certainly either a browser cache issue (try private mode or a different browser), or a www-server configuration issue.
– vidarlo
Jan 19 at 20:21
add a comment |
1 Answer
1
active
oldest
votes
There's no mechanism in DNS for rewriting host names, so it is certainly not a DNS issue. There can be two culprits here, really:
- Web server is somehow configured to redirect you
- The web server was configured to redirect you, and your browser now caches this.
To verify this, first check that the DNS records are seen correctly. DNS can take some time to propagate. This can be verified with
dig +short example.org
In the case of verifying cname, do
dig +short example.org cname
Once you have verified that DNS is correctly confiured, use curl to check for any offending headers from the webserver.
curl -I http://example.org
Look for any lines starting with Location: which is redirects.
This will tell you about server configuration. Note that curl uses no caching, so it is always fresh information after configuration changes.
This is not a complete answer, but I believe it is the best possible given the information. If you update your question with more information I will expand the answer :)
answered Jan 19 at 20:27
vidarlovidarlo
10.4k52447
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1111189%2fdns-redirection-issue%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
There's no mechanism in DNS for rewriting host names, so it is certainly not a DNS issue. There can be two culprits here, really:
- Web server is somehow configured to redirect you
- The web server was configured to redirect you, and your browser now caches this.
To verify this, first check that the DNS records are seen correctly. DNS can take some time to propagate. This can be verified with
dig +short example.org
In the case of verifying cname, do
dig +short example.org cname
Once you have verified that DNS is correctly confiured, use curl to check for any offending headers from the webserver.
curl -I http://example.org
Look for any lines starting with Location: which is redirects.
This will tell you about server configuration. Note that curl uses no caching, so it is always fresh information after configuration changes.
This is not a complete answer, but I believe it is the best possible given the information. If you update your question with more information I will expand the answer :)
answered Jan 19 at 20:27
vidarlovidarlo
10.4k52447
add a comment |
There's no mechanism in DNS for rewriting host names, so it is certainly not a DNS issue. There can be two culprits here, really:
- Web server is somehow configured to redirect you
- The web server was configured to redirect you, and your browser now caches this.
To verify this, first check that the DNS records are seen correctly. DNS can take some time to propagate. This can be verified with
dig +short example.org
In the case of verifying cname, do
dig +short example.org cname
Once you have verified that DNS is correctly confiured, use curl to check for any offending headers from the webserver.
curl -I http://example.org
Look for any lines starting with Location: which is redirects.
This will tell you about server configuration. Note that curl uses no caching, so it is always fresh information after configuration changes.
This is not a complete answer, but I believe it is the best possible given the information. If you update your question with more information I will expand the answer :)
answered Jan 19 at 20:27
vidarlovidarlo
10.4k52447
add a comment |
There's no mechanism in DNS for rewriting host names, so it is certainly not a DNS issue. There can be two culprits here, really:
- Web server is somehow configured to redirect you
- The web server was configured to redirect you, and your browser now caches this.
To verify this, first check that the DNS records are seen correctly. DNS can take some time to propagate. This can be verified with
dig +short example.org
In the case of verifying cname, do
dig +short example.org cname
Once you have verified that DNS is correctly confiured, use curl to check for any offending headers from the webserver.
curl -I http://example.org
Look for any lines starting with Location: which is redirects.
This will tell you about server configuration. Note that curl uses no caching, so it is always fresh information after configuration changes.
This is not a complete answer, but I believe it is the best possible given the information. If you update your question with more information I will expand the answer :)
answered Jan 19 at 20:27
vidarlovidarlo
10.4k52447
There's no mechanism in DNS for rewriting host names, so it is certainly not a DNS issue. There can be two culprits here, really:
- Web server is somehow configured to redirect you
- The web server was configured to redirect you, and your browser now caches this.
To verify this, first check that the DNS records are seen correctly. DNS can take some time to propagate. This can be verified with
dig +short example.org
In the case of verifying cname, do
dig +short example.org cname
Once you have verified that DNS is correctly confiured, use curl to check for any offending headers from the webserver.
curl -I http://example.org
Look for any lines starting with Location: which is redirects.
This will tell you about server configuration. Note that curl uses no caching, so it is always fresh information after configuration changes.
This is not a complete answer, but I believe it is the best possible given the information. If you update your question with more information I will expand the answer :)
answered Jan 19 at 20:27
vidarlovidarlo
10.4k52447
answered Jan 19 at 20:27
vidarlovidarlo
10.4k52447
answered Jan 19 at 20:27
vidarlovidarlo
10.4k52447
answered Jan 19 at 20:27
vidarlovidarlo
10.4k52447
10.4k52447
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1111189%2fdns-redirection-issue%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
It's probably not DNS. DNS has no mechanism for rewriting names. It's almost certainly either a browser cache issue (try private mode or a different browser), or a www-server configuration issue.
– vidarlo
Jan 19 at 20:21