Networking Forums

Networking Forums > Computer Networking > Windows Networking > ignore FQDN 2003 DHCP server

Reply
Thread Tools Display Modes

ignore FQDN 2003 DHCP server

 
 
dirtymafia@gmail.com
Guest
Posts: n/a

 
      10-13-2006, 07:40 PM
Is there any way to ignore the client's response of their FQDN (DHCP
option 81)?
I know there is a way to do this in ISC's DHCP server (used in Linux as
dhcpd) with the option of "ignore client-updates;" in dhcpd.conf.

There really should be a way to do this in windows, since without AD
and without going around to each machine or doing a login script the
client's all report their FQDN as only hostname. and not
hostname.mydomain.org. I would think it would be quite easy to have
this feature in 2003 DHCP if it currently is not, which I'm hoping
someone here will be able to tell me that there is an option hidden
away somewhere.

 
Reply With Quote
 
 
 
 
Wade Barrett
Guest
Posts: n/a

 
      10-13-2006, 07:56 PM
Good Day,


Take a look at this Artical, i think this is what you want.


http://technet2.microsoft.com/Window....mspx?mfr=true

"(E-Mail Removed)" wrote:

> Is there any way to ignore the client's response of their FQDN (DHCP
> option 81)?
> I know there is a way to do this in ISC's DHCP server (used in Linux as
> dhcpd) with the option of "ignore client-updates;" in dhcpd.conf.
>
> There really should be a way to do this in windows, since without AD
> and without going around to each machine or doing a login script the
> client's all report their FQDN as only hostname. and not
> hostname.mydomain.org. I would think it would be quite easy to have
> this feature in 2003 DHCP if it currently is not, which I'm hoping
> someone here will be able to tell me that there is an option hidden
> away somewhere.
>
>

 
Reply With Quote
 
dirtymafia@gmail.com
Guest
Posts: n/a

 
      10-13-2006, 08:57 PM

Wade Barrett wrote:
> Good Day,
>
>
> Take a look at this Artical, i think this is what you want.


I've read through that article before, and did again. I have DDNS
setup just fine, as long as the client has "Use This connection's DNS
suffix in DNS registration" checked then it register's with DNS just
fine (in this case the client is sending the correct FQDN of
computername.domain.com in DHCP option 81).

DDNS also works correctly if I have both "Register this connection's
address in DNS" & "Use this connection's DNS suffix in DNS
registration" (in this case the client does not send it's FQDN in DHCP
option 81 because it is set not to register).

The default for Windows XP is "Register this connection's address in
DNS" checked and "Use this connection's DNS suffix in DNS registration"
unchecked. Which means that by default a Windows XP client will try to
register the FQDN of computername. instead of computername.domain.com.
Meaning that if there is a way for a 2003 DHCP server to ignore option
81(FQDN of client) and just register the client with DNS using option
12(client's hostname) and then appending the domain name.

 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Windows Server 2008 DHCP Reservations not visible from 2003 DHCP mmc Ckuderna Windows Networking 2 04-02-2009 01:47 PM
FQDN DHCP option (81) Venkat Windows Networking 1 11-02-2007 02:24 PM
Ignore DHCP requests from Cisco IP phones Surety Windows Networking 3 07-20-2006 01:01 AM
DHCP vendor option 43 XP clients do not ignore it Lumae Windows Networking 2 06-19-2005 09:20 PM
Redhat 9.0 dhcp client & windows 2003 dhcp server: dynamic dns update Mads Ravn Linux Networking 0 06-29-2004 05:27 PM



1 2 3 4 5 6 7 8 9 10 11