Re: 'A' record dynamic DNS registration failing depending on DHCP serv
- From: "Jorge Silva" <jorgesilva_pt@xxxxxxxxxxx>
- Date: Wed, 23 Aug 2006 12:37:11 +0100
Hi
Inline
I am running a Windows Server 2003 workgroup with many clients and multipleThis is called, chache only servers, all you have to do to this work is to
segments. I want to be able to use DNS for name resolution within the
network.
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.
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.
I want to be able for the DHCP server set the DNS server to append the DNSI though that we were talking about Workgroup.
suffix to the hostname so I can use it for name resolution between the
network subnets.
Are we talking about Workgroup or Domain Environment?
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
"mtnit" <mtnit@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:216F34C2-17C3-4C7C-9004-B6CDB3B69298@xxxxxxxxxxxxxxxx
I am running a Windows Server 2003 workgroup with many clients and multiple
segments. I want to be able to use DNS for name resolution within the
network.
I am running Windows DNS server and am unable to have a client register
its
A record with the DNS server automatically when using the Windows DHCP
server.
The client will register its pointer (PTR) but not its A record or its
FQDN.
I want to be able for the DHCP server set the DNS server to append the DNS
suffix to the hostname so I can use it for name resolution between the
network subnets.
I have gone through the documentation of 'Option 81' and set the DHCP
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.
Obviously this has something to do with the dynamic update relationship
between Windows DHCP and DNS but I can't work out the option to fix it. I
don't want a solution that involves me changing a setting on every single
workstation.
Appreciate any help!
.
- Follow-Ups:
- Prev by Date: Re: Can DNS response be different according to client's AD site?
- Next by Date: Re: Remote sites and DNS
- Previous by thread: Standard DNS notifies.
- Next by thread: Re: 'A' record dynamic DNS registration failing depending on DHCP
- Index(es):
Relevant Pages
|
