General discussion

Locked

DNS Reverse Lookup

By stakhaus ·
I've been hunting down a DNS problem with Microsoft. When you create an
entry in the forward lookup zone and check the "create PTR record" box, it's
supposed to create an entry in the forward lookup zone and the reverse
lookup zone. For some hostnames, it works fine, for others it does not
create the reverse lookup entry. You have to check each time and create it
manually. Anyone ever heard of this? If the entry does not get created when you
think it had, a system that boots via FTP has a problem resolving the
hostname of a VxWorks client. This causes a delay for each file that FTP
tries to access. One system takes 5 minutes to boot vs. 2 minutes. Once I
created the reverse lookup pointer, everything worked as expected.

Win2K Server running.

This conversation is currently closed to new comments.

1 total post (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

corrupted component install

by Chris.. In reply to DNS Reverse Lookup

I'm sure MS has already had you do this, but you might think about removing the DNS component of the server, reboot, re-apply SP4, reload DNS, reboot, reapply SP4 and then hotfixes.

If that doesn't solve it, try adding the DNS component to another server and see how the replication works and try creating new entries there. Because DDNS isn't modeled like the older DNS there are no masters or secondaries and perhaps a newer DDNS config would replicated the DNS table and cure the corruption.

Worth a try I would think

Back to IT Employment Forum
1 total post (Page 1 of 1)  

Related Discussions

Related Forums