In
Jason Davis said:
I tried all of that. I refreshed, re-created, restarted, still
nothing.
and btw I can't restart the netlogon service because I'm not in
domain :-(
Any workaround?
There isn't such a thing as a "workaround" for this, but rather the way your
clients are configured and the way the zone (if it exists) is configured.
Jason, to create a reverse PTR, create a reverse zone that matches your IP
subnet. Then rt-click on the zone, create a new PTR (pointer), then tell it
the IP address, then tell it the full FQDN. If not sure how to create a
reverse zone, here's a helpful link:
308201 - HOW TO Create a New Zone on a DNS Server in Windows 2000 [Forward
zones, CNAMES, Host Records, MX Records, Name Server Records and Reverse
Zones]:
http://support.microsoft.com/default.aspx?scid=kb;en-us;308201
So in your case, when creating a reverse zone for your subnet, 10.x.x.x,
rt-click reverse Lookup Zones, new zone, in the wizard, just type in 10,
then next next next finish. Then go into it's properties and set updates to
YES. That's pretty much it.
Normally if you are using and pointing to your DNS server, this is automatic
when using W2k or newer machines. Just make sure in your zone properties
that updates are allowed (set it to YES). You should also set your Forward
Lookup zone to Yes also.
Well, not sure if you already did, since you didn't state it, but make sure
your machines (including the DNS server) are only pointing to your own DNS
server in their IP properties. This way when it registers, it will register
to it. If any other machine is in your properties, it will try to register
elsewhere and you won't get proper registration.
If using DHCP, it will by default register the clients for it.
--
Regards,
Ace
Please direct all replies to the newsgroup so all can benefit.
Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory