- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: named + https
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-06-2011 07:05 PM
тАО04-06-2011 07:05 PM
named + https
I recently decided to separate my web-server from Zimbra.
Zimbra is installed @ 10.10.0.2 and responds only on port 443. https://mydomain.com.
WWW is now on 10.10.0.9 and responds only on port 80. The problem now is that the zone points www to 10.10.0.9 so ping mydomain.com internally responds with 10.10.0.9.
This creates an inconvenient situation as I can't do https://mydomain.com internally because the DNS points to 10.10.0.9 which responds only to requests on port 80.
Can I make DNS be aware of different ports or protocols ?
mail A 10.10.0.2
www A 10.10.0.9
mydomain.com A 10.10.0.9
www.mydomain.com A 10.10.0.9
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-06-2011 07:48 PM
тАО04-06-2011 07:48 PM
Re: named + https
> or protocols ?
I don't see how it could. It's the Domain
Name Service, not the Domain Name and/or Port
Number Service.
This sort of thing is normally (best) handled
by an IP router using NAT. (With addresses
like 10.10.0.x, I'd conclude that you have a
router already. Why not use it?)
Alternatively, you might be able to rig a
proxy server on 10.10.0.9 which would forward
requests on port 443 to the other server at
10.10.0.2. Not so efficient as letting the
router do the work, though.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-07-2011 05:06 AM
тАО04-07-2011 05:06 AM
Re: named + https
http://www.askapache.com/htaccess/reverse-proxy-apache.html
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-07-2011 05:20 AM
тАО04-07-2011 05:20 AM
Re: named + https
RedirectMatch permanent /(.*) https://mail.mydomain.com/
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-07-2011 05:22 AM
тАО04-07-2011 05:22 AM
Re: named + https
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-07-2011 07:39 AM
тАО04-07-2011 07:39 AM
Re: named + https
router already. Why not use it?"
The router does the job perfectly well while I connect from outside of the network.
The 443 is nated to 10.10.0.2 and 80 to 10.10.0.9.
But I'm trying to connect from inside and the router is not in the path.
Proxy or rewrite sounds all right to me.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-07-2011 10:36 AM
тАО04-07-2011 10:36 AM
Re: named + https
> the router is not in the path.
It is if you talk to the router. It isn't if
you don't talk to the router. _I_ didn't
configure your name resolution this way.
Around here, "mydomain.com" always returns
the address of my router. If I want to talk
directly to a local system, then I don't use
that outside-world name.
> Proxy or rewrite sounds all right to me.
If you insist on avoiding the router, then
I'd probably agree.