Adding DHCP Scope Option 81

Hi,

I need to add DHCP scope option 81 (Client FQDN), as per
http://support.microsoft.com/default...b;en-us;816592 however it
doesn't currently show up under DHCP scope options, and when I try to add
it, I'm told that options 76 - 81 are reserved for standard options. How can
I specify a value for this option if it doesn't show up, or add it as an
option, if the code is reserved?

Ben

<using w2k3> Option 81 is defined by going to the dns properties tab of the
dhcp server and/or scope in the dhcp mmc.

"Ben" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi,
>
> I need to add DHCP scope option 81 (Client FQDN), as per
> http://support.microsoft.com/default...b;en-us;816592 however it
> doesn't currently show up under DHCP scope options, and when I try to add
> it, I'm told that options 76 - 81 are reserved for standard options. How
> can I specify a value for this option if it doesn't show up, or add it as
> an option, if the code is reserved?
>
> Ben
>

Hi Neo,

Thanks for the reply.

So it's one of the check/radio boxes, not actually defined as option 81 like
a scope option!
Hmm strange...as I have the following options checked, 'enable dns dynamic
updates - always dynamically update dns a & ptr', and 'dynamically update
dns a & ptr records for dhcp clients that do not request updates', but
looking at our dns zone, some records aren't updating. i.e. Yesterday laptop
A was 192.168.0.50, today laptop B is .50, however DNS hasn't updated. Also
I configured a reservation in DHCP yesterday for my laptop (internal nic mac
addy) as .60, today I've noticed that a VPN client has taken that IP. Surely
DHCP shouldn't issue a reserved IP? VPN is configured to use the internal
DHCP server, so all IPs comes from the same server/scope.

Ben




"neo [mvp outlook]" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> <using w2k3> Option 81 is defined by going to the dns properties tab of
> the dhcp server and/or scope in the dhcp mmc.
>
> "Ben" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Hi,
>>
>> I need to add DHCP scope option 81 (Client FQDN), as per
>> http://support.microsoft.com/default...b;en-us;816592 however it
>> doesn't currently show up under DHCP scope options, and when I try to add
>> it, I'm told that options 76 - 81 are reserved for standard options. How
>> can I specify a value for this option if it doesn't show up, or add it as
>> an option, if the code is reserved?
>>
>> Ben
>>
>
>

DHCP shouldn't be unless something else is a foot. For example since you
mention VPN, might want to check the VPN appliance configuration to ensure
that it isn't handing out from a static pool and is working in conjunction
with DHCP.

As for what is in DNS, might want to review the aging and savaging options
for the server/scope. If memory serves me right, MS sets up with a default
of 7 days and could influence what you see.

"Ben" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi Neo,
>
> Thanks for the reply.
>
> So it's one of the check/radio boxes, not actually defined as option 81
> like a scope option!
> Hmm strange...as I have the following options checked, 'enable dns dynamic
> updates - always dynamically update dns a & ptr', and 'dynamically update
> dns a & ptr records for dhcp clients that do not request updates', but
> looking at our dns zone, some records aren't updating. i.e. Yesterday
> laptop A was 192.168.0.50, today laptop B is .50, however DNS hasn't
> updated. Also I configured a reservation in DHCP yesterday for my laptop
> (internal nic mac addy) as .60, today I've noticed that a VPN client has
> taken that IP. Surely DHCP shouldn't issue a reserved IP? VPN is
> configured to use the internal DHCP server, so all IPs comes from the same
> server/scope.
>
> Ben
>
>
>
>
> "neo [mvp outlook]" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
>> <using w2k3> Option 81 is defined by going to the dns properties tab of
>> the dhcp server and/or scope in the dhcp mmc.
>>
>> "Ben" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> Hi,
>>>
>>> I need to add DHCP scope option 81 (Client FQDN), as per
>>> http://support.microsoft.com/default...b;en-us;816592 however
>>> it doesn't currently show up under DHCP scope options, and when I try to
>>> add it, I'm told that options 76 - 81 are reserved for standard options.
>>> How can I specify a value for this option if it doesn't show up, or add
>>> it as an option, if the code is reserved?
>>>
>>> Ben
>>>
>>
>>
>
>

Ben, did you every get to the bottom of this? my dhcp servers refuse point
blank to update dns regardless of the options ont eh dns tab. i too keep
comming across micrsooft docs suggesting using "option 81" which as you
rightly say, cannot be added. any help would be appreciated.
Shaun

"Ben" wrote:

> Hi Neo,
>
> Thanks for the reply.
>
> So it's one of the check/radio boxes, not actually defined as option 81 like
> a scope option!
> Hmm strange...as I have the following options checked, 'enable dns dynamic
> updates - always dynamically update dns a & ptr', and 'dynamically update
> dns a & ptr records for dhcp clients that do not request updates', but
> looking at our dns zone, some records aren't updating. i.e. Yesterday laptop
> A was 192.168.0.50, today laptop B is .50, however DNS hasn't updated. Also
> I configured a reservation in DHCP yesterday for my laptop (internal nic mac
> addy) as .60, today I've noticed that a VPN client has taken that IP. Surely
> DHCP shouldn't issue a reserved IP? VPN is configured to use the internal
> DHCP server, so all IPs comes from the same server/scope.
>
> Ben
>
>
>
>
> "neo [mvp outlook]" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
> > <using w2k3> Option 81 is defined by going to the dns properties tab of
> > the dhcp server and/or scope in the dhcp mmc.
> >
> > "Ben" <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed)...
> >> Hi,
> >>
> >> I need to add DHCP scope option 81 (Client FQDN), as per
> >> http://support.microsoft.com/default...b;en-us;816592 however it
> >> doesn't currently show up under DHCP scope options, and when I try to add
> >> it, I'm told that options 76 - 81 are reserved for standard options. How
> >> can I specify a value for this option if it doesn't show up, or add it as
> >> an option, if the code is reserved?
> >>
> >> Ben
> >>
> >
> >
>
>
>

Lets start with the basics.

1) Are your DNS zones configured to accept dynamic updates?

2) Are your servers/workstations tcpip properties set to the servers
identified in #1?

3) Are there any policies or configurations set to disable the workstations
ability to register the adapter in DNS?

4) For DHCP and assuming you are going with secure dynamic updates, did you
configure the DHCP server with a set of credentials so it could create the
necessary records in active directory?


"ShaunWills" <(E-Mail Removed)> wrote in message
news:0FF5F23B-18D6-4725-B77E-(E-Mail Removed)...
> Ben, did you every get to the bottom of this? my dhcp servers refuse point
> blank to update dns regardless of the options ont eh dns tab. i too keep
> comming across micrsooft docs suggesting using "option 81" which as you
> rightly say, cannot be added. any help would be appreciated.
> Shaun
>
> "Ben" wrote:
>
>> Hi Neo,
>>
>> Thanks for the reply.
>>
>> So it's one of the check/radio boxes, not actually defined as option 81
>> like
>> a scope option!
>> Hmm strange...as I have the following options checked, 'enable dns
>> dynamic
>> updates - always dynamically update dns a & ptr', and 'dynamically update
>> dns a & ptr records for dhcp clients that do not request updates', but
>> looking at our dns zone, some records aren't updating. i.e. Yesterday
>> laptop
>> A was 192.168.0.50, today laptop B is .50, however DNS hasn't updated.
>> Also
>> I configured a reservation in DHCP yesterday for my laptop (internal nic
>> mac
>> addy) as .60, today I've noticed that a VPN client has taken that IP.
>> Surely
>> DHCP shouldn't issue a reserved IP? VPN is configured to use the internal
>> DHCP server, so all IPs comes from the same server/scope.
>>
>> Ben
>>
>>
>>
>>
>> "neo [mvp outlook]" <(E-Mail Removed)> wrote in message
>> news:%(E-Mail Removed)...
>> > <using w2k3> Option 81 is defined by going to the dns properties tab of
>> > the dhcp server and/or scope in the dhcp mmc.
>> >
>> > "Ben" <(E-Mail Removed)> wrote in message
>> > news:(E-Mail Removed)...
>> >> Hi,
>> >>
>> >> I need to add DHCP scope option 81 (Client FQDN), as per
>> >> http://support.microsoft.com/default...b;en-us;816592 however
>> >> it
>> >> doesn't currently show up under DHCP scope options, and when I try to
>> >> add
>> >> it, I'm told that options 76 - 81 are reserved for standard options.
>> >> How
>> >> can I specify a value for this option if it doesn't show up, or add it
>> >> as
>> >> an option, if the code is reserved?
>> >>
>> >> Ben
>> >>
>> >
>> >
>>
>>
>>

Hi Neo,

Ok, lets see what I can tell you.

Its AD integrated DNS – secure updates, though Secure and Nonsecure has been
tried too. All DC’s are Server 2003 R2
Dhcp is on a Server 2003 R2 domain member server.

With default dhcp server settings, (ie Dynamically update DNS A and PTR
records only if client requests), the A record gets registered and the PTR
record does not. – the client of course registers the A record and the dhcp
server registers the ptr.

With the “Always update DNS A and PTR records� option selected, nothing get
registered. Here the dhcp server is trying to register both A & PTR

Allocating the ip address to the client statically both A & PTR get
registered.

So to resolve -
Dhcp servers have been added to DnsUpDateProxy group but it made no
difference.
Dns was changed to accept secure and non secure updates again no success.
I lowered the security on the reverse lookup zone to allow “Everyone� to
write to it, again no difference.
We have 4 dhcp servers in 4 different locations (different AD sites) and we
have the same problem at each location.

All clients are WindowsXP (various Service packs) a few Win2k and several
Server 2003. all clients with statically assigned ip addresses are able to
register A & PTR records. take a client of static and place on dhcp, the ptr
record disappears (even if it is the same address and suffix etc).

At one point I used my domain admin account as credentials for the dhcp
server to register my details with, but it made no difference.

I think that about covers this. any help would be appreciated.


"neo [mvp outlook]" wrote:

> Lets start with the basics.
>
> 1) Are your DNS zones configured to accept dynamic updates?
>
> 2) Are your servers/workstations tcpip properties set to the servers
> identified in #1?
>
> 3) Are there any policies or configurations set to disable the workstations
> ability to register the adapter in DNS?
>
> 4) For DHCP and assuming you are going with secure dynamic updates, did you
> configure the DHCP server with a set of credentials so it could create the
> necessary records in active directory?
>
>
> "ShaunWills" <(E-Mail Removed)> wrote in message
> news:0FF5F23B-18D6-4725-B77E-(E-Mail Removed)...
> > Ben, did you every get to the bottom of this? my dhcp servers refuse point
> > blank to update dns regardless of the options ont eh dns tab. i too keep
> > comming across micrsooft docs suggesting using "option 81" which as you
> > rightly say, cannot be added. any help would be appreciated.
> > Shaun
> >
> > "Ben" wrote:
> >
> >> Hi Neo,
> >>
> >> Thanks for the reply.
> >>
> >> So it's one of the check/radio boxes, not actually defined as option 81
> >> like
> >> a scope option!
> >> Hmm strange...as I have the following options checked, 'enable dns
> >> dynamic
> >> updates - always dynamically update dns a & ptr', and 'dynamically update
> >> dns a & ptr records for dhcp clients that do not request updates', but
> >> looking at our dns zone, some records aren't updating. i.e. Yesterday
> >> laptop
> >> A was 192.168.0.50, today laptop B is .50, however DNS hasn't updated.
> >> Also
> >> I configured a reservation in DHCP yesterday for my laptop (internal nic
> >> mac
> >> addy) as .60, today I've noticed that a VPN client has taken that IP.
> >> Surely
> >> DHCP shouldn't issue a reserved IP? VPN is configured to use the internal
> >> DHCP server, so all IPs comes from the same server/scope.
> >>
> >> Ben
> >>
> >>
> >>
> >>
> >> "neo [mvp outlook]" <(E-Mail Removed)> wrote in message
> >> news:%(E-Mail Removed)...
> >> > <using w2k3> Option 81 is defined by going to the dns properties tab of
> >> > the dhcp server and/or scope in the dhcp mmc.
> >> >
> >> > "Ben" <(E-Mail Removed)> wrote in message
> >> > news:(E-Mail Removed)...
> >> >> Hi,
> >> >>
> >> >> I need to add DHCP scope option 81 (Client FQDN), as per
> >> >> http://support.microsoft.com/default...b;en-us;816592 however
> >> >> it
> >> >> doesn't currently show up under DHCP scope options, and when I try to
> >> >> add
> >> >> it, I'm told that options 76 - 81 are reserved for standard options.
> >> >> How
> >> >> can I specify a value for this option if it doesn't show up, or add it
> >> >> as
> >> >> an option, if the code is reserved?
> >> >>
> >> >> Ben
> >> >>
> >> >
> >> >
> >>
> >>
> >>
>
>
>

Hi Neo,

Ok, lets see what I can tell you.

Its AD integrated DNS – secure updates, though Secure and Nonsecure has been
tried too. All DC’s are Server 2003 R2
Dhcp is on a Server 2003 R2 domain member server.

With default dhcp server settings, (ie Dynamically update DNS A and PTR
records only if client requests), the A record gets registered and the PTR
record does not. – the client of course registers the A record and the dhcp
server registers the ptr.

With the “Always update DNS A and PTR records� option selected, nothing get
registered. Here the dhcp server is trying to register both A & PTR

Allocating the ip address to the client statically both A & PTR get
registered.

So to resolve -
Dhcp servers have been added to DnsUpDateProxy group but it made no
difference.
Dns was changed to accept secure and non secure updates again no success.
I lowered the security on the reverse lookup zone to allow “Everyone� to
write to it, again no difference.
We have 4 dhcp servers in 4 different locations (different AD sites) and we
have the same problem at each location.

All clients are WindowsXP (various Service packs) a few Win2k and several
Server 2003. all clients with statically assigned ip addresses are able to
register A & PTR records. take a client of static and place on dhcp, the ptr
record disappears (even if it is the same address and suffix etc).

At one point I used my domain admin account as credentials for the dhcp
server to register my details with, but it made no difference.

I think that about covers this any help would be appreciated.


"neo [mvp outlook]" wrote:

> Lets start with the basics.
>
> 1) Are your DNS zones configured to accept dynamic updates?
>
> 2) Are your servers/workstations tcpip properties set to the servers
> identified in #1?
>
> 3) Are there any policies or configurations set to disable the workstations
> ability to register the adapter in DNS?
>
> 4) For DHCP and assuming you are going with secure dynamic updates, did you
> configure the DHCP server with a set of credentials so it could create the
> necessary records in active directory?
>
>
> "ShaunWills" <(E-Mail Removed)> wrote in message
> news:0FF5F23B-18D6-4725-B77E-(E-Mail Removed)...
> > Ben, did you every get to the bottom of this? my dhcp servers refuse point
> > blank to update dns regardless of the options ont eh dns tab. i too keep
> > comming across micrsooft docs suggesting using "option 81" which as you
> > rightly say, cannot be added. any help would be appreciated.
> > Shaun
> >
> > "Ben" wrote:
> >
> >> Hi Neo,
> >>
> >> Thanks for the reply.
> >>
> >> So it's one of the check/radio boxes, not actually defined as option 81
> >> like
> >> a scope option!
> >> Hmm strange...as I have the following options checked, 'enable dns
> >> dynamic
> >> updates - always dynamically update dns a & ptr', and 'dynamically update
> >> dns a & ptr records for dhcp clients that do not request updates', but
> >> looking at our dns zone, some records aren't updating. i.e. Yesterday
> >> laptop
> >> A was 192.168.0.50, today laptop B is .50, however DNS hasn't updated.
> >> Also
> >> I configured a reservation in DHCP yesterday for my laptop (internal nic
> >> mac
> >> addy) as .60, today I've noticed that a VPN client has taken that IP.
> >> Surely
> >> DHCP shouldn't issue a reserved IP? VPN is configured to use the internal
> >> DHCP server, so all IPs comes from the same server/scope.
> >>
> >> Ben
> >>
> >>
> >>
> >>
> >> "neo [mvp outlook]" <(E-Mail Removed)> wrote in message
> >> news:%(E-Mail Removed)...
> >> > <using w2k3> Option 81 is defined by going to the dns properties tab of
> >> > the dhcp server and/or scope in the dhcp mmc.
> >> >
> >> > "Ben" <(E-Mail Removed)> wrote in message
> >> > news:(E-Mail Removed)...
> >> >> Hi,
> >> >>
> >> >> I need to add DHCP scope option 81 (Client FQDN), as per
> >> >> http://support.microsoft.com/default...b;en-us;816592 however
> >> >> it
> >> >> doesn't currently show up under DHCP scope options, and when I try to
> >> >> add
> >> >> it, I'm told that options 76 - 81 are reserved for standard options.
> >> >> How
> >> >> can I specify a value for this option if it doesn't show up, or add it
> >> >> as
> >> >> an option, if the code is reserved?
> >> >>
> >> >> Ben
> >> >>
> >> >
> >> >
> >>
> >>
> >>
>
>
>

Based on the info given, here is my plan of attack.

1) Definitely stick with secure updates.

2) Switch back to dynamically update DNS A and PTR records only if client
request. Reason being, we know that the client is registering the A but
DHCP is failing on the PTR.

3) Instead of using a domain admin account for the DHCP credentials, I would
create a new user account for the DHCP credentials. This service account
only needs to be a member of Domain Users and DNSUpdateProxy. After you
plug this account into the configuration, I would recycle DHCP services.

4) I would also take a look at the latest DHCP audit log to see if anything
else turns up. (If audit logging is enabled, you will find the logs at
\WINDOWS\system32\dhcp.)

Outside of that, the only difference I can see between your and my
configuration is that I have DHCP services running on a DC rather than a
member server.

"ShaunWills" <(E-Mail Removed)> wrote in message
news:479C3BFB-92A8-43A4-BCA8-(E-Mail Removed)...
> Hi Neo,
>
> Ok, lets see what I can tell you.
>
> Its AD integrated DNS - secure updates, though Secure and Nonsecure has
> been
> tried too. All DC's are Server 2003 R2
> Dhcp is on a Server 2003 R2 domain member server.
>
> With default dhcp server settings, (ie Dynamically update DNS A and PTR
> records only if client requests), the A record gets registered and the PTR
> record does not. - the client of course registers the A record and the
> dhcp
> server registers the ptr.
>
> With the "Always update DNS A and PTR records" option selected, nothing
> get
> registered. Here the dhcp server is trying to register both A & PTR
>
> Allocating the ip address to the client statically both A & PTR get
> registered.
>
> So to resolve -
> Dhcp servers have been added to DnsUpDateProxy group but it made no
> difference.
> Dns was changed to accept secure and non secure updates again no success.
> I lowered the security on the reverse lookup zone to allow "Everyone" to
> write to it, again no difference.
> We have 4 dhcp servers in 4 different locations (different AD sites) and
> we
> have the same problem at each location.
>
> All clients are WindowsXP (various Service packs) a few Win2k and several
> Server 2003. all clients with statically assigned ip addresses are able to
> register A & PTR records. take a client of static and place on dhcp, the
> ptr
> record disappears (even if it is the same address and suffix etc).
>
> At one point I used my domain admin account as credentials for the dhcp
> server to register my details with, but it made no difference.
>
> I think that about covers this. any help would be appreciated.
>
>
> "neo [mvp outlook]" wrote:
>
>> Lets start with the basics.
>>
>> 1) Are your DNS zones configured to accept dynamic updates?
>>
>> 2) Are your servers/workstations tcpip properties set to the servers
>> identified in #1?
>>
>> 3) Are there any policies or configurations set to disable the
>> workstations
>> ability to register the adapter in DNS?
>>
>> 4) For DHCP and assuming you are going with secure dynamic updates, did
>> you
>> configure the DHCP server with a set of credentials so it could create
>> the
>> necessary records in active directory?
>>
>>
>> "ShaunWills" <(E-Mail Removed)> wrote in message
>> news:0FF5F23B-18D6-4725-B77E-(E-Mail Removed)...
>> > Ben, did you every get to the bottom of this? my dhcp servers refuse
>> > point
>> > blank to update dns regardless of the options ont eh dns tab. i too
>> > keep
>> > comming across micrsooft docs suggesting using "option 81" which as you
>> > rightly say, cannot be added. any help would be appreciated.
>> > Shaun
>> >
>> > "Ben" wrote:
>> >
>> >> Hi Neo,
>> >>
>> >> Thanks for the reply.
>> >>
>> >> So it's one of the check/radio boxes, not actually defined as option
>> >> 81
>> >> like
>> >> a scope option!
>> >> Hmm strange...as I have the following options checked, 'enable dns
>> >> dynamic
>> >> updates - always dynamically update dns a & ptr', and 'dynamically
>> >> update
>> >> dns a & ptr records for dhcp clients that do not request updates', but
>> >> looking at our dns zone, some records aren't updating. i.e. Yesterday
>> >> laptop
>> >> A was 192.168.0.50, today laptop B is .50, however DNS hasn't updated.
>> >> Also
>> >> I configured a reservation in DHCP yesterday for my laptop (internal
>> >> nic
>> >> mac
>> >> addy) as .60, today I've noticed that a VPN client has taken that IP.
>> >> Surely
>> >> DHCP shouldn't issue a reserved IP? VPN is configured to use the
>> >> internal
>> >> DHCP server, so all IPs comes from the same server/scope.
>> >>
>> >> Ben
>> >>
>> >>
>> >>
>> >>
>> >> "neo [mvp outlook]" <(E-Mail Removed)> wrote in message
>> >> news:%(E-Mail Removed)...
>> >> > <using w2k3> Option 81 is defined by going to the dns properties tab
>> >> > of
>> >> > the dhcp server and/or scope in the dhcp mmc.
>> >> >
>> >> > "Ben" <(E-Mail Removed)> wrote in message
>> >> > news:(E-Mail Removed)...
>> >> >> Hi,
>> >> >>
>> >> >> I need to add DHCP scope option 81 (Client FQDN), as per
>> >> >> http://support.microsoft.com/default...b;en-us;816592
>> >> >> however
>> >> >> it
>> >> >> doesn't currently show up under DHCP scope options, and when I try
>> >> >> to
>> >> >> add
>> >> >> it, I'm told that options 76 - 81 are reserved for standard
>> >> >> options.
>> >> >> How
>> >> >> can I specify a value for this option if it doesn't show up, or add
>> >> >> it
>> >> >> as
>> >> >> an option, if the code is reserved?
>> >> >>
>> >> >> Ben
>> >> >>
>> >> >
>> >> >
>> >>
>> >>
>> >>
>>
>>
>>