DNS Issue for FireFly setup

[BarriedaleNick]

Hi all,

 

We are setting up FireFly here it is setup internally on 192.168.1.80 - our internal domain is myschool.local handled by our local DNS server on 2008 R2

 

Externally this is known as learning.myschool.org.uk and this has been setup at the ISP who handles our external DNS on one my public IPs.

 

However for several reasons we can't use the internal name learning.myschool.local in school (Due to friendly urls and auto login) so we use the external one which breaks autologin etc//

 

The support suggested that I set my DNS up so that learning.mychool.org.uk maps to 192.168.1.80.

 

Can this be done by editing DNS on server 2008 R2?

 

I am pretty sure it cant other than by the use of a hosts file (which does work but is a terrible idea and wont work for tablets etc)

[benjie]

Hi,

 

If you open you DNS management console, right click on "Forward Lookup Zones", select "New Zone". Follow the wizard creating a zone called myschool.org.uk. Then create a new A record call learning under the new zone and map it to 192.168.1.80.

 

Hope this helps.

[BarriedaleNick]

Cheers benjie - Sounds too easy! Does this have any knock on effects for other web services like http://www.myschool.org.uk, mail.myschool.org.uk, schoolbase.myschool.org.uk or will the DNS forwarders take care of that and forward upstream?

[benjie]

I would just put the records in just to be on the safe side.

[BarriedaleNick]

Cheers - I had to add all our internal and external sites and now it seems to be fine and I can access sites internally and externally.

Now to reinstall FireFly!