DNS Design Questions

[juniorb2000]

Hi everyone, I've checked out this forum and it looks excellent so thought I'd give it a go!!

A quick theoretical MS DNS question. I have clients in various locations whose DNS suffix is set to company.co.uk. It needs to resolve the name of a server called server1.

Obviously the A record for that server could be put straight into the company.co.uk forward lookup zone and all would work ok. My question really is this - If I were to put the A record in another forward lookup zone called site1.company.co.uk and an alias to that record in company.co.uk, is it significantly more work for the server to resolve?(basically is it like 2 lookups?) I say 'signifcantly' in the context of this one lookup as in reality I may have similar zones set up for site2, site3 etc, with a number of servers' A records in each and aliases to them in company.co.uk like before. I definately want all the clients to have the DNS suffix company.co.uk wherever they may reside for consistency.
Hope you can help..
Big Thanks. jR

 

[Nostradamus]

We've used aliases in our organisation both before AND now. Much like the way you asked. We used bind on solaris back then, but the principle is the same. Now we use m$ DNS.

We've never had any problems using aliases the way you describe. We use the same suffix on all our clients and the load on the dns server(s) running aliases and subdomains have never been any worries. I don't think it should pose a problem for you, but the best way is always to test.

/Sören