Werbung: SecurityConsole.de verwaltet Ihre Computer mit Security Essentails aus der Cloud!
30 Tage kostenfrei testen und 20% Rabatt für Ihre Bestellung mit Promocode: WBF2685582
(Promocode gültig bis 31.12.2011)

Group:  English: Windows Server » microsoft.public.windows.server.dns
Thread: Clients not resolving dns names

HTVi
TV Discussion Newsgroups

Clients not resolving dns names
Marcus Dempsey 4/24/2007 4:28:00 PM
Hi,

We are running a Windows 20003 AD domain (latest sevrice pack), and have an
issue where all our cients are unable to resolve certain external dns names -
ftp.microsoft.com for instance. However our domain controllers can resolve
these without issue.

Here is what I got from one of the client machines:

[Quoted Text]
> ftp.microsoft.com
Server: hof-dom-001.scs
Address: 10.250.0.1

------------
Got answer:
HEADER:
opcode = QUERY, id = 2, rcode = NXDOMAIN
header flags: response, auth. answer, want recursion
questions = 1, answers = 0, authority records = 1, additional = 0

QUESTIONS:
ftp.microsoft.com.SCS, type = A, class = IN
AUTHORITY RECORDS:
-> scs
ttl = 3600 (1 hour)
primary name server = hof-dom-001.scs
responsible mail addr = hostmaster.scs
serial = 30810
refresh = 900 (15 mins)
retry = 600 (10 mins)
expire = 86400 (1 day)
default TTL = 3600 (1 hour)

------------
------------
Got answer:
HEADER:
opcode = QUERY, id = 3, rcode = SERVFAIL
header flags: response, want recursion
questions = 1, answers = 0, authority records = 0, additional = 0

QUESTIONS:
ftp.microsoft.com, type = A, class = IN

------------
*** hof-dom-001.scs can't find ftp.microsoft.com: Server failed
>

Can anyone shed any light on this? do I need to enable forwarders on the
DNS servers?

Marcus
Re: Clients not resolving dns names
Myweb <meiweb[ at ]gmx.de> 4/24/2007 7:21:16 PM
Hello Marcus,

Please post an ipconfig /all from your DNS server and one workstation. By
default the workstation should only look to the internal DNS of your domain
and the DNS server should have enabled Forwarders to your ISP's DNS.

Best regards

Myweb
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

[Quoted Text]
> Hi,
>
> We are running a Windows 20003 AD domain (latest sevrice pack), and
> have an issue where all our cients are unable to resolve certain
> external dns names - ftp.microsoft.com for instance. However our
> domain controllers can resolve these without issue.
>
> Here is what I got from one of the client machines:
>
>> ftp.microsoft.com
>>
> Server: hof-dom-001.scs
> Address: 10.250.0.1
> ------------
> Got answer:
> HEADER:
> opcode = QUERY, id = 2, rcode = NXDOMAIN
> header flags: response, auth. answer, want recursion
> questions = 1, answers = 0, authority records = 1,
> additional = 0
> QUESTIONS:
> ftp.microsoft.com.SCS, type = A, class = IN
> AUTHORITY RECORDS:
> -> scs
> ttl = 3600 (1 hour)
> primary name server = hof-dom-001.scs
> responsible mail addr = hostmaster.scs
> serial = 30810
> refresh = 900 (15 mins)
> retry = 600 (10 mins)
> expire = 86400 (1 day)
> default TTL = 3600 (1 hour)
> ------------
> ------------
> Got answer:
> HEADER:
> opcode = QUERY, id = 3, rcode = SERVFAIL
> header flags: response, want recursion
> questions = 1, answers = 0, authority records = 0,
> additional = 0
> QUESTIONS:
> ftp.microsoft.com, type = A, class = IN
> ------------
> *** hof-dom-001.scs can't find ftp.microsoft.com: Server failed
> Can anyone shed any light on this? do I need to enable forwarders on
> the DNS servers?
>
> Marcus
>

Home | Search | Terms | Imprint Contact
Newsgroups Reader - provided by WiredBox.Net
Suche nach Orten, Städten, Postleitzahlen, Vorwahlen, Kfz-Kennzeichen