Jump to content

Recommended Posts

Posted

We have a Moodle server here, and at the minute when a user goes to moodle.domain.com it go out on the internet to retrieve it.

 

I have set up DNS so that moodle.domain.com goes to the internal IP of xxx.xxx.xxx.xxx which works a treat, but if I try to go to http://www.domain.com it throws a "cannot find server".

 

How do I open up (using internal DNS) moodle.domain.com to go to our internal IP but all other *.domain.com resolves using external DNS.

Posted
Get the properties of the DNS server in the DNS MMC, and on the Forwarders tab pick 'All other DNS domains' and add your upstreams into the bottom section. Remember to hit Add to actually put them into the list.
Posted
Get the properties of the DNS server in the DNS MMC, and on the Forwarders tab pick 'All other DNS domains' and add your upstreams into the bottom section. Remember to hit Add to actually put them into the list.

 

I right-clicked on the new zone I added, went to properties and then forwarders. Clicked all other DNS domains and it already has 2 IP's in there.

Posted

What I did was manually added the static public ips for to the domain names manually into dns as there’s not that many on most domains. E.g. http://www.domainname .co.uk (public ip) mail.domainname.co.uk(public ip) imail.domainname.co.uk(public ip) and moodle.domainname.co.uk (with internal ip) folders.domainname.co.uk (with internal ip) intranet.domainname.co.uk (with internal ip) I think I had to put in another one for ISP mail server but you get the idea.

 

I got the public static ip’s by using Convert Host Name to IP Address or Find IP address of a host - e.g. find IP address of host name of to convert them.

 

Hope that helps

Posted
What I did was manually added the static public ips for to the domain names manually into dns as there’s not that many on most domains. E.g. www.domainname .co.uk (public ip) mail.domainname.co.uk(public ip) imail.domainname.co.uk(public ip) and moodle.domainname.co.uk (with internal ip) folders.domainname.co.uk (with internal ip) intranet.domainname.co.uk (with internal ip) I think I had to put in another one for ISP mail server but you get the idea.

 

I got the public static ip’s by using Convert Host Name to IP Address or Find IP address of a host - e.g. find IP address of host name of to convert them.

 

Hope that helps

 

But we have forwarders like

 

add1.domain.com which directs to 123.123.123.123/add1
and
add2.domain.com which directs to 123.123.123.123/add2

 

So we can't do it the way you suggest.

 

Any other thoughts?

Posted

From my understanding once you add a domain as a zone on your dns servers it becomes authoritative thusly you cannot pick and chose which subdomains you want it to answer for. You need to do as microdigit suggests and add all sub domains as exist on your public dns server.

 

The fact that you have multiple sub domains that may or may not point to different servers should not matter. So long as the subdomain and ip are the same between both dns servers it is the web server that resolves what content should be returned.

 

Matt

Posted
If you have a zone for the .domain then yep.

 

Which I have - that was the easy part.

 

The thing is, now I have that domain set up as a zone, I want to be able to say (excuse my pseudo code haha) "if the prefix (www. or ww2. etc) doesn't exist in this zone, find it on the internet."

Posted
Which I have - that was the easy part.

 

The thing is, now I have that domain set up as a zone, I want to be able to say (excuse my pseudo code haha) "if the prefix (www. or ww2. etc) doesn't exist in this zone, find it on the internet."

 

That should work anyway...

 

here we have

 

vle.* (moodle)

comm.* (moodle)

mail.* (exchange)

folders.* (webfolders)

share.* (sharepoint)

 

They are all internal

 

http://www.* (website)

 

Is external, but isnt listed in the zone, so goes out on the internet to fetch.

We mainly did first due to moodle, having upgraded to 1.9 ove the summer from 1.7, and was having issues with the fix to get around the server having 2 domains.

We then added mail and share, as we purchased a wildcard SSL cert for our domain.

 

Gary

Posted
That should work anyway...

 

here we have

 

vle.* (moodle)

comm.* (moodle)

mail.* (exchange)

folders.* (webfolders)

share.* (sharepoint)

 

They are all internal

 

www.* (website)

 

Is external, but isnt listed in the zone, so goes out on the internet to fetch.

We mainly did first due to moodle, having upgraded to 1.9 ove the summer from 1.7, and was having issues with the fix to get around the server having 2 domains.

We then added mail and share, as we purchased a wildcard SSL cert for our domain.

 

Gary

 

See, that's exactly what I want yet for some reason it's not working. if I try http://www.* (because I haven't added a www look-up) I get a "server cannot be found" message instead of the externally hosted website.

 

Any ideas why this is so, and what I might need to look at to correct this?

 

Many thanks,

Posted

You need to do as below because as soon as you set it as a record on your DNS it is authorotive:

 

Re: Non authoritative domain on Windows Server 2003

You could create a zone called "hostname.domainname.com" and then within

that zone create a blank host A record (same as parent) pointing to the

relevant internal IP

 

Then your server would only be authorative for the zone "hostname.domainname.

com"and any records within that zone (such as the same as parent host record

you need)

 

Only drawback to this is you have to create a separate DNS zone for each host

and a same as parent record but it works

  • Thanks 1
Posted

I would just make a new forward lookup zone of moodle.domain.com (I assume on zone is domain.com) and create a blank A record with the IP.

That *should* work?

Posted
See, that's exactly what I want yet for some reason it's not working. if I try http://www.* (because I haven't added a www look-up) I get a "server cannot be found" message instead of the externally hosted website.

 

Any ideas why this is so, and what I might need to look at to correct this?

 

Many thanks,

 

Is you www. internal or external?

 

If external, then you dont need one.

 

Gary

Posted
Is you www. internal or external?

 

If external, then you dont need one.

 

Gary

 

If you mean where is it hosted, it's hosted externally. As I said, I haven't added a forwarder but I get that error - so there's obviously something not right.

Posted
If you mean where is it hosted, it's hosted externally. As I said, I haven't added a forwarder but I get that error - so there's obviously something not right.

 

Have you done what I said or are you trying the * thing?

Create a forwarder like I said above and it should work.

Posted
Have you done what I said or are you trying the * thing?

Create a forwarder like I said above and it should work.

 

Sorry ZH - only just noticed your response, didn't realise we were now on two pages.

 

The problem with doing it your way is our default zone is:

 

domain.internal

 

and I've just created domain.co.uk as an extra zone.

 

Should I still be able to carry out your recommendations?

Posted

your forward lookup zone would be moodle.domain.co.uk then make the blank A record and it should be fine.

delete domain.co.uk if you made it though as that could cause other issues.

  • Thanks 1
Posted
your forward lookup zone would be moodle.domain.co.uk then make the blank A record and it should be fine.

delete domain.co.uk if you made it though as that could cause other issues.

 

Just to verify before I do this....

 

I have DOMAIN.internal and DOMAIN.co.uk

 

You're saying to delete DOMAIN.co.uk and create moodle.DOMAIN.co.uk

 

Can I create as many of these as I want? As I would also like whitelist.DOMAIN.co.uk to be directed as well.

Posted

as long as you are not using domain.co.uk yeh you can delete it. Are their records?

you can leave it for now as it wont stop the new areas working and yes you can use it for other things you need to map.

E.G. {something}.whitelist.domain.oc.uk could be set by making a forward zone of whitelist.domain.co.uk and then you make A records for each "something"

Posted
as long as you are not using domain.co.uk yeh you can delete it. Are their records?

you can leave it for now as it wont stop the new areas working and yes you can use it for other things you need to map.

E.G. {something}.whitelist.domain.oc.uk could be set by making a forward zone of whitelist.domain.co.uk and then you make A records for each "something"

 

That seems to be working by carrying out those instructions. Cheers folks :D

 

Happy for another day haha

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 account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...