Domain Server changes DDNS address (Windows Server 2008)

Hello,

I have a Windows Server 2008 server that is part of an Active
Directory domain, it has one NIC and that NIC has 5 IP address
associated with it, each of them on the same subnet. I have a number
of servers that are configured this way, but this it the first 2008
machine (the rest are 2003). On the Windows Server 2003 servers the
hostname and DDNS names always mapped to the main, first IP, I
specified in the NIC's TCP/IP properties. However, on my 2008 machine
it seems to be mapping to a random IP.

What would be causing this behavior and how can I get DDNS to map to a
specif IP that is configured on that machine?

Thanks,
Patrick

On Oct 10, 11:12*am, keenan....@gmail.com wrote:
> Hello,
>
> I have a Windows Server 2008 server that is part of an Active
> Directory domain, it has one NIC and that NIC has 5 IP address
> associated with it, each of them on the same subnet. *I have a number
> of servers that are configured this way, but this it the first 2008
> machine (the rest are 2003). *On the Windows Server 2003 servers the
> hostname and DDNS names always mapped to the main, first IP, I
> specified in the NIC's TCP/IP properties. *However, on my 2008 machine
> it seems to be mapping to a random IP.
>
> What would be causing this behavior and how can I get DDNS to map to a
> specif IP that is configured on that machine?
>
> Thanks,
> Patrick

I just did an nslookup on my hostname it returned all 7 of the IPs
that are associated with my server. This has never happened before on
any of my systems, why would it now?

Thanks,
Patrick

Hello (E-Mail Removed),

What's the reason for this configuration?

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Hello,
>
> I have a Windows Server 2008 server that is part of an Active
> Directory domain, it has one NIC and that NIC has 5 IP address
> associated with it, each of them on the same subnet. I have a number
> of servers that are configured this way, but this it the first 2008
> machine (the rest are 2003). On the Windows Server 2003 servers the
> hostname and DDNS names always mapped to the main, first IP, I
> specified in the NIC's TCP/IP properties. However, on my 2008 machine
> it seems to be mapping to a random IP.
>
> What would be causing this behavior and how can I get DDNS to map to a
> specif IP that is configured on that machine?
>
> Thanks,
> Patrick

This server host multiple websites that all have different IPs

I would add that excluding the target IP addresses from DDHCP assignment
might be a good idea. Also look into reservations, see if that is possible
when serveral IP addresses are mapped to a single NIC. After thought: What
is the brand of the NIC? Is it intelligent?



"Bill Kearney" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) t...
>> I have a Windows Server 2008 server that is part of an Active
>> Directory domain, it has one NIC and that NIC has 5 IP address
>> associated with it, each of them on the same subnet. I have a number
>> of servers that are configured this way, but this it the first 2008
>> machine (the rest are 2003). On the Windows Server 2003 servers the
>> hostname and DDNS names always mapped to the main, first IP
>
> Why do you have multiple IP addresses if you're mapping all of them to the
> same (as you call it 'main') IP address?
>
>> specified in the NIC's TCP/IP properties. However, on my 2008 machine
>> it seems to be mapping to a random IP.
>
> 'It' being what, exactly?
>
>> What would be causing this behavior and how can I get DDNS to map to a
>> specif IP that is configured on that machine?
>
> Set up the DNS records with them? Seems like a no-brainer. Set up the
> NIC with the appropriate STATIC addresses. Then go over to DNS and setup
> each A record appropriately to the desired IP address.

> After thought: Whatis the brand of the NIC? Is it intelligent?

This is a Intel Pro/1000 MT NIC used on a VMware ESX virtual machine
(The NIC is dedicated to my VM).

I should have probably included some more information regarding my
environment. All my IPs are static addresses and there are two DNS
systems on my network - a Unix DNS system which is used for static DNS
entries which all my IPs have entries in and a DDNS system that is
handed by our Active Directory system (every machine in our active
director has at least one entry there).

Having an multiple host (a) records in DDNS for the one hostname is
not so much a problem as it is an annoyance since I still have that
static dns entries I can use. However, I have some services (such as
RDP) that I only have accessible from one of the IPs (the first IPs I
installed on the machine) which is not mapped to any of the website
IPs and I use to just access those services using the hostname, not
the FQDN.

So basically my only question is, why would this have just started to
happen now when I have had many systems set up this way in the past
and there has only been one DDNS record for them.

On Oct 13, 4:15*pm, "Bill Kearney" <wkearne...@hotmail.com> wrote:
> Aren't ALL the DNS records for this setup as static? *You keep writing
> 'DDNS', does that mean you're letting the OS attempt to dynamically update
> them? *If so, why?

Like I said before there are two DNS systems in our environment. The
one that is part of Active Directory is a dynamic DNS setup for all
domain computers. I am not sure why it was set up like this, i am not
a domain admin. However, we have an extremely large environment and
that may have had something do with it.

> That it didn't fail before does mean it was a good idea. *Predictable bugs
> are nothing something on which to base good practices.

So, what you are saying is that the behavior i am experiencing is the
correct behavior, but something in Windows Server 2003 (what all my
other systems are) caused it to act different and only record one IP
in our AD's DNS? If that is the case, I can accept that.