Re: Hostname resolution from client fails

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Clients get their IPs from a router with DHCP. The router also
distributes DNS information to clients. The only DNS server address
passed to clients is the IP of the Windows Server.

The server has two DNS forwarders set up that point to the ISP's DNS
servers. I'm guessing some part of the server's DNS configuration is
the problem, but don't know where else to look.

Here's a list of some of the DNS settings on the Windows server:

--- Forwarders --------
DNS Domain: [set to] "All other DNS domains"
Selected domain's forwarder IP address list:
xx.xx.xx.xx
xx.xx.xx.xx [ISP DNS servers]

--- Advanced ---------
[ ] Disable recursion
[x] BIND secondaries
[ ] Fail on load if bad zone data
[x] Enable round robin
[x] Enable netmask ordering
[x] Secure cache against pollution
Name checking: Multibye (UTF8)
Load zone data on startup: From Active Directory and registry
[ ] Enable automatic scavenging of stale records

Is there anything in Active Directory that I need to be concerned with?


daniel wrote:
How are your client machines obtaining an IP address? If you have a DHCP
server then you need to include your DNS server address in the scope. Of
course, you need to have DNS configured in your Windows 2003 server also.

"Chris Mueller" wrote:

I'm running Windows Server 2003 in a small office network (a dozen
clients). Executing ping on a client and the server return different
results, as follows:

ping -a 192.168.168.2

Server output:

"Pinging MYWORKSTATION [192.168.168.2] with 32 bytes of data: ...."

Client output:

"Pinging 192.168.168.2 with 32 bytes of data: ...."

The client *should* display the hostname (myworkstation) in the output
from the ping command, so I am fearing that there is a problem with the
DNS/hostname lookup.

I first noticed this problem when trying to install Symantec A/V
Corporate 10. My Symanetc System Console is unable to recognize client
computers, and I believe the issue described above is the problem.

Any suggestions would be greatly appreciated. Thank you.



.

Relevant Pages

  • Re: Cannot connect to RWW from home PC
    ... eth0 172.26.0.1/16 Extra none ... That would be the address you need a DNS record for. ... One question - if I reset the Thomson Router will that clear all the ... Heres' the info for our server: ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot connect to RWW from home PC
    ... No 10.0.0.138 is the address used to log onto Thomson's router to make the ... On the DNS question I can add an MX record in the DNS area of GoDaddy's ... eth0 172.26.0.1/16 Extra none ... Heres' the info for our server: ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... NIC, you need to specify an external DNS server for DNS, instead of the ... Both NICs should point to his internal IP for DNS. ... forward ports to it reliably in the router. ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot connect to RWW from home PC
    ... You say "And in the router you need to forward to your external nic IP" ... You say "You need the domain hoster to setup a DNS record that will be ... We have rerun CEICW sort of hoping it would sort out the router but no ... Heres' the info for our server: ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... The SBS DNS server, running on ... its IP it means that your problem is now DNS. ... forward ports to it reliably in the router. ... I should have been more clear about internet connection.. ...
    (microsoft.public.windows.server.sbs)