IIS host header name resolution across my networkHost Header DNS Problem - Requires FlushDNSsetup dns to redirect all http requests on a specific machine in LANConfiguring DNS and IIS for multiple domains on a single serverDNS points to wrong website IIS7How do use Host Headers in IIS 6.0?Domain Name hosted by GoDaddy not resolved to IIS websiteLocal request to port 80 via domain nameBinding a host name in IIS 8.5 causes “Authentication Required” promptIIS serving page remote but not locallyWildcard certificate host name
Test if tikzmark exists on same page
Email Account under attack (really) - anything I can do?
A newer friend of my brother's gave him a load of baseball cards that are supposedly extremely valuable. Is this a scam?
TGV timetables / schedules?
Show that if two triangles built on parallel lines, with equal bases have the same perimeter only if they are congruent.
Why are electrically insulating heatsinks so rare? Is it just cost?
"to be prejudice towards/against someone" vs "to be prejudiced against/towards someone"
tikz: show 0 at the axis origin
The use of multiple foreign keys on same column in SQL Server
Languages that we cannot (dis)prove to be Context-Free
Did Shadowfax go to Valinor?
To string or not to string
Is a tag line useful on a cover?
Theorems that impeded progress
Either or Neither in sentence with another negative
I'm planning on buying a laser printer but concerned about the life cycle of toner in the machine
Arthur Somervell: 1000 Exercises - Meaning of this notation
Why are 150k or 200k jobs considered good when there are 300k+ births a month?
Why don't electron-positron collisions release infinite energy?
Is it possible to do 50 km distance without any previous training?
Why doesn't Newton's third law mean a person bounces back to where they started when they hit the ground?
How do we improve the relationship with a client software team that performs poorly and is becoming less collaborative?
Adding span tags within wp_list_pages list items
US citizen flying to France today and my passport expires in less than 2 months
IIS host header name resolution across my network
Host Header DNS Problem - Requires FlushDNSsetup dns to redirect all http requests on a specific machine in LANConfiguring DNS and IIS for multiple domains on a single serverDNS points to wrong website IIS7How do use Host Headers in IIS 6.0?Domain Name hosted by GoDaddy not resolved to IIS websiteLocal request to port 80 via domain nameBinding a host name in IIS 8.5 causes “Authentication Required” promptIIS serving page remote but not locallyWildcard certificate host name
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I have a Windows Server 2012 R2 machine, named [mine-1234].
I have IIS 8.5 installed and a hole in my firewall for ports 80 and 443.
I have created 2 test sites
- one with a default binding to
:80 - one with two bindings to
:80with host headers.[foo.mine-1234]and[foo.mine.local]
I configured my hosts file to resolve mine.local and foo.mine.local to 127.0.0.1 and local reference to the sites resolve fine. The issue I'm having is when I attempt to use the external bindings on my LAN.
Requests from Localhost
http://mine.local/index.htmlloads in the browserhttp://foo.mine.local/index.htmlloads in the browser.
Requests from LAN Clients
http://mine-1234/index.htmlloads in the browser.http://foo.mine-1234/index.htmldoes not load in the browser.
However, the host headers do not resolve for other callers on my LAN that are outside my machine.
3 Questions (2 and 3 depend on the answer to 1)
- Can
foobe made available to my LAN without modifying DNS? [if: 1=yes]What is the proper binding forfooonmine-1234to make it accessible to my LAN without modifying DNS?[if: 1=no]What is the most straightforward way to modify DNS to makefooavailable to my LAN?
domain-name-system web-hosting iis-8.5
asked Feb 8 '16 at 18:59
K. Alan BatesK. Alan Bates
1617
add a comment |
I have a Windows Server 2012 R2 machine, named [mine-1234].
I have IIS 8.5 installed and a hole in my firewall for ports 80 and 443.
I have created 2 test sites
- one with a default binding to
:80 - one with two bindings to
:80with host headers.[foo.mine-1234]and[foo.mine.local]
I configured my hosts file to resolve mine.local and foo.mine.local to 127.0.0.1 and local reference to the sites resolve fine. The issue I'm having is when I attempt to use the external bindings on my LAN.
Requests from Localhost
http://mine.local/index.htmlloads in the browserhttp://foo.mine.local/index.htmlloads in the browser.
Requests from LAN Clients
http://mine-1234/index.htmlloads in the browser.http://foo.mine-1234/index.htmldoes not load in the browser.
However, the host headers do not resolve for other callers on my LAN that are outside my machine.
3 Questions (2 and 3 depend on the answer to 1)
- Can
foobe made available to my LAN without modifying DNS? [if: 1=yes]What is the proper binding forfooonmine-1234to make it accessible to my LAN without modifying DNS?[if: 1=no]What is the most straightforward way to modify DNS to makefooavailable to my LAN?
domain-name-system web-hosting iis-8.5
asked Feb 8 '16 at 18:59
K. Alan BatesK. Alan Bates
1617
add a comment |
I have a Windows Server 2012 R2 machine, named [mine-1234].
I have IIS 8.5 installed and a hole in my firewall for ports 80 and 443.
I have created 2 test sites
- one with a default binding to
:80 - one with two bindings to
:80with host headers.[foo.mine-1234]and[foo.mine.local]
I configured my hosts file to resolve mine.local and foo.mine.local to 127.0.0.1 and local reference to the sites resolve fine. The issue I'm having is when I attempt to use the external bindings on my LAN.
Requests from Localhost
http://mine.local/index.htmlloads in the browserhttp://foo.mine.local/index.htmlloads in the browser.
Requests from LAN Clients
http://mine-1234/index.htmlloads in the browser.http://foo.mine-1234/index.htmldoes not load in the browser.
However, the host headers do not resolve for other callers on my LAN that are outside my machine.
3 Questions (2 and 3 depend on the answer to 1)
- Can
foobe made available to my LAN without modifying DNS? [if: 1=yes]What is the proper binding forfooonmine-1234to make it accessible to my LAN without modifying DNS?[if: 1=no]What is the most straightforward way to modify DNS to makefooavailable to my LAN?
domain-name-system web-hosting iis-8.5
asked Feb 8 '16 at 18:59
K. Alan BatesK. Alan Bates
1617
I have a Windows Server 2012 R2 machine, named [mine-1234].
I have IIS 8.5 installed and a hole in my firewall for ports 80 and 443.
I have created 2 test sites
- one with a default binding to
:80 - one with two bindings to
:80with host headers.[foo.mine-1234]and[foo.mine.local]
I configured my hosts file to resolve mine.local and foo.mine.local to 127.0.0.1 and local reference to the sites resolve fine. The issue I'm having is when I attempt to use the external bindings on my LAN.
Requests from Localhost
http://mine.local/index.htmlloads in the browserhttp://foo.mine.local/index.htmlloads in the browser.
Requests from LAN Clients
http://mine-1234/index.htmlloads in the browser.http://foo.mine-1234/index.htmldoes not load in the browser.
However, the host headers do not resolve for other callers on my LAN that are outside my machine.
3 Questions (2 and 3 depend on the answer to 1)
- Can
foobe made available to my LAN without modifying DNS? [if: 1=yes]What is the proper binding forfooonmine-1234to make it accessible to my LAN without modifying DNS?[if: 1=no]What is the most straightforward way to modify DNS to makefooavailable to my LAN?
domain-name-system web-hosting iis-8.5
domain-name-system web-hosting iis-8.5
asked Feb 8 '16 at 18:59
K. Alan BatesK. Alan Bates
1617
asked Feb 8 '16 at 18:59
K. Alan BatesK. Alan Bates
1617
edited Feb 8 '16 at 21:19
K. Alan Bates
asked Feb 8 '16 at 18:59
K. Alan BatesK. Alan Bates
1617
asked Feb 8 '16 at 18:59
K. Alan BatesK. Alan Bates
1617
asked Feb 8 '16 at 18:59
K. Alan BatesK. Alan Bates
1617
1617
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Alan Bates,
Generally speaking yes you need to modify your DNS for other LAN clients in your network to know how to reach the website.
An easy way to think about it is the setting you create in IIS tell the web server what IP address and host name your website to answer to. It does NOT tell other LAN clients how to reach your website.
LAN clients send the hostname to the DNS server and the DNS server resolves the hostname to an IP address (for this to work you need an A record) the LAN client then sends the request to that IP address (your web server) which checks the hostname requested and if it matches the settings in IIS displays the website.
So you have two parts.
What do I respond to (IIS settings)
How do I reach the website (DNS records)
Best practice is to set one static IP address per website and set the IIS binding for each site to its corresponding static IP address. Then add the DNS A and PTR records on your DNS server so your LAN clients know how to reach your website.
Please let me know if you have any other questions.
answered Feb 8 '16 at 19:37
user5870571user5870571
2,6242829
I was expecting that the existing A record for[mine-1234]could be matched with a CNAME record fordev.mine.domain.localto allow LAN connected users to find my machine, but my curiosity was whether or notfoowould need its own DNS entry or if registering it with a host header in the site binding would suffice. Are you saying it will not? (This is my first time being responsible for onprem hosting in about 12 years. I'm rusty)
– K. Alan Bates
Feb 8 '16 at 19:44
"I was expecting that the existing A record for [mine-1234] could be matched with a CNAME record for dev.mine.domain.local." Usually your DNS server would be authoritative for domain.local. Your hostname would be mine and your FQDN for that server is mine.domain.local. So if you want to create a website hosted on mine.domain.local with a DNS name of dev.domain.local you would bind the hostname dev.domain.local to the website in IIS and create a DNS CNAME record that says dev.domain.local is actually mine.domain.local.
– user5870571
Feb 8 '16 at 19:57
ok. So let me see if I understand you: if my FQMN is//mine-1234.domain.local, I need to configure the binding in IIS tofoo.mine-1234.domain.local:80and in order to make it accessible to LAN Clients, I need a CNAME pointingfoo.mine.localtofoo.mine-1234.domain.local. Is this correct?
– K. Alan Bates
Feb 8 '16 at 20:05
For reference it is FQDN not FQMN and in Windows the slashes for a computer name are "\" not "//". ;) You can have your hostname be whatever you want (mine-1234.domain.local is fine). Configure your website in IIS to bind to dev, foo, whatever .domain.local (e.g. dev.domain.local) and in your DNS server create a CNAME record for dev.domain.local to mine-1234.domain.local.
– user5870571
Feb 8 '16 at 20:07
ok. ...that's consistent with something that I had already tried but couldn't make work and why I asked the question the way I did. With a default binding to port 80, I can accesshttp://mine-1234on my LAN. I can also accesshttp://mine-1234.mydomain.localon my LAN as well as to localhost. Whenever I add a host header to the binding,http://foo.mine-1234.mydomain.localdoesn't even resolve on localhost.
– K. Alan Bates
Feb 8 '16 at 20:58
|
show 3 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%2f754815%2fiis-host-header-name-resolution-across-my-network%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
Alan Bates,
Generally speaking yes you need to modify your DNS for other LAN clients in your network to know how to reach the website.
An easy way to think about it is the setting you create in IIS tell the web server what IP address and host name your website to answer to. It does NOT tell other LAN clients how to reach your website.
LAN clients send the hostname to the DNS server and the DNS server resolves the hostname to an IP address (for this to work you need an A record) the LAN client then sends the request to that IP address (your web server) which checks the hostname requested and if it matches the settings in IIS displays the website.
So you have two parts.
What do I respond to (IIS settings)
How do I reach the website (DNS records)
Best practice is to set one static IP address per website and set the IIS binding for each site to its corresponding static IP address. Then add the DNS A and PTR records on your DNS server so your LAN clients know how to reach your website.
Please let me know if you have any other questions.
answered Feb 8 '16 at 19:37
user5870571user5870571
2,6242829
I was expecting that the existing A record for[mine-1234]could be matched with a CNAME record fordev.mine.domain.localto allow LAN connected users to find my machine, but my curiosity was whether or notfoowould need its own DNS entry or if registering it with a host header in the site binding would suffice. Are you saying it will not? (This is my first time being responsible for onprem hosting in about 12 years. I'm rusty)
– K. Alan Bates
Feb 8 '16 at 19:44
"I was expecting that the existing A record for [mine-1234] could be matched with a CNAME record for dev.mine.domain.local." Usually your DNS server would be authoritative for domain.local. Your hostname would be mine and your FQDN for that server is mine.domain.local. So if you want to create a website hosted on mine.domain.local with a DNS name of dev.domain.local you would bind the hostname dev.domain.local to the website in IIS and create a DNS CNAME record that says dev.domain.local is actually mine.domain.local.
– user5870571
Feb 8 '16 at 19:57
ok. So let me see if I understand you: if my FQMN is//mine-1234.domain.local, I need to configure the binding in IIS tofoo.mine-1234.domain.local:80and in order to make it accessible to LAN Clients, I need a CNAME pointingfoo.mine.localtofoo.mine-1234.domain.local. Is this correct?
– K. Alan Bates
Feb 8 '16 at 20:05
For reference it is FQDN not FQMN and in Windows the slashes for a computer name are "\" not "//". ;) You can have your hostname be whatever you want (mine-1234.domain.local is fine). Configure your website in IIS to bind to dev, foo, whatever .domain.local (e.g. dev.domain.local) and in your DNS server create a CNAME record for dev.domain.local to mine-1234.domain.local.
– user5870571
Feb 8 '16 at 20:07
ok. ...that's consistent with something that I had already tried but couldn't make work and why I asked the question the way I did. With a default binding to port 80, I can accesshttp://mine-1234on my LAN. I can also accesshttp://mine-1234.mydomain.localon my LAN as well as to localhost. Whenever I add a host header to the binding,http://foo.mine-1234.mydomain.localdoesn't even resolve on localhost.
– K. Alan Bates
Feb 8 '16 at 20:58
|
show 3 more comments
Alan Bates,
Generally speaking yes you need to modify your DNS for other LAN clients in your network to know how to reach the website.
An easy way to think about it is the setting you create in IIS tell the web server what IP address and host name your website to answer to. It does NOT tell other LAN clients how to reach your website.
LAN clients send the hostname to the DNS server and the DNS server resolves the hostname to an IP address (for this to work you need an A record) the LAN client then sends the request to that IP address (your web server) which checks the hostname requested and if it matches the settings in IIS displays the website.
So you have two parts.
What do I respond to (IIS settings)
How do I reach the website (DNS records)
Best practice is to set one static IP address per website and set the IIS binding for each site to its corresponding static IP address. Then add the DNS A and PTR records on your DNS server so your LAN clients know how to reach your website.
Please let me know if you have any other questions.
answered Feb 8 '16 at 19:37
user5870571user5870571
2,6242829
I was expecting that the existing A record for[mine-1234]could be matched with a CNAME record fordev.mine.domain.localto allow LAN connected users to find my machine, but my curiosity was whether or notfoowould need its own DNS entry or if registering it with a host header in the site binding would suffice. Are you saying it will not? (This is my first time being responsible for onprem hosting in about 12 years. I'm rusty)
– K. Alan Bates
Feb 8 '16 at 19:44
"I was expecting that the existing A record for [mine-1234] could be matched with a CNAME record for dev.mine.domain.local." Usually your DNS server would be authoritative for domain.local. Your hostname would be mine and your FQDN for that server is mine.domain.local. So if you want to create a website hosted on mine.domain.local with a DNS name of dev.domain.local you would bind the hostname dev.domain.local to the website in IIS and create a DNS CNAME record that says dev.domain.local is actually mine.domain.local.
– user5870571
Feb 8 '16 at 19:57
ok. So let me see if I understand you: if my FQMN is//mine-1234.domain.local, I need to configure the binding in IIS tofoo.mine-1234.domain.local:80and in order to make it accessible to LAN Clients, I need a CNAME pointingfoo.mine.localtofoo.mine-1234.domain.local. Is this correct?
– K. Alan Bates
Feb 8 '16 at 20:05
For reference it is FQDN not FQMN and in Windows the slashes for a computer name are "\" not "//". ;) You can have your hostname be whatever you want (mine-1234.domain.local is fine). Configure your website in IIS to bind to dev, foo, whatever .domain.local (e.g. dev.domain.local) and in your DNS server create a CNAME record for dev.domain.local to mine-1234.domain.local.
– user5870571
Feb 8 '16 at 20:07
ok. ...that's consistent with something that I had already tried but couldn't make work and why I asked the question the way I did. With a default binding to port 80, I can accesshttp://mine-1234on my LAN. I can also accesshttp://mine-1234.mydomain.localon my LAN as well as to localhost. Whenever I add a host header to the binding,http://foo.mine-1234.mydomain.localdoesn't even resolve on localhost.
– K. Alan Bates
Feb 8 '16 at 20:58
|
show 3 more comments
Alan Bates,
Generally speaking yes you need to modify your DNS for other LAN clients in your network to know how to reach the website.
An easy way to think about it is the setting you create in IIS tell the web server what IP address and host name your website to answer to. It does NOT tell other LAN clients how to reach your website.
LAN clients send the hostname to the DNS server and the DNS server resolves the hostname to an IP address (for this to work you need an A record) the LAN client then sends the request to that IP address (your web server) which checks the hostname requested and if it matches the settings in IIS displays the website.
So you have two parts.
What do I respond to (IIS settings)
How do I reach the website (DNS records)
Best practice is to set one static IP address per website and set the IIS binding for each site to its corresponding static IP address. Then add the DNS A and PTR records on your DNS server so your LAN clients know how to reach your website.
Please let me know if you have any other questions.
answered Feb 8 '16 at 19:37
user5870571user5870571
2,6242829
Alan Bates,
Generally speaking yes you need to modify your DNS for other LAN clients in your network to know how to reach the website.
An easy way to think about it is the setting you create in IIS tell the web server what IP address and host name your website to answer to. It does NOT tell other LAN clients how to reach your website.
LAN clients send the hostname to the DNS server and the DNS server resolves the hostname to an IP address (for this to work you need an A record) the LAN client then sends the request to that IP address (your web server) which checks the hostname requested and if it matches the settings in IIS displays the website.
So you have two parts.
What do I respond to (IIS settings)
How do I reach the website (DNS records)
Best practice is to set one static IP address per website and set the IIS binding for each site to its corresponding static IP address. Then add the DNS A and PTR records on your DNS server so your LAN clients know how to reach your website.
Please let me know if you have any other questions.
answered Feb 8 '16 at 19:37
user5870571user5870571
2,6242829
edited Feb 8 '16 at 23:00
answered Feb 8 '16 at 19:37
user5870571user5870571
2,6242829
answered Feb 8 '16 at 19:37
user5870571user5870571
2,6242829
answered Feb 8 '16 at 19:37
user5870571user5870571
2,6242829
2,6242829
I was expecting that the existing A record for[mine-1234]could be matched with a CNAME record fordev.mine.domain.localto allow LAN connected users to find my machine, but my curiosity was whether or notfoowould need its own DNS entry or if registering it with a host header in the site binding would suffice. Are you saying it will not? (This is my first time being responsible for onprem hosting in about 12 years. I'm rusty)
– K. Alan Bates
Feb 8 '16 at 19:44
"I was expecting that the existing A record for [mine-1234] could be matched with a CNAME record for dev.mine.domain.local." Usually your DNS server would be authoritative for domain.local. Your hostname would be mine and your FQDN for that server is mine.domain.local. So if you want to create a website hosted on mine.domain.local with a DNS name of dev.domain.local you would bind the hostname dev.domain.local to the website in IIS and create a DNS CNAME record that says dev.domain.local is actually mine.domain.local.
– user5870571
Feb 8 '16 at 19:57
ok. So let me see if I understand you: if my FQMN is//mine-1234.domain.local, I need to configure the binding in IIS tofoo.mine-1234.domain.local:80and in order to make it accessible to LAN Clients, I need a CNAME pointingfoo.mine.localtofoo.mine-1234.domain.local. Is this correct?
– K. Alan Bates
Feb 8 '16 at 20:05
For reference it is FQDN not FQMN and in Windows the slashes for a computer name are "\" not "//". ;) You can have your hostname be whatever you want (mine-1234.domain.local is fine). Configure your website in IIS to bind to dev, foo, whatever .domain.local (e.g. dev.domain.local) and in your DNS server create a CNAME record for dev.domain.local to mine-1234.domain.local.
– user5870571
Feb 8 '16 at 20:07
ok. ...that's consistent with something that I had already tried but couldn't make work and why I asked the question the way I did. With a default binding to port 80, I can accesshttp://mine-1234on my LAN. I can also accesshttp://mine-1234.mydomain.localon my LAN as well as to localhost. Whenever I add a host header to the binding,http://foo.mine-1234.mydomain.localdoesn't even resolve on localhost.
– K. Alan Bates
Feb 8 '16 at 20:58
|
show 3 more comments
I was expecting that the existing A record for[mine-1234]could be matched with a CNAME record fordev.mine.domain.localto allow LAN connected users to find my machine, but my curiosity was whether or notfoowould need its own DNS entry or if registering it with a host header in the site binding would suffice. Are you saying it will not? (This is my first time being responsible for onprem hosting in about 12 years. I'm rusty)
– K. Alan Bates
Feb 8 '16 at 19:44
"I was expecting that the existing A record for [mine-1234] could be matched with a CNAME record for dev.mine.domain.local." Usually your DNS server would be authoritative for domain.local. Your hostname would be mine and your FQDN for that server is mine.domain.local. So if you want to create a website hosted on mine.domain.local with a DNS name of dev.domain.local you would bind the hostname dev.domain.local to the website in IIS and create a DNS CNAME record that says dev.domain.local is actually mine.domain.local.
– user5870571
Feb 8 '16 at 19:57
ok. So let me see if I understand you: if my FQMN is//mine-1234.domain.local, I need to configure the binding in IIS tofoo.mine-1234.domain.local:80and in order to make it accessible to LAN Clients, I need a CNAME pointingfoo.mine.localtofoo.mine-1234.domain.local. Is this correct?
– K. Alan Bates
Feb 8 '16 at 20:05
For reference it is FQDN not FQMN and in Windows the slashes for a computer name are "\" not "//". ;) You can have your hostname be whatever you want (mine-1234.domain.local is fine). Configure your website in IIS to bind to dev, foo, whatever .domain.local (e.g. dev.domain.local) and in your DNS server create a CNAME record for dev.domain.local to mine-1234.domain.local.
– user5870571
Feb 8 '16 at 20:07
ok. ...that's consistent with something that I had already tried but couldn't make work and why I asked the question the way I did. With a default binding to port 80, I can accesshttp://mine-1234on my LAN. I can also accesshttp://mine-1234.mydomain.localon my LAN as well as to localhost. Whenever I add a host header to the binding,http://foo.mine-1234.mydomain.localdoesn't even resolve on localhost.
– K. Alan Bates
Feb 8 '16 at 20:58
I was expecting that the existing A record for
[mine-1234] could be matched with a CNAME record for dev.mine.domain.local to allow LAN connected users to find my machine, but my curiosity was whether or not foo would need its own DNS entry or if registering it with a host header in the site binding would suffice. Are you saying it will not? (This is my first time being responsible for onprem hosting in about 12 years. I'm rusty)– K. Alan Bates
Feb 8 '16 at 19:44
I was expecting that the existing A record for
[mine-1234] could be matched with a CNAME record for dev.mine.domain.local to allow LAN connected users to find my machine, but my curiosity was whether or not foo would need its own DNS entry or if registering it with a host header in the site binding would suffice. Are you saying it will not? (This is my first time being responsible for onprem hosting in about 12 years. I'm rusty)– K. Alan Bates
Feb 8 '16 at 19:44
"I was expecting that the existing A record for [mine-1234] could be matched with a CNAME record for dev.mine.domain.local." Usually your DNS server would be authoritative for domain.local. Your hostname would be mine and your FQDN for that server is mine.domain.local. So if you want to create a website hosted on mine.domain.local with a DNS name of dev.domain.local you would bind the hostname dev.domain.local to the website in IIS and create a DNS CNAME record that says dev.domain.local is actually mine.domain.local.
– user5870571
Feb 8 '16 at 19:57
"I was expecting that the existing A record for [mine-1234] could be matched with a CNAME record for dev.mine.domain.local." Usually your DNS server would be authoritative for domain.local. Your hostname would be mine and your FQDN for that server is mine.domain.local. So if you want to create a website hosted on mine.domain.local with a DNS name of dev.domain.local you would bind the hostname dev.domain.local to the website in IIS and create a DNS CNAME record that says dev.domain.local is actually mine.domain.local.
– user5870571
Feb 8 '16 at 19:57
ok. So let me see if I understand you: if my FQMN is
//mine-1234.domain.local, I need to configure the binding in IIS to foo.mine-1234.domain.local:80 and in order to make it accessible to LAN Clients, I need a CNAME pointing foo.mine.local to foo.mine-1234.domain.local. Is this correct?– K. Alan Bates
Feb 8 '16 at 20:05
ok. So let me see if I understand you: if my FQMN is
//mine-1234.domain.local, I need to configure the binding in IIS to foo.mine-1234.domain.local:80 and in order to make it accessible to LAN Clients, I need a CNAME pointing foo.mine.local to foo.mine-1234.domain.local. Is this correct?– K. Alan Bates
Feb 8 '16 at 20:05
For reference it is FQDN not FQMN and in Windows the slashes for a computer name are "\" not "//". ;) You can have your hostname be whatever you want (mine-1234.domain.local is fine). Configure your website in IIS to bind to dev, foo, whatever .domain.local (e.g. dev.domain.local) and in your DNS server create a CNAME record for dev.domain.local to mine-1234.domain.local.
– user5870571
Feb 8 '16 at 20:07
For reference it is FQDN not FQMN and in Windows the slashes for a computer name are "\" not "//". ;) You can have your hostname be whatever you want (mine-1234.domain.local is fine). Configure your website in IIS to bind to dev, foo, whatever .domain.local (e.g. dev.domain.local) and in your DNS server create a CNAME record for dev.domain.local to mine-1234.domain.local.
– user5870571
Feb 8 '16 at 20:07
ok. ...that's consistent with something that I had already tried but couldn't make work and why I asked the question the way I did. With a default binding to port 80, I can access
http://mine-1234 on my LAN. I can also access http://mine-1234.mydomain.local on my LAN as well as to localhost. Whenever I add a host header to the binding, http://foo.mine-1234.mydomain.local doesn't even resolve on localhost.– K. Alan Bates
Feb 8 '16 at 20:58
ok. ...that's consistent with something that I had already tried but couldn't make work and why I asked the question the way I did. With a default binding to port 80, I can access
http://mine-1234 on my LAN. I can also access http://mine-1234.mydomain.local on my LAN as well as to localhost. Whenever I add a host header to the binding, http://foo.mine-1234.mydomain.local doesn't even resolve on localhost.– K. Alan Bates
Feb 8 '16 at 20:58
|
show 3 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%2f754815%2fiis-host-header-name-resolution-across-my-network%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
