I am a dev-op (a software developer who has to do IT on the side). As a website developer, I create DNS host entries on my local Windows 2003 DNS servers - there are two DNS servers in the local domain - so that I can set up IIS7 websites on my Windows 7 development box.
My method is to add the given client's domain to a zone on my DNS server; copy across all the MX records from the primary nameserver; add a www A record; and then my own dev A record. This way users on my domain (graphic designers, etc) and I get to see the public website and the development website, but the public at large don't get to see the latter.
From time to time - which is a bit weird - I have a problem with Windows 2003 DNS resolving these entries. It adds my local domain (cazburo.co.uk) to the DNS search eg sc-asphalte.fr.cazburo.co.uk shown below:
------------ Got answer: HEADER: opcode = QUERY, id = 2, rcode = NXDOMAIN header flags: response, auth. answer, want recursion, recursion avail. questions = 1, answers = 0, authority records = 1, additional = 0 QUESTIONS: sc-asphalte.fr.cazburo.co.uk, type = A, class = IN AUTHORITY RECORDS: ...
Appending a dot onto the FQDN ie dev.sc-asphalte.fr resolves correctly, but users don't expect to do this and browsers are not mad about it either giving bad host responses some of the time.
The rationale for appending a suffix onto the DNS query before attempting to resolve the query 'as is' first eludes me. However this is the behaviour I would like: attempt resolution 'as-is', then resolve with suffixes, go to fowarders, etc. Is there any way of achieving this with Windows 2003+ (I'll upgrade from Windows 2003 if necessary)?
PS things that I have tried:
- disabled DNS Devolution with a Group Policy setting http://technet.microsoft.com/en-us/library/ee683928%28WS.10%29.aspx
- removed 015 DNS Domain Name from the DHCP Scope Options
- removed the forwarders for All other DNS domains in the DNS Server properties, Forwarders tab - it had been set to Google's public server 18.104.22.168
Other settings that may have a bearing:
- the DHCP Scope Options for 005 Name Servers and 006 DNS Servers are set to the internal domain DNS servers.
- all client computers use DHCP for network configuration