Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.java.programmer > #38466 > unrolled thread
| Started by | Eric Douglas <e.d.programmer@gmail.com> |
|---|---|
| First post | 2018-07-03 08:34 -0700 |
| Last post | 2018-07-03 13:56 -0700 |
| Articles | 4 — 2 participants |
Back to article view | Back to comp.lang.java.programmer
Not Java related, anyone know a way to passthrough a web site? Eric Douglas <e.d.programmer@gmail.com> - 2018-07-03 08:34 -0700
Re: Not Java related, anyone know a way to passthrough a web site? Eric Douglas <e.d.programmer@gmail.com> - 2018-07-03 11:46 -0700
Re: Not Java related, anyone know a way to passthrough a web site? Martin Gregorie <martin@mydomain.invalid> - 2018-07-03 19:25 +0000
Re: Not Java related, anyone know a way to passthrough a web site? Eric Douglas <e.d.programmer@gmail.com> - 2018-07-03 13:56 -0700
| From | Eric Douglas <e.d.programmer@gmail.com> |
|---|---|
| Date | 2018-07-03 08:34 -0700 |
| Subject | Not Java related, anyone know a way to passthrough a web site? |
| Message-ID | <22d85c36-a5e1-4cc7-a2f4-d666bfa94e39@googlegroups.com> |
I'm not sure if there's a different forum to sign up for or where is the best place to ask this kind of question. We just moved our website, I changed the IP in our DNS and now it doesn't work. Previously if we put our web address into a browser it would pull up our site but now inside our network where the site domain is the same name as our internal domain it just pulls up the default landing page for our IIS server. The only obvious answers I've found are to disable IIS which we can't do because we're using it, or change the internal domain name. I'm not sure how this was working previously, if there's something else I need to change, or if this just won't work with the new host. Our old site was running Javascript with a PHP backend, the new site is running wordpress where multiple sites map the the same IP. I've tried many configurations now using the DNS and the IIS server trying to get the domain requests to ignore the IIS or pass through and the best I could get is the 404 page not found message showing the wordpress host. The only other thing we can think of is registering an additional domain for internal use which does nothing but redirect to our site.
[toc] | [next] | [standalone]
| From | Eric Douglas <e.d.programmer@gmail.com> |
|---|---|
| Date | 2018-07-03 11:46 -0700 |
| Message-ID | <7212cddb-f22f-44c9-b616-74d6a92c7500@googlegroups.com> |
| In reply to | #38466 |
On Tuesday, July 3, 2018 at 11:35:15 AM UTC-4, Eric Douglas wrote: > > We just moved our website, I changed the IP in our DNS and now it doesn't As far as I can tell, our marketing company is not too bright. It appears they set up our new website to resolve without www. and it appears there should be an option on that host to resolve it with the www, and if you resolve it without and the site name matches the internal domain and you have an internal web service running there is no way to get to the web site. I don't know what sort of trouble it could cause to rename an internal domain. Our best bet is to see if those idiots can add the www.
[toc] | [prev] | [next] | [standalone]
| From | Martin Gregorie <martin@mydomain.invalid> |
|---|---|
| Date | 2018-07-03 19:25 +0000 |
| Message-ID | <phgijp$vg5$1@news.albasani.net> |
| In reply to | #38467 |
On Tue, 03 Jul 2018 11:46:30 -0700, Eric Douglas wrote: > On Tuesday, July 3, 2018 at 11:35:15 AM UTC-4, Eric Douglas wrote: >> >> We just moved our website, I changed the IP in our DNS and now it >> doesn't > > As far as I can tell, our marketing company is not too bright. It > appears they set up our new website to resolve without www. and it > appears there should be an option on that host to resolve it with the > www, and if you resolve it without and the site name matches the > internal domain and you have an internal web service running there is no > way to get to the web site. I don't know what sort of trouble it could > cause to rename an internal domain. Our best bet is to see if those > idiots can add the www. Been there, done that. The LAN domain should NOT be the same as the external domain. That just causes problems as you're finding out. My LAN is private and has only a few hosts on it, which made changing the internal domain name very easy: my external domain is a .org, so all the FQDNs on my LAN end in .lan - yes, its non-standard but, as it will not/ should not resolve externally and I don't accept inward traffic: it gets retrieved from my ISP's smarthost by getmail and passed to my internal mailserver for spam scanning and delivery, so who cares that the internal TLD is nonstandard? Not me, for sure. I run an internal webserver which is never externally visible. It serves private pages internally and also holds the master copies of my public websites. These are hosted externally and maintained by FTP, i.e. replacement and new web pages are developed internally and published by sending them to the webhost. I think something like this should work for you too: your public-facing firewall is, or should be, capable of forwarding incoming traffic (mail, web traffic, etc) to the relevant internal host and excluding everything else, so your use of private host names internally shouldn't be a problem or visible externally. You might also consider routing all mail through an internal company mailserver and closing the firewall to direct outgoing mail, because the mailserver can rewrite the From header to hide internal host names. Before you ask: yes, I've been doing this for years without any problem. Side benefits are: - this makes archiving both inbound and outbound business mail very easy - it allows you to use a spam scanner on both inbound and outbound mail. -- Martin | martin at Gregorie | gregorie dot org
[toc] | [prev] | [next] | [standalone]
| From | Eric Douglas <e.d.programmer@gmail.com> |
|---|---|
| Date | 2018-07-03 13:56 -0700 |
| Message-ID | <a2ad6172-fdc0-4a1a-9788-43fb0a1efb7e@googlegroups.com> |
| In reply to | #38468 |
On Tuesday, July 3, 2018 at 3:25:56 PM UTC-4, Martin Gregorie wrote: > Been there, done that. The LAN domain should NOT be the same as the > external domain. That just causes problems as you're finding out. > If I only had a time machine, I could make whoever initially created our internal domain name use something different, but yeah internally it's companyname.com and the website should be www.companyname.com. This works as long as anyone internally trying to view the site types the www and you have a dns entry for www mapped to the external site IP. I did find the setup, not sure why this fool marketing company setup the site without www but I was able to add it in so it works internally now. We had asked them to fix it and they apparently had no clue what we were talking about. They claim to have been in business for years never encountering this problem. > My LAN is private and has only a few hosts on it, which made changing the > internal domain name very easy: my external domain is a .org, so all the > FQDNs on my LAN end in .lan - yes, its non-standard but, as it will not/ > should not resolve externally and I don't accept inward traffic: it gets > retrieved from my ISP's smarthost by getmail and passed to my internal > mailserver for spam scanning and delivery, so who cares that the internal > TLD is nonstandard? Not me, for sure. > > I run an internal webserver which is never externally visible. It serves > private pages internally and also holds the master copies of my public > websites. These are hosted externally and maintained by FTP, i.e. > replacement and new web pages are developed internally and published by > sending them to the webhost. > > I think something like this should work for you too: your public-facing > firewall is, or should be, capable of forwarding incoming traffic (mail, > web traffic, etc) to the relevant internal host and excluding everything > else, so your use of private host names internally shouldn't be a problem > or visible externally. > > You might also consider routing all mail through an internal company > mailserver and closing the firewall to direct outgoing mail, because the > mailserver can rewrite the From header to hide internal host names. > Before you ask: yes, I've been doing this for years without any problem. > Side benefits are: > > - this makes archiving both inbound and outbound business mail very easy > > - it allows you to use a spam scanner on both inbound and outbound mail. > My IIS internally is doing a couple things. I have one setup for WSUS. I have one setup for my Java application which loads through JNLP. We use gmail, hasn't been a problem. They do all the spam scanning virus checking for us pretty well. Internally we also have a Cisco firewall and McAfee for virus and malware. Google also has an API for everything. They have a button on the admin page to generate an email archive, or you can pull everyone's emails through the API.
[toc] | [prev] | [standalone]
Back to top | Article view | comp.lang.java.programmer
csiph-web