DNS HELP

Right he is the situation.

Currently have an Apache web server with a Joomla install and dev Moodle install. There is a dns entry call intranet that points to the server IP and it works fine.

This server can now be accessed from outside the network via intranet.schoolsdomain.sch.uk We cannot access via this address internally.

The problem is that the websites dont work due to the live site addresses being intranet/joomla and not intranet.schoolsdomain.sch.uk/joomla.

So i decided to create a dns record for intranet.schoolsdomain.sch.uk to point to the server IP like above, so making the live site info the same for both inside / outside access.

This seems to be working from both W2k3 servers, but when you try from any XP workstation nothing happens.

So what am I missing?

Have you flushed the DNS resolver cache on the workstations?

ipconfig /flushdns
ipconfig /registerdns

Or are they resolving their web addresses via a proxy? You may have to add the site to the exclusions list.

Yep done that. Pinging the address brings up the correct ip address. NSLOOKUP on the address bring up the correct ip address. The dns table has the correct info.

IE just says opening page and nothing happens.

now thats just wierd, its started working all of a sudden. grrrr damn computers lol

Cheers for the quick responce though DB :D

Windows DNS services take a little while to make a new hostname work. If you want DNS that works instantly (rather than when it gets round to it) use a real DNS server.

I have noticed the same thing when adding cnames for local servers. It seems to take a long time even when it should have already updated all the servers.

Glad its not just me then :D

DNSMasq running on Linux works fine as the primary DNS/DHCP for a Windows domain if your interested in an alternative.

http://thekelleys.org.uk/dnsmasq/doc.html

as much as I think every school should have a propoer box doing DNS for the important machines in a school, the extra AD related bits that are put into DNS on a windows box should only be done on a wondows box.

If DNS is going pear-shaped I would rather solve the problem than put it onto another box. A scenario I have used before is to have the DNS on the DCs point at a *nix box and telling them to pull info for specific domains from there (eg use domain.school for the AD Domain, and have the records for school.area.sch.uk on the *nix box).

Worked fantastically ...

Quote:

---

the extra AD related bits that are put into DNS on a windows box should only be done on a wondows box.

---

It's just a bunch of SRV records. It's not really an issue.

Quote:

---

as much as I think every school should have a propoer box doing DNS for the important machines in a school, the extra AD related bits that are put into DNS on a windows box should only be done on a wondows box.

---

since version 8.x BIND fully supports active directory

BIND is probably a bit OTT for most people here though. That's why I suggested dnsmasq.

The recent times I have had BIND (on Solaris 8) and AD side by side there have been issues with authenticating updates between DCs (which must have the SVR records for their roles to function properly) and the solaris boxen.

Once I got SfU 3.5 happy it was better, but it was a level of obfustication that could easily be ruled out.

I still believe in the adage: the more complicated it is the easiest it is to go wrong.

Um, you do know that the DC's produce a text file in there system32 folder detailing the SRV records they need...?