Like you say, you don't really have control over your client's domain names, so you'd need something rooted at the local level...
So if I was you, I'd set it up thus: *.localdev.tunaranch.net : 127.0.0.1. That way, all subdomains of localdev. will go to localhost. This would need virtual hosts to be set correctly, of course. And then, you can set, say, foo-inc.clients.tunaranch.net : <IP for dev box for Foo. Inc> . bar-co.clients.tunaranch.net : <IP for dev box for Bar Co.> . Makes sense? Duncan wrote: > Scenario: > > Web dev shop, lots of clients, lots of domains, using an internal dev > box, using SBS server 2003 > > Problem: > > current DNS is set up for clientname.local and points to the site on > the central dev box > > we are introducing SVN and individual environments on the developers > local machines. > > Ideally I would like to be able to use local.client.com for the local > developer machine, dev.client.com for the dev box etc. > > Clearly we don't have control over the clients DNS so we cant create > these on their domain (and I wouldn't want to as 2 of them would be > useless to external folks). > > So I want to create a couple of entries for an external domain name, > that are available only to our network and have the external entries > still work without us having to maintain a second copy of them (this > appears to be the only solution in SBS DNS). > > Can we do this? How do y'all cope with this? Do I need to look at a > different naming schema? > > -- Haikal Saadh Applications Programmer ICT Resources, TALSS QUT Kelvin Grove --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to cfaussie@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~----------~----~----~----~------~----~------~--~---
