DNS Issue

[LloydSev]

OK.. I have 2 Windows 2000 Servers running DNS.

Server # 1 handles DNS Primarily.
Server # 2 handles DNS Secondary, as well as dial-in.

Problem, the dial-in NIC IP address seems to find it's way into DNS every once in a while. This throws off the company, as Server # 2 also hosts our intranet site off it's first NIC.

NIC # 1 = *.*.*.3
NIC # 2 = *.*.*.63

So when NIC # 2 gets into DNS, some users try hitting the intranet site through the .63 address. How can I prevent this from happening anymore?

Computer/Network Technician
CCNA

 

[LloydSev]

bump

Computer/Network Technician
CCNA

 

[spike0724]

Active Directory integrated? Also want to check to see if Primary DNS server is allowing automatic updates... If so you may want to turn that off or select who can/cannot update it.

S. Mike Harris

"If there we 90 seconds in a minute, I might get everything done in a day" - S. M. Harris

 

[LloydSev]

yes Active Directory integrated.. both servers are Active Directory DCs.

Computer/Network Technician
CCNA

 

[wcburton]

Each NIC maintains a separate setting for whether or not to "Register this connection's addresses in DNS". This is found under the Advanced properties for TCP/IP. I do not know how your dial-up is set. If it does not expose that properties page, you may be able to accomplish that with a change to the registry.

 

[LloydSev]

OK.. I guess I was mistaken..

the machine does not have 2 NICs.. it has multiple interfaces

In RRAS it lists the following as interfaces

Loopback - 127.0.0.1
Internal - 193.100.1.63
(NIC) - 193.100.1.3

I need to stop the internal interface from registering in DNS.. and it does not list it in Network & Dial-Up Connections.

Computer/Network Technician
CCNA

 

[LloydSev]

bump

Computer/Network Technician
CCNA