Would like to see about getting DHCP configured on a Cisco switch to auto-register the computers hostname with a MS DNS server.Had to troubleshoot a workstation hogging bandwidth.
Choose "add/edit name servers." Enter the correct values for the Route 53 name servers, which you'll see when you click on the domain from the Hosted Zones page.
I've noticed that webmin isn't creating reverse PTR records when adding an A record to a DNS zone if another PTR with the same address already exists.
Dont have a router there, only a 3750 tied in via a fiber link.
I have been looking at the Cisco docs for getting this to work but nothing yet.
When a client shuts down, and later returns past the lease time, it may get a different IP address.
With the default settings, a duplicate A record gets registered by DHCP with the client’s new IP.
This is because DHCP doesn’t own the record, the client does, even though DHCP registered it. If you have Windows 2008 R2, in addition to configuring the DNS tab to force registration, you still must configure credentials and add the server to the Dns Update Proxy group.
The way to get around this is you can configure DHCP’s Option 081 to update the record for all client, no matter if the client asks or not. If DHCP is on a Windows 2008 R2 DC, to protect the DC when using the Dns Update Proxy group, you must secure the group by running: dnscmd /config /Open Acl On Proxy Updates 0 Using “DHCP Name Protection.” will register A and PTR record on behalf of a client, and will prevent a workstation (non-Windows) Name Squatting, meaning using a name that another machine (non-Windows or Windows) client that DHCP already registered , from registering it’s name.
Using Netflow, I could see the ip address of the offender but couldnt see the hostname of the computer/workstation that was the offender.