How do I disable a NIC from registering itself in DNS?

[Jim Rodgers]

I have a DNS/AD/Exchange server that has two NICs in it
(one has a 192.168.x.x IP) and the other has a public IP.

My Exchange (5.5) server on this box will not RECEIVE mail
when the 192.168.x.x address is listed in DNS.

There are two entries in DNS for this box, one with the
public IP and one with the private IP.
EVERYTHING works flawlessly when I delete the private IP
listed in DNS, but it will automatically put itself back
in there after a while (Dynamic DNS is disabled, but I
would like to be able to enable it, also on the TCP/IP
settings for the private IP, I have the box UNCHECKED
to "Register in DNS").

So my question is this:
What's causing this card to keep showing up in DNS or what
can I do to make my Exchange server start receiving mail
(it sends fine) while this private IP is listed in DNS??

Thanks for the help!

Jim Rodgers
(e-mail address removed)

 

[Simon Geary]

Domain Controllers and DNS servers have other methods they use to register
with DNS. This article explains what is going on and how to disable dynamic
DNS. http://support.microsoft.com/?id=246804

 

[Guest]

THANKS!
That may be the answer, but with one exception.
The section on DNS Servers says to post the IP address in
the registry, unfortunately, I have a dynamic IP address
and when it changes, I may be in trouble if I do it this
way.
I do use a service called TZO for resolving my domain name
with a dynamic IP, can I just put in my domain name
instead of a specific IP?

 

[Ace Fekay [MVP]]

In

THANKS!
That may be the answer, but with one exception.
The section on DNS Servers says to post the IP address in
the registry, unfortunately, I have a dynamic IP address
and when it changes, I may be in trouble if I do it this
way.
I do use a service called TZO for resolving my domain name
with a dynamic IP, can I just put in my domain name
instead of a specific IP?

If you are using TZO for DNS, then why are you using your DNS for your
domain? If the public is accessing your machine via TZO, it doesn't make
sense, unless I'm missing something here.

You could also strip out that extra NIC and use a NAT/router and port
forward mail traffic to this machine. As far as internet users are
concerned, they are only looking up the WAN IP of the router, not the
private IP. Unless of course you have your DNS server listed as the second
nameserver for your domain name, which then I would suggest to use two DNS
servers, one for internal private usage (for AD and such) and one to host
the public data that is needed. ALl machines would use the internal DNS
only, and forward to the ISP's DNS. THis is common practice if you are
hosting your own DNS and are using private IPs because MS DNS has no
provisisons to host both private and public data on one box. BIND does, but
not MS.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory