Re: 'A' record dynamic DNS registration failing depending on DHCP

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 and multiple
segments. I want to be able to use DNS for name resolution within the
network.
This is called, chache only servers, all you have to do to this work is 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 its
FQDN.
Create a PTR zone an allow updates. Do you have a forward zone?


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 the DNS
suffix to the hostname so I can use it for name resolution between the
network subnets.
I though that we were talking about Workgroup.

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 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.
read this:
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
.

Relevant Pages

  • RE: VPN Clients Not Registering in AD DNS
    ... via VPN, the DNS records of the VPN clients are unable to be registered. ... Windows 2003 server? ... please let me know whether the clients get the IP ...
    (microsoft.public.windows.server.sbs)
  • Re: Permissions across 2 Forrest
    ... Primary DNS server on 1.x and the 18.x network along with DHCP and WINS. ... For instance ForrestA DNS is now a secondary for Forrest B and vise versa. ... WINS clients must use the same "WINS Database"* ...
    (microsoft.public.windows.server.active_directory)
  • Re: Still strange not fully working DNS server
    ... On none of the computers (both DC and clients) no firewall software is ... For the rest nothing happens in the DNS forward lookup zone. ... Is the new server Global catalog? ... The config you mentioned was not configured so I have configured ...
    (microsoft.public.windows.server.dns)
  • Re: Client installation frustration.
    ... not, apparently, any DNS lookup issues on my network. ... connection's addresses in DNS" and "Use this connection's DNS suffix in DNS ... is a file and print server that we have at one of our secondary sites. ... Is there any way to cancel all current requests to install clients? ...
    (microsoft.public.sms.admin)
  • Re: problem with xp clients and windows 2003
    ... We now have the cross cable running from the room's switch ... >> policy but logs into the server. ... >> aware that this is a DNS issue but I have TRIPLE checked the DNS ... >> If I do NSlookup from the problematic clients, ...
    (microsoft.public.windows.server.networking)
Loading