Duplicate DNS Records

  • Thread starter Thread starter Brandon Riffel
  • Start date Start date
B

Brandon Riffel

We've been having some problems with DNS. Some of the issues may be
solved with Scavenging and Aging, but that only fixes part of our
problems.

Here is an example that wouldn't be fixed with scavenging:

We use VLANs on our network and when a tech sets up a new pc in the
work room on VLAN 1, then delivers the machine to an office in VLAN
12, it gets a new IP address in that VLAN. This causes 2 DNS entries
and thus causes a problem with an application we use.

Here is part of our DNS Forward and Reverse lookups (I've changes
names to protect the innocent):

FORWARD_________________________________

Name Type Data

name4 Host (A) 10.1.7.1
name5 Host (A) 10.1.7.2
ksotbrandon2 Host (A) 10.1.7.3
ksotapp01 Host (A) 10.1.7.4
ADMINISTRATOR2 Host (A) 10.1.7.5
johndoe Host (A) 10.1.7.7
janedoe Host (A) 10.1.7.11
madsenn Host (A) 10.1.7.11
aljen Host (A) 10.1.7.12
name2 Host (A) 10.1.7.12
desktopsupport Host (A) 10.1.7.15
rndibm Host (A) 10.1.7.15
arbt Host (A) 10.1.7.16
coleles Host (A) 10.1.7.17
dierkerm Host (A) 10.1.7.17
jane2 Host (A) 10.1.7.17
ou-yia6ffpnmy3q Host (A) 10.1.7.19
ksotsms01 Host (A) 10.1.7.20
black Host (A) 10.1.7.22
image2 Host (A) 10.1.7.23
newlaptop Host (A) 10.1.7.23
mordor Host (A) 10.1.7.24
brent Host (A) 10.1.7.25
krebsc2 Host (A) 10.1.7.27
watchdog Host (A) 10.1.7.30
name1 Host (A) 10.1.7.32
infotech_rnd Host (A) 10.1.7.37
ottawa-hrz9nggw Host (A) 10.1.7.39
rnd_snap Host (A) 10.1.7.211

REVERSE___________________________________

Name Type Data
10.1.7.1 Pointer (PTR) name3.
10.1.7.1 Pointer (PTR) mediacenter.
10.1.7.2 Pointer (PTR) ttwokk.
10.1.7.2 Pointer (PTR) ttwokk.domain.edu.
10.1.7.3 Pointer (PTR) ksotbrandon2.domain.edu.
10.1.7.4 Pointer (PTR) ksotapp01.domain.edu.
10.1.7.5 Pointer (PTR) ksotsms01.domain.edu.
10.1.7.5 Pointer (PTR) name2.domain.edu.
10.1.7.6 Pointer (PTR) jane2.
10.1.7.7 Pointer (PTR) johndoe.domain.edu.
10.1.7.8 Pointer (PTR) reborn.
10.1.7.8 Pointer (PTR) shire.
10.1.7.8 Pointer (PTR) win32.
10.1.7.11 Pointer (PTR) janedoe.domain.edu.
10.1.7.12 Pointer (PTR) ngohs.domain.edu.
10.1.7.14 Pointer (PTR) pineapple.
10.1.7.16 Pointer (PTR) arbt.domain.edu.
10.1.7.17 Pointer (PTR) jane2.domain.edu.
10.1.7.18 Pointer (PTR) brandonpc.
10.1.7.23 Pointer (PTR) itstudent.
10.1.7.25 Pointer (PTR) brent.
10.1.7.25 Pointer (PTR) suseserver.
10.1.7.32 Pointer (PTR) name1.domain.edu.
10.1.7.35 Pointer (PTR) ahshucks.
10.1.7.36 Pointer (PTR) domainun.domain.edu.
 
Brandon,,

try to run a ipconfig /release before powering off the system, if you find
that this works you could add it to a AD logoff script to ensure that all
addresses are releases once systems are powered off..

Jay
 
Scavenging works hand-in-hand with your lease duration. Try re-alligning
your lease duration such that it conforms to your scavenging period. Then
let DHCP recycle and clean up the stale leases for you.

--


Sincerely,

Dèjì Akómöláfé, MCSE+M MCSA+M MCP+I
Microsoft MVP - Directory Services
www.readymaids.com - we know IT
www.akomolafe.com
Do you now realize that Today is the Tomorrow you were worried about
Yesterday? -anon
 
Back
Top