rrafluap Posted January 6, 2017 Posted January 6, 2017 Hey, Having a bit of a nightmare at the moment. We have a school domain name mpsplymouth.net that is primarily used for emails. As its not our primary website domain, I simply had it pointing to one of our servers that has a redirect script as index.html (so I could use subdirectories etc...) Now ive created a subdomain 'site' in IIS (the app im using requires its own Application Pool - PassCore https://github.com/unosquare/passcore). I've installed it as they requested but I cant get the DNS to work properly. Our AD domain ends in .local so every time I create a CNAME entry its creating the FQDN as subdomain.mpsplymouth.net.schoolname.local - This works on the server that IIS is installed on, but on any other computer I get sent to the root site mpsplymouth.net Also have https bindings for the default site and the new one (*:443:subdomain.mpsplymouth.net) - Dont know if thats a contributing factor? Does anyone have any tips? Am I missing something? Thanks,
rrafluap Posted January 10, 2017 Author Posted January 10, 2017 Ok, so a bit of an update. - I've had an external IP set up by SWGfL thats dedicated to the subdomain which is NATed to an additional internal IP - Added the additional IP to the NIC in the adaptor settings - the ip address is outside of the DHCP address pool so wont be conflicting - Created an A record with GoDaddy for the subdomain to the new external IP (mpsplymouth.net - subdomain is selfservice.mpsplymouth.net) Using lookup tools online, it seems to be valid etc... but when i visit the site, it shows a 404 error All of the 'sites' in IIS have a valid page configured for the default document, so i really dont understand where its forwarding / directing it to? Even the subdomain site works via the internal ip so its not even that site? Really bugging me as I cant seem to crack this! Im sure its something silly. Any suggestions, please let me know.
snagrat Posted January 10, 2017 Posted January 10, 2017 Hi Paul. Using mxtoolbox to lookup selfserve.mpsplymouth.net I can't see that anything exist. Is GoDaddy set correctly?
snagrat Posted January 10, 2017 Posted January 10, 2017 Also doing mxlookup on mpsplymouth.net gives the SWGfL external IP but a port scan doesn't do port 80/443 as open, only 1723 for VPN
rrafluap Posted January 10, 2017 Author Posted January 10, 2017 Hi Paul. Using mxtoolbox to lookup selfserve.mpsplymouth.net I can't see that anything exist. Is GoDaddy set correctly? Also doing mxlookup on mpsplymouth.net gives the SWGfL external IP but a port scan doesn't do port 80/443 as open, only 1723 for VPN Its selfservice but that doesnt show up anything either :-/ How should the record be? I was under the impression that setting an A record on the mpsplymouth.net DNS settings that it would work for that? I'll get in touch with SWGfL re the ports not being opened up, they must have misunderstood my request!
snagrat Posted January 10, 2017 Posted January 10, 2017 Port 80 is open on the .251 address you show but not .249 that mpsplymouth.net resolves to. So the port looks ok 1
snagrat Posted January 10, 2017 Posted January 10, 2017 selfservice does resolve but i get the 404 error as well 1
snagrat Posted January 10, 2017 Posted January 10, 2017 Is IIS configured to accept traffic on that internal IP? I know it works internally but possible that is working on the other internal adapter 1
rrafluap Posted January 10, 2017 Author Posted January 10, 2017 The root domain was just forwarded but never actually used. Is IIS configured to accept traffic on that internal IP? I know it works internally but possible that is working on the other internal adapter Is that done via the bindings? If so yes its bound to that ip but if theres another step, i may have missed that.
rrafluap Posted January 11, 2017 Author Posted January 11, 2017 Is IIS configured to accept traffic on that internal IP? I know it works internally but possible that is working on the other internal adapter Ok in the end it looks like ive been a bit of a tool... On the instructions for the script, they only tell you to add an SSL binding. Which makes sense as its a password reset tool. What I didnt think of was that it would need an ordinary http binding to be able to redirect or anything. I added the http binding and Googled a URL rewrite rule to redirect any http traffic to http and bob's your uncle! Thanks so much for your help snagrat! *face palms*
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now