>From MS Technet:
The basic rules for DNS registration:
You must ONLY use the internal DNS servers on all machines. Any ISP's addresses
will cause it to fail
If any of the DCs are multihomed (multi NICs, multi IPs, and/or RRAS is
installed, will more than likely fail, as well as cause other significant
problems
For forward zone registration, the Primary DNS Suffix MUST match the zonename
in DNS
For reverse zone registration, it must be alo
For foward or reverse zone registration, the zones in question MUST be allowed
updates
If the zone updates are set to Secure Only, the machines MUST be joined to work
(because that uses Kerberos), otherwise, the DHCP server must be configured
with Credentials or the DHCP server object must be added to theDnsProxyUpdate
group
The AD DNS zone name cannot be a single label name ("DOMAIN" = bad,
"domain.com" = good)
GuidoElia
HELPPC-HELPPCSERVICE
________________________________________
Da: [email protected] [[email protected]] per conto
di Charles F Sullivan [[email protected]]
Inviato: venerdì 1 luglio 2016 19.46
A: [email protected]
Oggetto: RE: [NTSysADM] DHCP server not updating PTR records
Even if that is not what is causing the problem, the way I understand it
it's bad security to not designate an account here as you point out when
running DHCP on a DC.
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Sean Martin
Sent: Friday, July 1, 2016 11:15 AM
To: [email protected]
Subject: Re: [NTSysADM] DHCP server not updating PTR records
I seem to recall that the DHCP advanced properties need to be configured
with an account to register records in DNS, specifically when DHCP is
installed on a Domain Controller.
- Sean
> On Jun 30, 2016, at 6:51 PM, Richard Stovall <[email protected]> wrote:
>
> Some folks I'm working with have 2 DCs that are also DHCP servers. Each
server hands out part of the scope. Long story short, clients who receive
ips from DC1/DHCP1 have PTR records. Clients who receive ips from
DC2/DHCP2 do not. All clients are Win7. If, on a client that has an ip
received from server 2, you tick the box in advanced IPV4 properties to
"Use this connection's DNS suffix in DNS registration", then run ipconfig
/registerdns, a PTR record is created. No clients that have received ips
from server 1 have this option checked, but they all have PTR records.
>
> I've checked the settings on the DHCP servers and everything I can find
for DNS registration looks the same.
>
> Any thoughts? I'm betting it's pretty simple and we're just missing
something easy.
>
> FWIW, the DCs and the domain/forest are Server 2008.
>
> Thanks,
> RS
--
Questo messaggio e' stato analizzato con Libra ESVA ed e' risultato non infetto.
Seguire il link qui sotto per segnalarlo come spam:
http://mx01.enter.it/cgi-bin/learn-msg.cgi?id=509FE436AB.A76F3
