Problem DNS challenge

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

I wonder if I can draw on some of you lots collective brain power, I'm sure this is easy but I cant for the life of me figure it out.

I have an external domain which hosts our website (company.co.uk for instance), there is also a subdomain (app.company.co.uk) which is hosted internally. Now our internal users cannot view the internally hosted website site because of the circular action the resolving is taking. I would like them to resolve the sub domain directly to the internal ip of the server but cannot quite get it working correctly.

I have set up a forward zone in dns called App.company.co.uk and so far theres an A record (manually created pointing to the internal web server) and 2 ns records. so pinging app.company.co.uk resolves to internal IP correctly.

However because our site is published such as http://app.company.co.uk pinging this still resolves to the external ip and I cant figure out how to get it resolving internally. I cannot set up a zone for http://company.co.uk so any pointers would be most gratefully received.

 

Yes I get "the name is invalid" when I try create it. Slight typo there I've tried creating a primary zone for "http://app.company.co.uk" which doesn't work presumably because of the http:// bit I guess.

 

Thanks for that sparky, I've now created a company.co.uk foward lookup zone with www as the external company server and app as the internal ip address. its still not working correctly, now in my little brain if I ping app.company.co.uk I get the correct internal ip back but if I ping http://app.company.co.uk I get unable to find host. most of the time you can ping external websites happily using http so what is causing this.

 

I wasn't too sure I can ping my blog using http://dales-diary.co.uk so got myself a bit confused as to why this doesn't work here. If I goto http://app:81 or http://app.company.local:81 then I can login to the app and all sorts of cool stuff, but it appears when you login from app.company.co.uk (i.e. you get the login page but nothing entering details and clicking go times out with a usual page cannot be displayed). I think that we've exhausted all possible dns reasons for the trouble so I'm thinking it might be an iis or the way the site is coded.

I guess as a workaround for the moment I could give a users a link to the http://app:81 which should work, not slick but it does work.