Re: Windows 2003 DCs changing DNS zones in BIND

In news:1124792035.929455.92550@xxxxxxxxxxxxxxxxxxxxxxxxxxxx,
benlonguk@xxxxxxxxxxx <benlonguk@xxxxxxxxxxx> made this post, which I then
commented about below:
> Hi,
>
> Hopefully someone can help with this despite it being one of those
> problems where you're not 100% sure on what group if should belong. So
> I will probably end up repeating this in other groups if I have no
> luck.
>
> We have a Windows 2003 Active Directory using BIND for DNS running on
> UNIX servers. Our DCs are the only machines allowed to dynamically
> update DNS so we're sure the DCs are causing the problem.
>
> The problem is our developers in their wisdom have created a number of
> test web servers with dots in their name e.g. test.server and
> web.test. These are registered in DNS as aliases so they can be
> accessed using the hostname. When our DCs start up they intepret the
> dots and changes the zone information so that they're sub zones so
> web.test becomes an host entry web in the sub zone
> test.ourcompany.com.
>
> It wouldn't be so bad if it worked but web.test and
> web.test.ourcompany.com doesn't work either.
>
> Has anyone seen this happen or can anyone think of a fix to prevent
> the DCs trying to be helpful and fixing this problem.
>
> Thanks for your time
>
> Ben.

I'm not sure I entirely understand the problem. What exactly is not working
with web.test or web.test.company.com? You mean accessing the web server?
Using IE, when you enter http://web.test.company.com, does it resolve to the
correct IP address of the webserver? Is the webserver the DC?

Now if you try to enter http://web.test, I can understand that not being
able to work, since that will not resolve.

How is web.test being registered by the DCs? Was that zone added as a suffix
in IP properties, advanced, DNS tab, and set to "register this connection in
DNS"?

What exactly did the web devs do on the DC?

Also, if accessing IIS, keep in mind hostheaders play a major role and if
they don't match the URL (which should be the FQDN), it won't connect.

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services
Infinite Diversities in Infinite Combinations.
=================================




.

Relevant Pages

  • Windows 2003 DCs changing DNS zones in BIND
    ... We have a Windows 2003 Active Directory using BIND for DNS running on ... update DNS so we're sure the DCs are causing the problem. ... test web servers with dots in their name e.g. test.server and web.test. ... the zone information so that they're sub zones so web.test becomes an ...
    (microsoft.public.win2000.dns)
  • Re: I can not figure out why?
    ... I have two windows 2000 DCs and two Windows 2003 DCs. ... all workstations new DNS to point the new DNS through the DHCP server ... you must be careful when selecting the new servers to be DNS servers. ... If the zone is ...
    (microsoft.public.windows.server.active_directory)
  • Re: Scavenging question
    ... I think that "DCpromo cycling" mentioned by Herb means "Demote your DCs and ... If you have another DC, you can transfer FSMO to that DC, clean install the ... Clients recieve all DNS information via DHCP so in that way XP ...
    (microsoft.public.win2000.dns)
  • Re: Can I Round Robin DCs?
    ... To make sure that everything is setup correctly rin dcdiag and netdiag on ... Assuming that both DCs are also DNS servers, ... clients have them both in NIC DNS settings. ... DCs in the clients site. ...
    (microsoft.public.windows.server.dns)
  • Re: Weird network failure/ duplicate machine name MYSTERY, 2003 AD
    ... I have two DCs.. ... Ideally the two DHCP servers offering on the same subnet will PRECISELY ... So then I decided just to give one of the DCs a reboot (the main one, ... DNS Clients must also use STRICTLY the INTERNAL ...
    (microsoft.public.windows.server.general)