Taevalaotus
asked on
DNS is loosing A records, DHCP clients not registering correctly.
We are running win2000/2003 mixed domain in 2000 native mode.
Win2000 is GC server, runs primary DNS, DHCP and WINS server. Points to itself by real ip as primary DNS.
WIN2003 have DNS server, points to win2K as primary DNS and to itself as secondary DNS.
DNS servers are AD integrated, and zones are configured to allow dynamic updates.
Automatic aging/scavening is enabled for forward and reverse zones on both DNS servers.
Netdiag will pass all tests without issues.
DHCP server is configured to:
1. Automatically update DHCP client info in DNS
2. Always update DNS
3. Discard forward lookups when lease expires.
DHCP server provides valid router, DNS, Domain name, and gateway options for clients. Lease time is 1 hour.
Problems:
1. Sometimes dynamic DHCP clients do have several simultaneous (duplicate) IP addresses registered as PTR in reverse lookup zone (recreation of this zone did not help, have manually to clean zone, restart DNS and let machines renew registration.)
2. We are loosing records for static machines, not in dhcp pool segment (IE servers).
Host A records are deleted by DNS (scavening stalled records???) and not reregistered for some reason.
Additional information:
We have 2 separate C class networks, both divided as smaller sub-segments and connected transparently by router.
Servers have manual IP configuration, single network interface configurations, subnet xxx.xxx.249.0/26, DHCP clients have pool from subnet xxx.xxx.249.128/25. (there are more subnets on another xxx.xxx.248. network)
I can ping DNS servers from all our subnets and also nslookup works (as long as host records are on place)
Question: why do servers fail automatic registering on DNS?
Why DHCP clients get those duplicate records?
How to resolve issues?
Win2000 is GC server, runs primary DNS, DHCP and WINS server. Points to itself by real ip as primary DNS.
WIN2003 have DNS server, points to win2K as primary DNS and to itself as secondary DNS.
DNS servers are AD integrated, and zones are configured to allow dynamic updates.
Automatic aging/scavening is enabled for forward and reverse zones on both DNS servers.
Netdiag will pass all tests without issues.
DHCP server is configured to:
1. Automatically update DHCP client info in DNS
2. Always update DNS
3. Discard forward lookups when lease expires.
DHCP server provides valid router, DNS, Domain name, and gateway options for clients. Lease time is 1 hour.
Problems:
1. Sometimes dynamic DHCP clients do have several simultaneous (duplicate) IP addresses registered as PTR in reverse lookup zone (recreation of this zone did not help, have manually to clean zone, restart DNS and let machines renew registration.)
2. We are loosing records for static machines, not in dhcp pool segment (IE servers).
Host A records are deleted by DNS (scavening stalled records???) and not reregistered for some reason.
Additional information:
We have 2 separate C class networks, both divided as smaller sub-segments and connected transparently by router.
Servers have manual IP configuration, single network interface configurations, subnet xxx.xxx.249.0/26, DHCP clients have pool from subnet xxx.xxx.249.128/25. (there are more subnets on another xxx.xxx.248. network)
I can ping DNS servers from all our subnets and also nslookup works (as long as host records are on place)
Question: why do servers fail automatic registering on DNS?
Why DHCP clients get those duplicate records?
How to resolve issues?
Last Comment
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Thank you Chris+Dent for help, time and pointing good direction.
Final result possibly takes little thrill of aging timing, because about third of our clients are mobile users who just plug and go- several times a day. And some DHCP pools are 90% occupied. They go, this doesnt matter, but they find way back to office again, this is not so good for DNS.
That is reason for duplicate records in DNS and makes it complex to set proper scavening time for them.
Issue got me seek for understanding of those timings more properly, and i found this excellent article here also helpful, for learning purposes: http://searchwincomputing.techtarget.com/tip/0,289483,sid68_gci1040355,00.html
With regards:
Taevalaotus
Final result possibly takes little thrill of aging timing, because about third of our clients are mobile users who just plug and go- several times a day. And some DHCP pools are 90% occupied. They go, this doesnt matter, but they find way back to office again, this is not so good for DNS.
That is reason for duplicate records in DNS and makes it complex to set proper scavening time for them.
Issue got me seek for understanding of those timings more properly, and i found this excellent article here also helpful, for learning purposes: http://searchwincomputing.techtarget.com/tip/0,289483,sid68_gci1040355,00.html
With regards:
Taevalaotus
Windows Server 2003
Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).
129K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
ASKER
About aging:
[Quote="Chris-Dent"]
1. Aging is enabled on the reverse lookup zone? If so, what intervals?[/Quote]
You are right. here we go with inconsistencies:
On win2k DNS server itself- property: aging 1 hour, (did reset to default: 7 days)
Forward zone-site container properties: Aging was 1 hour ( changed to 1 day)
on reverse zones -property- non-refresh interval 1 hour, refresh interval 1 hour
DHCP timings are as such from previous administrator. I don't see any reason why lease time can't be longer, some 8 hours or 1 day for example.
I changed revers agings to 1 day, but what would be reasonable timings for those non-refresh and refresh intervals? Anything longer than/or equal to 24 hours? As much i understand, zone settings override server timings for finetune?
Should i consider DHCP lease timings when i apply DNS zone aging?
On win2003 DNS server: aging 1 day, (reset to default 7 days)
on zones settings inherited from master DNS.
About DHCP registering
As pointed in first post:
DHCP server is configured to:
1. Automatically update DHCP client info in DNS
I suggest that means: "registering is done via DHCP server, not client itself?" Am i correct?