Our PDC and primay DNS is a Windows 2003 server. That server has 2
NICs - 1 for our internal network, and the 2nd for a different,
private network. The IP config looks something like this:

PDC Machine name: Server1
PDC IP: 172.5.5.1
Internal network: 172.x.x.x/255.0.0.0
Private network: 10.1.15.x/255.255.255.0

After tracking down some bizarre time problems over the weekend I
discovered that dns queries for Server1 were returning addresses for
both NICs - which is not the intended operation. For my machines that
were in the same subnet as Server1, they could figure out a route to
the 172 address without a problem. Machines that aren't in the same
subnet, though, are confused since the routes to 10.x.x.x and
172.5.5.x are the same cost. What's worse is that no machine has
connectivity to 10.x.x.x except Server1.

Basically, the 10.x.x.x address shouldn't be published in the DNS. I
tried just removing the A records from the DNS console, but a few
minutes later it re-appeared. When I look at the properities of the
adapter, "Register this connection's addresses in DNS" is not
checked.

How can I prevent any evidence of this 2nd NIC from appearing in DNS?

Thanks... Shaun McGuire

Hi Shaun,

Hopefully, I have understood your request correctly.

Open the DNS Management Console; right click on the server node; choose the
"Interfaces" tab and select "Only the following IP Addresses"; the list
should only show the ip addresses of interfaces you want DNS to bind to.

Regards,

Paul MaC


<mcguire731@gmail.com> wrote in message
news:1173769445.685787.160160@j27g2000cwj.googlegr oups.com...
> Our PDC and primay DNS is a Windows 2003 server. That server has 2
> NICs - 1 for our internal network, and the 2nd for a different,
> private network. The IP config looks something like this:
>
> PDC Machine name: Server1
> PDC IP: 172.5.5.1
> Internal network: 172.x.x.x/255.0.0.0
> Private network: 10.1.15.x/255.255.255.0
>
> After tracking down some bizarre time problems over the weekend I
> discovered that dns queries for Server1 were returning addresses for
> both NICs - which is not the intended operation. For my machines that
> were in the same subnet as Server1, they could figure out a route to
> the 172 address without a problem. Machines that aren't in the same
> subnet, though, are confused since the routes to 10.x.x.x and
> 172.5.5.x are the same cost. What's worse is that no machine has
> connectivity to 10.x.x.x except Server1.
>
> Basically, the 10.x.x.x address shouldn't be published in the DNS. I
> tried just removing the A records from the DNS console, but a few
> minutes later it re-appeared. When I look at the properities of the
> adapter, "Register this connection's addresses in DNS" is not
> checked.
>
> How can I prevent any evidence of this 2nd NIC from appearing in DNS?
>
> Thanks... Shaun McGuire
>