Re: 'A' record dynamic DNS registration failing depending on DHCP
- From: "Jorge Silva" <jorgesilva_pt@xxxxxxxxxxx>
- Date: Wed, 23 Aug 2006 16:29:28 +0100
Inline
DNS has been setup with default settings and is resolving names correctlyOk, so I can assume that your server is using the default root hints.
for clients.
Yes forward and reverse lookup zones have been created. However the
clients
are only being registered in the Reverse Lookup Zone. They are not
registering themselves in the Forward Lookup Zone. Also they only register
themselves in the Reverse Lookup Zone as: 'hostname.', whereas clients
that
recieved their IP from another DHCP server register their name under the
'Data' column as: 'hostname.domain.local'.
Did you enabled the option:Always update DNS
Did you configured the dns suffix on dhcp
If you define staticTCP/ IP with the preferred dns server pointing to the
correct dns server, and run from cmd ipconfig /registerdns, the record
shows?
The clients that are having problems do they already had a A record on DNS
register by the other DHCP, if you delete that record and try again what
happens?
Are these windows xp clients or do you have NT4, W98,etc?
Read:
Troubleshooting dynamic updates
http://technet2.microsoft.com/WindowsServer/en/library/1583e419-88a6-4062-8807-d9eea99e3b421033.mspx?mfr=true
DHCP Dynamic DNS Registration for Windows 2000 Clients Does Not Work
http://support.microsoft.com/default.aspx?scid=kb;en-us;314822
A DHCP Client May Send an Incorrect FQDN in a DHCP-Request Packet
http://support.microsoft.com/?kbid=317288
Dynamic Host Configuration Protocol for Windows Server 2003
http://download.microsoft.com/download/1/6/a/16a11c96-daa4-44a6-98ae-9f9ddb203b46/DHCP2003.doc
--
I hope that the information above helps you
Good Luck
Jorge Silva
MCSA
Systems Administrator
"mtnit" <mtnit@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E3F13C00-6A3B-48DB-B8E6-79C880528D6E@xxxxxxxxxxxxxxxx
Hi Jorge,
Thanks for your response. I followed your suggestions and the clients are
now showing up in the Forward Lookup Zone however they are still not
having a
FQDN suffix attached. Please see some of my responses below.
Thanks,
-Kyle
"Jorge Silva" wrote:
Hi
Inline
I am running a Windows Server 2003 workgroup with many clients andThis is called, chache only servers, all you have to do to this work is
multiple
segments. I want to be able to use DNS for name resolution within the
network.
to
install DNS service on that server, point the server to itself, and point
the clients to the server. If you want you can increase security by
configuring the server to forward the requests to your ISP and/or Router
and
enableing the option don't use recursion for this domain.
DNS has been setup with default settings and is resolving names correctly
for clients.
The client will register its pointer (PTR) but not its A record or itsCreate a PTR zone an allow updates. Do you have a forward zone?
FQDN.
Yes forward and reverse lookup zones have been created. However the
clients
are only being registered in the Reverse Lookup Zone. They are not
registering themselves in the Forward Lookup Zone. Also they only register
themselves in the Reverse Lookup Zone as: 'hostname.', whereas clients
that
recieved their IP from another DHCP server register their name under the
'Data' column as: 'hostname.domain.local'.
I want to be able for the DHCP server set the DNS server to append theI though that we were talking about Workgroup.
DNS
suffix to the hostname so I can use it for name resolution between the
network subnets.
Are we talking about Workgroup or Domain Environment?
Its a workgroup and their is no DC or AD. I would still like DNS to append
a
DNS suffix to make a FQDN for the purpose of name resolution within the
network.
I have gone through the documentation of 'Option 81' and set the DHCPread this:
server
to have DNS A and PRT records always dynamically updated. I am able to
get
the client to register correctly if I check the clients 'Use this
connection's DNS suffix in DNS registration' in its network connection
options. What's even more strange is that if I use the DHCP server in
another
hardware device (Adtran router) the DNS suffix is appended and the FQDN
is
correct. As soon as I try to use the Windows DHCP server this no longer
works.
Using DNS servers with DHCP
http://technet2.microsoft.com/WindowsServer/en/Library/179d4f6c-9482-4dac-8f03-74bd78b7d2631033.mspx
--
I hope that the information above helps you
Good Luck
Jorge Silva
MCSA
Systems Administrator
.
- References:
- Prev by Date: Windows 2003 server, append DNS search suffix? Max entries.
- Next by Date: Re: Windows 2003 server, append DNS search suffix? Max entries.
- Previous by thread: Re: 'A' record dynamic DNS registration failing depending on DHCP
- Next by thread: Re: 'A' record dynamic DNS registration failing depending on DHCP
- Index(es):
Relevant Pages
|
