Dumb question on Hosts file - DNS migration

[Michael Voight]

If the localserver entry is different at different locations, then a
hostsfile might be necessary. One alternative: On the primary, put a NS
record for localserver.theory.co.nz pointing at localhost. DNS should
have an A record for localhost, or localhost.thecoy.co.nz as 127.0.0.1.
Then, on the local DNS secondary server for theory.thecoy.co.nz, you put
a secondary zone for the domain localserver.theory.co.nz. In this zone,
you put the A record for the local localserver.

Michael


James Hall-Kenney wrote:
> 
> Hi all,
> 
> The following is a dumb question but I'm sort of obliged to ask it in
> case someone has been here before.
> 
> I'm working on a project to migrate an organisation away from host files
> towards a private DNS infrastructure.
> 
> One of the challenges I am hitting is the fact that legacy workstation
> and host scripts make use of a host file entry "localserver".  This
> entry is different depending on which site you are at.
> 
> The scale of the implementation doesn't justify any depth of hierarchy
> beyond "thecoy.co.nz." ie there is no requirement for
> "site.thecoy.co.nz".
> 
> Has anyone come across a smart way of dealing with this?  At the moment,
> we are looking at leaving a host file behind on the workstations with a
> customised localserver entry until someone fixes the scripts however
> this is being frowned upon as someone has done the "hosts file bad - DNS
> good" speech.
> 
> We are looking at options for DHCP to supply the local server name and
> doing some global search and replaces on the scripts ...
> 
> Any polite suggestions gratefully received.
> 
> Cheers
> 
> J.
> 
> James Hall-Kenney
> mailto: jhall at sytec.co.nz