asked on

Windows 2003 Server DNS Issues

I have two windows 2003 servers in our environment setup as DNS servers for our domain. Our website is setup externally from our network for example our domain is example.org and our website is setup as www.example.org and example.org. I have an A record setup for www.example.org, but I also have several (same as parent folder) A records setup for several servers and two 169.254.*.* ip addresses that keep adding them selves in to my DNS records. Once I remove them I am able to visit example.com or www.example.com from our internal lan and access our website, but as soon as 24hrs pass and they get added back into dns the website stops responding. How can I get these ip's to stop populating my dns records?

serchlop

IP address for range 169.254.*.* are called APIPA Automatic Private Internet Protocol Addressing.

I think that your DNS zone is an AD zone and it allow dinamyc updates for the zone.

If this is true, maybe a domain controller for your domain has a network adapter without fixed IP, and when it request an IP address and can not obtain it from a DHCP server, assign APIPA to this NIC. Then the other NIC that contact DNS try to register the DNS names for this domain and could be the raise of your problem. Look at the NICs for your domain controllers to check it. You can uncheck option in the NIC that generte the problem to avoid DNS registering.

If DNS is forward and not your AD zone, then you can disable dynamic updates for the zone.

DrDave242

If the 169.254.x.x records are blank records (i.e., their names are listed as "same as parent folder"), then they're being registered by a domain controller. It is very likely you've got one or more DCs with NICs that are enabled and configured to obtain DHCP addresses but not plugged into anything. Disable those NICs, type "ipconfig /flushdns" and "ipconfig /registerdns" on the affected DC(s), then restart the Net Logon service on those DCs. This should remove the APIPA records. If not, you'll have to manually delete them, but they shouldn't come back.

TermEcho

ASKER

DrDave242:

That has resolved the dns address, but I am still having problems.

Server01.domain.org 172.16.2.2
Server02.domain.org 172.16.2.3 Are both Domain Controllers and DNS Servers.

In DNS I have am still getting multiple A records: (Same as parent folder) Host (A) 172.16.2.2
(Same as parent folder) Host (A) 172.16.2.3

But I also have a standard A record for each server: Server01.domain.org Host (A) 172.16.2.2
Server02.domain.org Host (A) 172.16.2.3

Any idea why I keep getting these A records for 2.2 and 2.3?
I need only one (same as parent folder) Host (A) xxx.xxx.xxx.xxx <--- IP of Website and
www Host (A) xxx.xxx.xxx.xxx <--- IP of Website

This way domain computers can type in www.example.org and still resolve our website. This was working until we switched our site to a new address that resolves all www.example.org request to example.org stripping the www.

Any ideas would be a big help.

Thanks!

ASKER CERTIFIED SOLUTION

DrDave242

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

TermEcho

ASKER

DrDave242:

I was able to find the DC's with the 169.* address we recently installed additional nic's for our SAN. :) I was able to get the web host to stop stripping the www and issues seemed to have been resolved. Thanks for the help!