- Sep 19, 2000
- 1,003
- 0
- 0
I'm nearly pulling my hair out over this one.
I've been trying to get DNS 100% stable because a bunch of test servers on the domain that the internet guys were using were doing dynamic updates and kept adding IPs to the tables that were screwing things up.
I think I've got that taken care of by adding the DisableDynamicUpdate Registry Key to 1 on these systems, and also by stopping and disabling the DHCP client (they were using statics anyway).
I still have this one nagging issue that's driving me crazy though, whenever I do a direct nslookup query against one of the servers for just the domain (i.e. domain.com vs. server.domain.com) it's coming up with more IP addresses then are showing up in the MMC. To further make a mess, a couple of servers are doing this, but they aren't coming up with the same results (and every other record sync's flawlessly between them).
Here's the really really weird part... The numbers that are getting added are part of the range on the PIX, but one is permanently mapped to a corresponding IP on the DMZ, one is part of the NAT range, and one is unused (and the other server doing this is only showing 2 of these, not three).
Anyone have any idea about where this is coming from? Or, more importantly, how to kill those records when they don't show up in the management console?
I've been trying to get DNS 100% stable because a bunch of test servers on the domain that the internet guys were using were doing dynamic updates and kept adding IPs to the tables that were screwing things up.
I think I've got that taken care of by adding the DisableDynamicUpdate Registry Key to 1 on these systems, and also by stopping and disabling the DHCP client (they were using statics anyway).
I still have this one nagging issue that's driving me crazy though, whenever I do a direct nslookup query against one of the servers for just the domain (i.e. domain.com vs. server.domain.com) it's coming up with more IP addresses then are showing up in the MMC. To further make a mess, a couple of servers are doing this, but they aren't coming up with the same results (and every other record sync's flawlessly between them).
Here's the really really weird part... The numbers that are getting added are part of the range on the PIX, but one is permanently mapped to a corresponding IP on the DMZ, one is part of the NAT range, and one is unused (and the other server doing this is only showing 2 of these, not three).
Anyone have any idea about where this is coming from? Or, more importantly, how to kill those records when they don't show up in the management console?