Setting up DNS on reverse proxyProblem with GWT behind a reverse proxy - either nginx or apachenginx load...
They call me Inspector Morse
infinitive telling the purpose
"One can do his homework in the library"
Does "variables should live in the smallest scope as possible" include the case "variables should not exist if possible"?
Examples of a statistic that is not independent of sample's distribution?
Finding algorithms of QGIS commands?
Word for a person who has no opinion about whether god exists
Why would a jet engine that runs at temps excess of 2000°C burn when it crashes?
In the late 1940’s to early 1950’s what technology was available that could melt a LOT of ice?
Why is there a voltage between the mains ground and my radiator?
How do I deal with a powergamer in a game full of beginners in a school club?
Making a sword in the stone, in a medieval world without magic
How do you like my writing?
Do Bugbears' arms literally get longer when it's their turn?
Fourth person (in Slavey language)
What are some noteworthy "mic-drop" moments in math?
Does splitting a potentially monolithic application into several smaller ones help prevent bugs?
How did Alan Turing break the enigma code using the hint given by the lady in the bar?
What is the likely impact of grounding an entire aircraft series?
Is there any way to damage Intellect Devourer(s) when already within a creature's skull?
How do I express some one as a black person?
Should I tell my boss the work he did was worthless
If the Captain's screens are out, does he switch seats with the co-pilot?
Should QA ask requirements to developers?
Setting up DNS on reverse proxy
Problem with GWT behind a reverse proxy - either nginx or apachenginx load balancing issue with 301 from backendNginx case-insensitive reverse proxy rewritessetting up postfix on Ubuntu with Apache and nginxnginx reverse proxy, ssl offloading, caching and pagespeed all in one.Make nginx to pass hostname of the upstream when reverseproxyingAny good solution to deliver private HTTP service to public with reverse connection?Letsencrypt client behind a reverse Nginx proxyNginx reverse proxy arbitrary directory to subdomainnginx reverse stream proxy with multiple ports to the same server
I have a backend that used to be my front end. Now my front end is an nginx proxy server. It just serves as an http and an IMAP/SMTP proxy. The backend services apache,mysql,dovecot/postfix. Since I defined the nameservers to this box on the registrar, do I now define the nameservers to the proxy box? It is located in a different geographical location? If so, what hostname should the backend have? The proxy needs to resolve the MX. Thanks.
domain-name-system nginx reverse-proxy
edited Sep 17 '15 at 9:21
Reaces
4,89433045
asked Apr 9 '14 at 16:31
pipetosedpipetosed
144
bumped to the homepage by Community♦ 3 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I have a backend that used to be my front end. Now my front end is an nginx proxy server. It just serves as an http and an IMAP/SMTP proxy. The backend services apache,mysql,dovecot/postfix. Since I defined the nameservers to this box on the registrar, do I now define the nameservers to the proxy box? It is located in a different geographical location? If so, what hostname should the backend have? The proxy needs to resolve the MX. Thanks.
domain-name-system nginx reverse-proxy
edited Sep 17 '15 at 9:21
Reaces
4,89433045
asked Apr 9 '14 at 16:31
pipetosedpipetosed
144
bumped to the homepage by Community♦ 3 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I have a backend that used to be my front end. Now my front end is an nginx proxy server. It just serves as an http and an IMAP/SMTP proxy. The backend services apache,mysql,dovecot/postfix. Since I defined the nameservers to this box on the registrar, do I now define the nameservers to the proxy box? It is located in a different geographical location? If so, what hostname should the backend have? The proxy needs to resolve the MX. Thanks.
domain-name-system nginx reverse-proxy
edited Sep 17 '15 at 9:21
Reaces
4,89433045
asked Apr 9 '14 at 16:31
pipetosedpipetosed
144
I have a backend that used to be my front end. Now my front end is an nginx proxy server. It just serves as an http and an IMAP/SMTP proxy. The backend services apache,mysql,dovecot/postfix. Since I defined the nameservers to this box on the registrar, do I now define the nameservers to the proxy box? It is located in a different geographical location? If so, what hostname should the backend have? The proxy needs to resolve the MX. Thanks.
domain-name-system nginx reverse-proxy
domain-name-system nginx reverse-proxy
edited Sep 17 '15 at 9:21
Reaces
4,89433045
asked Apr 9 '14 at 16:31
pipetosedpipetosed
144
edited Sep 17 '15 at 9:21
Reaces
4,89433045
asked Apr 9 '14 at 16:31
pipetosedpipetosed
144
edited Sep 17 '15 at 9:21
Reaces
4,89433045
edited Sep 17 '15 at 9:21
Reaces
4,89433045
edited Sep 17 '15 at 9:21
Reaces
4,89433045
4,89433045
asked Apr 9 '14 at 16:31
pipetosedpipetosed
144
asked Apr 9 '14 at 16:31
pipetosedpipetosed
144
asked Apr 9 '14 at 16:31
pipetosedpipetosed
144
144
bumped to the homepage by Community♦ 3 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 3 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
By defining nameservers at registrar to this box I assume that you are referring to glue records pointing to the IP(s) of that server. It means that you also have a DNS server running on that box, such as BIND or DNSMASQ. You would need to move that service to the new box.
answered Apr 9 '14 at 17:11
Florin AsăvoaieFlorin Asăvoaie
6,3161633
Yes the glue records defined in the registrar and bind is set up on that box. Now I am moving my front end to a proxy. Should the glue records be defined for the new proxy? Also if I do that, what hostname should the backend NOT be? I assume since there aren't any authoritative dns servers on the backend anymore (after moving them to the proxy), that it would not matter since they wont resolve anyway. However my postfix needs to have my official mail exchanger record set up right. My MX record. I see that in nginx.conf, I can set the name server regardless of that physical hostname
– pipetosed
Apr 9 '14 at 17:20
Nameservers have nothing to do with nginx, there is no such thing as a physical hostname and, if you want your proxy to get the emails for the postfix server then the MX records have to be pointed to the proxy. I think that you either need to start reading and learn what you are doing and have to do, either hire a professional.
– Florin Asăvoaie
Apr 9 '14 at 17:28
Let me clarify for you since I don't think you understand what I am asking. On the proxy box, I defined my dns zone to be my authoritative server and have the glue records pointed there. I already know that part. However, what kind of zone is supposed to be configured for the BACKEND? I run bind on the backend, yes or no and just point server_name in nginx.conf to the physical IP of the backend? When i said physical hostname, I am reffering to /etc/hostname. I also am aware I define the MX hostname inside nginx.conf no matter what is listed in /etc/hostname. This serves as reference for MX.
– pipetosed
Apr 9 '14 at 17:48
You don't run DNS on backend.
– Florin Asăvoaie
Apr 9 '14 at 17:55
Thanks. I assumed that's what I needed. However, I should still define /etc/hostname as my MX like mail.example.com on the backend correct? postfix would need this. Finally, for /etc/hostname on the proxy, should that just be something like ns1.example.com? Defining mail.example.com here does not make sense since that is defined INSIDE nginx.conf for our single point of reference for our mail users correct? Really appreciate the clarification
– pipetosed
Apr 9 '14 at 18:14
|
show 2 more comments
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "2"
};
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%2fserverfault.com%2fquestions%2f587824%2fsetting-up-dns-on-reverse-proxy%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
By defining nameservers at registrar to this box I assume that you are referring to glue records pointing to the IP(s) of that server. It means that you also have a DNS server running on that box, such as BIND or DNSMASQ. You would need to move that service to the new box.
answered Apr 9 '14 at 17:11
Florin AsăvoaieFlorin Asăvoaie
6,3161633
Yes the glue records defined in the registrar and bind is set up on that box. Now I am moving my front end to a proxy. Should the glue records be defined for the new proxy? Also if I do that, what hostname should the backend NOT be? I assume since there aren't any authoritative dns servers on the backend anymore (after moving them to the proxy), that it would not matter since they wont resolve anyway. However my postfix needs to have my official mail exchanger record set up right. My MX record. I see that in nginx.conf, I can set the name server regardless of that physical hostname
– pipetosed
Apr 9 '14 at 17:20
Nameservers have nothing to do with nginx, there is no such thing as a physical hostname and, if you want your proxy to get the emails for the postfix server then the MX records have to be pointed to the proxy. I think that you either need to start reading and learn what you are doing and have to do, either hire a professional.
– Florin Asăvoaie
Apr 9 '14 at 17:28
Let me clarify for you since I don't think you understand what I am asking. On the proxy box, I defined my dns zone to be my authoritative server and have the glue records pointed there. I already know that part. However, what kind of zone is supposed to be configured for the BACKEND? I run bind on the backend, yes or no and just point server_name in nginx.conf to the physical IP of the backend? When i said physical hostname, I am reffering to /etc/hostname. I also am aware I define the MX hostname inside nginx.conf no matter what is listed in /etc/hostname. This serves as reference for MX.
– pipetosed
Apr 9 '14 at 17:48
You don't run DNS on backend.
– Florin Asăvoaie
Apr 9 '14 at 17:55
Thanks. I assumed that's what I needed. However, I should still define /etc/hostname as my MX like mail.example.com on the backend correct? postfix would need this. Finally, for /etc/hostname on the proxy, should that just be something like ns1.example.com? Defining mail.example.com here does not make sense since that is defined INSIDE nginx.conf for our single point of reference for our mail users correct? Really appreciate the clarification
– pipetosed
Apr 9 '14 at 18:14
|
show 2 more comments
By defining nameservers at registrar to this box I assume that you are referring to glue records pointing to the IP(s) of that server. It means that you also have a DNS server running on that box, such as BIND or DNSMASQ. You would need to move that service to the new box.
answered Apr 9 '14 at 17:11
Florin AsăvoaieFlorin Asăvoaie
6,3161633
Yes the glue records defined in the registrar and bind is set up on that box. Now I am moving my front end to a proxy. Should the glue records be defined for the new proxy? Also if I do that, what hostname should the backend NOT be? I assume since there aren't any authoritative dns servers on the backend anymore (after moving them to the proxy), that it would not matter since they wont resolve anyway. However my postfix needs to have my official mail exchanger record set up right. My MX record. I see that in nginx.conf, I can set the name server regardless of that physical hostname
– pipetosed
Apr 9 '14 at 17:20
Nameservers have nothing to do with nginx, there is no such thing as a physical hostname and, if you want your proxy to get the emails for the postfix server then the MX records have to be pointed to the proxy. I think that you either need to start reading and learn what you are doing and have to do, either hire a professional.
– Florin Asăvoaie
Apr 9 '14 at 17:28
Let me clarify for you since I don't think you understand what I am asking. On the proxy box, I defined my dns zone to be my authoritative server and have the glue records pointed there. I already know that part. However, what kind of zone is supposed to be configured for the BACKEND? I run bind on the backend, yes or no and just point server_name in nginx.conf to the physical IP of the backend? When i said physical hostname, I am reffering to /etc/hostname. I also am aware I define the MX hostname inside nginx.conf no matter what is listed in /etc/hostname. This serves as reference for MX.
– pipetosed
Apr 9 '14 at 17:48
You don't run DNS on backend.
– Florin Asăvoaie
Apr 9 '14 at 17:55
Thanks. I assumed that's what I needed. However, I should still define /etc/hostname as my MX like mail.example.com on the backend correct? postfix would need this. Finally, for /etc/hostname on the proxy, should that just be something like ns1.example.com? Defining mail.example.com here does not make sense since that is defined INSIDE nginx.conf for our single point of reference for our mail users correct? Really appreciate the clarification
– pipetosed
Apr 9 '14 at 18:14
|
show 2 more comments
By defining nameservers at registrar to this box I assume that you are referring to glue records pointing to the IP(s) of that server. It means that you also have a DNS server running on that box, such as BIND or DNSMASQ. You would need to move that service to the new box.
answered Apr 9 '14 at 17:11
Florin AsăvoaieFlorin Asăvoaie
6,3161633
By defining nameservers at registrar to this box I assume that you are referring to glue records pointing to the IP(s) of that server. It means that you also have a DNS server running on that box, such as BIND or DNSMASQ. You would need to move that service to the new box.
answered Apr 9 '14 at 17:11
Florin AsăvoaieFlorin Asăvoaie
6,3161633
answered Apr 9 '14 at 17:11
Florin AsăvoaieFlorin Asăvoaie
6,3161633
answered Apr 9 '14 at 17:11
Florin AsăvoaieFlorin Asăvoaie
6,3161633
answered Apr 9 '14 at 17:11
Florin AsăvoaieFlorin Asăvoaie
6,3161633
6,3161633
Yes the glue records defined in the registrar and bind is set up on that box. Now I am moving my front end to a proxy. Should the glue records be defined for the new proxy? Also if I do that, what hostname should the backend NOT be? I assume since there aren't any authoritative dns servers on the backend anymore (after moving them to the proxy), that it would not matter since they wont resolve anyway. However my postfix needs to have my official mail exchanger record set up right. My MX record. I see that in nginx.conf, I can set the name server regardless of that physical hostname
– pipetosed
Apr 9 '14 at 17:20
Nameservers have nothing to do with nginx, there is no such thing as a physical hostname and, if you want your proxy to get the emails for the postfix server then the MX records have to be pointed to the proxy. I think that you either need to start reading and learn what you are doing and have to do, either hire a professional.
– Florin Asăvoaie
Apr 9 '14 at 17:28
Let me clarify for you since I don't think you understand what I am asking. On the proxy box, I defined my dns zone to be my authoritative server and have the glue records pointed there. I already know that part. However, what kind of zone is supposed to be configured for the BACKEND? I run bind on the backend, yes or no and just point server_name in nginx.conf to the physical IP of the backend? When i said physical hostname, I am reffering to /etc/hostname. I also am aware I define the MX hostname inside nginx.conf no matter what is listed in /etc/hostname. This serves as reference for MX.
– pipetosed
Apr 9 '14 at 17:48
You don't run DNS on backend.
– Florin Asăvoaie
Apr 9 '14 at 17:55
Thanks. I assumed that's what I needed. However, I should still define /etc/hostname as my MX like mail.example.com on the backend correct? postfix would need this. Finally, for /etc/hostname on the proxy, should that just be something like ns1.example.com? Defining mail.example.com here does not make sense since that is defined INSIDE nginx.conf for our single point of reference for our mail users correct? Really appreciate the clarification
– pipetosed
Apr 9 '14 at 18:14
|
show 2 more comments
Yes the glue records defined in the registrar and bind is set up on that box. Now I am moving my front end to a proxy. Should the glue records be defined for the new proxy? Also if I do that, what hostname should the backend NOT be? I assume since there aren't any authoritative dns servers on the backend anymore (after moving them to the proxy), that it would not matter since they wont resolve anyway. However my postfix needs to have my official mail exchanger record set up right. My MX record. I see that in nginx.conf, I can set the name server regardless of that physical hostname
– pipetosed
Apr 9 '14 at 17:20
Nameservers have nothing to do with nginx, there is no such thing as a physical hostname and, if you want your proxy to get the emails for the postfix server then the MX records have to be pointed to the proxy. I think that you either need to start reading and learn what you are doing and have to do, either hire a professional.
– Florin Asăvoaie
Apr 9 '14 at 17:28
Let me clarify for you since I don't think you understand what I am asking. On the proxy box, I defined my dns zone to be my authoritative server and have the glue records pointed there. I already know that part. However, what kind of zone is supposed to be configured for the BACKEND? I run bind on the backend, yes or no and just point server_name in nginx.conf to the physical IP of the backend? When i said physical hostname, I am reffering to /etc/hostname. I also am aware I define the MX hostname inside nginx.conf no matter what is listed in /etc/hostname. This serves as reference for MX.
– pipetosed
Apr 9 '14 at 17:48
You don't run DNS on backend.
– Florin Asăvoaie
Apr 9 '14 at 17:55
Thanks. I assumed that's what I needed. However, I should still define /etc/hostname as my MX like mail.example.com on the backend correct? postfix would need this. Finally, for /etc/hostname on the proxy, should that just be something like ns1.example.com? Defining mail.example.com here does not make sense since that is defined INSIDE nginx.conf for our single point of reference for our mail users correct? Really appreciate the clarification
– pipetosed
Apr 9 '14 at 18:14
Yes the glue records defined in the registrar and bind is set up on that box. Now I am moving my front end to a proxy. Should the glue records be defined for the new proxy? Also if I do that, what hostname should the backend NOT be? I assume since there aren't any authoritative dns servers on the backend anymore (after moving them to the proxy), that it would not matter since they wont resolve anyway. However my postfix needs to have my official mail exchanger record set up right. My MX record. I see that in nginx.conf, I can set the name server regardless of that physical hostname
– pipetosed
Apr 9 '14 at 17:20
Yes the glue records defined in the registrar and bind is set up on that box. Now I am moving my front end to a proxy. Should the glue records be defined for the new proxy? Also if I do that, what hostname should the backend NOT be? I assume since there aren't any authoritative dns servers on the backend anymore (after moving them to the proxy), that it would not matter since they wont resolve anyway. However my postfix needs to have my official mail exchanger record set up right. My MX record. I see that in nginx.conf, I can set the name server regardless of that physical hostname
– pipetosed
Apr 9 '14 at 17:20
Nameservers have nothing to do with nginx, there is no such thing as a physical hostname and, if you want your proxy to get the emails for the postfix server then the MX records have to be pointed to the proxy. I think that you either need to start reading and learn what you are doing and have to do, either hire a professional.
– Florin Asăvoaie
Apr 9 '14 at 17:28
Nameservers have nothing to do with nginx, there is no such thing as a physical hostname and, if you want your proxy to get the emails for the postfix server then the MX records have to be pointed to the proxy. I think that you either need to start reading and learn what you are doing and have to do, either hire a professional.
– Florin Asăvoaie
Apr 9 '14 at 17:28
Let me clarify for you since I don't think you understand what I am asking. On the proxy box, I defined my dns zone to be my authoritative server and have the glue records pointed there. I already know that part. However, what kind of zone is supposed to be configured for the BACKEND? I run bind on the backend, yes or no and just point server_name in nginx.conf to the physical IP of the backend? When i said physical hostname, I am reffering to /etc/hostname. I also am aware I define the MX hostname inside nginx.conf no matter what is listed in /etc/hostname. This serves as reference for MX.
– pipetosed
Apr 9 '14 at 17:48
Let me clarify for you since I don't think you understand what I am asking. On the proxy box, I defined my dns zone to be my authoritative server and have the glue records pointed there. I already know that part. However, what kind of zone is supposed to be configured for the BACKEND? I run bind on the backend, yes or no and just point server_name in nginx.conf to the physical IP of the backend? When i said physical hostname, I am reffering to /etc/hostname. I also am aware I define the MX hostname inside nginx.conf no matter what is listed in /etc/hostname. This serves as reference for MX.
– pipetosed
Apr 9 '14 at 17:48
You don't run DNS on backend.
– Florin Asăvoaie
Apr 9 '14 at 17:55
You don't run DNS on backend.
– Florin Asăvoaie
Apr 9 '14 at 17:55
Thanks. I assumed that's what I needed. However, I should still define /etc/hostname as my MX like mail.example.com on the backend correct? postfix would need this. Finally, for /etc/hostname on the proxy, should that just be something like ns1.example.com? Defining mail.example.com here does not make sense since that is defined INSIDE nginx.conf for our single point of reference for our mail users correct? Really appreciate the clarification
– pipetosed
Apr 9 '14 at 18:14
Thanks. I assumed that's what I needed. However, I should still define /etc/hostname as my MX like mail.example.com on the backend correct? postfix would need this. Finally, for /etc/hostname on the proxy, should that just be something like ns1.example.com? Defining mail.example.com here does not make sense since that is defined INSIDE nginx.conf for our single point of reference for our mail users correct? Really appreciate the clarification
– pipetosed
Apr 9 '14 at 18:14
|
show 2 more comments
Thanks for contributing an answer to Server Fault!
- 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%2fserverfault.com%2fquestions%2f587824%2fsetting-up-dns-on-reverse-proxy%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
