• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1181
  • Last Modified:

Registerdns with 169.254 IP

I am installing 2 new Windows 2008 servers into an existing 2003 domain. 1 will be a DC and the other for Exchange 2007.

The client currently uses 169.254.228.0/24 as there internal network range and this is distributed by the 2003 server via DHCP.

After installing the ADS roles for 2008 and promoted it to a DC, GC, running DNS, i noticed that there was no A record for this new server in the AD integrated DNS zone for this domain. I manually added an A record for this server and AD was working ok.

After a little amount of time, AD\DNS stopped working and the A record for the 2008 server was gone.

After pulling my hair out for hours, I removed the DNS zone and recreated on the 2003 server. I restarted the netlogon service and ipconfig /registerdns on both DC's servers but still the 2008 servers IP does not get registered.

Before the 2008 installation, clients were registering their IPs to DNS ok, I have not tested if they still do now since I have recreated the zone remotely.

Any ideas? Could it be coded in not to register APIPA ranged IPs?
0
adm-computing
Asked:
adm-computing
  • 5
  • 4
  • 2
3 Solutions
 
minas69yanCommented:
Hello,

The range of 169.254.0.0/16 is an address range given to computer when it is unable to get address from DHCP or looses connectivity.
So something is going wrong with client's subnet-domain. Those addresses are not routable. So before digging any further just check DHCP server on clien's side(probably it's down).

Domain controllers should be set up with static addresses, (i.e 192.168.111.1 or 10.10.10.1).
Sorry if I getting off the question ( your clients address range did that to me :))

Raz
0
 
Chris DentPowerShell DeveloperCommented:

> Could it be coded in not to register APIPA ranged IPs?

I know that it definitely isn't coded in that manner.

You don't happen to have a single label domain name do you? e.g. "YourDomain", instead of "YourDomain.com".

I seriously recommend you move away from the 169.254 range, it's a bit daft to be handing out the auto-configuration range in DHCP.

Chris
0
 
adm-computingAuthor Commented:
@Chris

Thanks for your reply. domain.local is what we use here but there was a single label domain registered in DNS but I have removed that (there was no records other then NS and SOA records in that zone)

It's just odd that its been working fine under a 2003 DC for a few years and now with 2008 it's not working.

I think I will run some tests on a IP change to see if that cures the problem and DNS registration is working.

@Raz, I know ;)
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
Chris DentPowerShell DeveloperCommented:

You you already checked the event logs on the hosts for DNSAPI errors?

Chris
0
 
adm-computingAuthor Commented:
Thats the odd thing, I don't see any DNS events in any of the logs - which one would you expect them appear in?
I do get lots of Group Policy and Directory Services errors but this is due to them unable to resolved the new DCs.
0
 
Chris DentPowerShell DeveloperCommented:

Either System or Application, I'm afraid I forget exactly which. I'd be tempted to throw Wireshark (never could get along with Network Monitor) onto the server and see if it's even attempting to send the update request.

Chris
0
 
adm-computingAuthor Commented:
I changed the LANs IP range to 192.168.100.0/23 and now DNS is being updated as it should.
But my Windows 2008 DCs are not very happy even after a demote and promote. Looks like I'll need a clean install for 2008.
0
 
Chris DentPowerShell DeveloperCommented:

You shouldn't need to. What are the doing to make them unhappy?

Chris
0
 
adm-computingAuthor Commented:
There are just soo many errors in the event logs relating to being unable to resolve its own name in DNS although nslookup does return ok.

The netlogon and sysvol shares are visable on the 2008 server but ADUC doesnt open. Comes up with an error about the schema and not being able to resolve its own name.
0
 
minas69yanCommented:
Glad to hear that something moved :)
1)
now about demotion and promotion:

Once the repairing of Domain Controller took from me about 1 and half day to get rid of all the errors. I was still getting some replication issues of DNS records.
Clean reinstallation of the same DC  took about 3 hours with all user accounts. So decision is yours :)

So keeping in mind that it is the Microsoft product we are dealing with (not Linux fileserver rebooted last time 2 years ago) then periodically clean installation is very healthy for your AD :)

2)
Did you intentionally used subnet /23 and not the /24? If yes then be careful with netmasks.
255.255.254.0 instead of 255.255.255.0

Raz
0
 
adm-computingAuthor Commented:
Points split to those that replied to this. I had to reinstall the servers and started from scratch. I found that most of the problems stemed from having hyper-v and IPv6 on a HP ML350 G5 server with the built in HP teamed network card drivers installed. Nice one HP!
0

Featured Post

Vote for the Most Valuable Expert

It’s time to recognize experts that go above and beyond with helpful solutions and engagement on site. Choose from the top experts in the Hall of Fame or on the right rail of your favorite topic page. Look for the blue “Nominate” button on their profile to vote.

  • 5
  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now