PHWinfo banniere

Titres
PORTAIL ANNUAIRE ARTICLES COMPARATEUR HÉBERGEURS DEVIS FORUMS RÉDUCTEUR D'URL
Précédent   PHWinfo > Forums Hébergement > Forum Noms de domaine > ms.public.win.server.dns > Netbios Name Resolution Fast, FQDN Slow
S'inscrire FAQ Membres Recherche Messages du jour Marquer les forums comme lus
Netbios Name Resolution Fast, FQDN Slow

Réponse
 
LinkBack Outils de la discussion
Vieux 04/09/2006, 09h31   #1
Andrew Hayes
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Netbios Name Resolution Fast, FQDN Slow

If I ping SERVER then it resolves to an IP address and gets a response very
quickly. If I ping SERVER.DOMAIN then it takes about 25 seconds before it
responds.

I know that an FQDN normally goes directly to DNS, while a Netbios name will
go to WINS first, then DNS. I've tried switch the primary and secondary DNS
servers around but the response times are the same.

Using NSLOOKUP and typing in SERVER.DOMAIN gets a very quick response, so I
believe that DNS is working correctly. The forward-lookup-zone for DOMAIN is
also setup to use WINS.

Anyone have an idea of what might be the cause?


  Réponse avec citation
Vieux 04/09/2006, 13h53   #2
Herb Martin
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Re: Netbios Name Resolution Fast, FQDN Slow

"Andrew Hayes" <AndrewHayes@discussions.microsoft.com> wrote in message
news:%230igCz$zGHA.3908@TK2MSFTNGP05.phx.gbl...
> If I ping SERVER then it resolves to an IP address and gets a response
> very quickly. If I ping SERVER.DOMAIN then it takes about 25 seconds
> before it responds.
>
> I know that an FQDN normally goes directly to DNS, while a Netbios name
> will go to WINS first, then DNS. I've tried switch the primary and
> secondary DNS servers around but the response times are the same.


That is incorrect for programs, such as Ping, that are traditionally
IP based -- they use DNS resolution and ONLY use "NetBIOS"
as a supplement to their DNS methods (not checking for a NetBIOS
name directly but rather using NetBIOS as a fail over.)

Why would you EVER ping "server.domain" and not "Server.domain.com"
(or appropriate extension)?


> Using NSLOOKUP and typing in SERVER.DOMAIN gets a very quick response, so
> I believe that DNS is working correctly. The forward-lookup-zone for
> DOMAIN is also setup to use WINS.
>
> Anyone have an idea of what might be the cause?


Normally it is the other way around, since most people have their
DNS domain name for the computer set incorrectly in the SYSTEM
CONTROL Panel, and then try to overcome this by mucking around
with suffixes in the NIC IP DNS tab.

Check those two areas for correctness (mainly the System Control
Panel).

Post your "IPConfig /all" results (unedited, by sending to a file and
not using 'graphics'.)


--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]


  Réponse avec citation
Vieux 04/09/2006, 23h43   #3
Ace Fekay [MVP]
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Re: Netbios Name Resolution Fast, FQDN Slow

In news:%230igCz$zGHA.3908@TK2MSFTNGP05.phx.gbl,
Andrew Hayes <AndrewHayes@discussions.microsoft.com> stated, which I
commented on below:
> If I ping SERVER then it resolves to an IP address and gets a
> response very quickly. If I ping SERVER.DOMAIN then it takes about 25
> seconds before it responds.
>
> I know that an FQDN normally goes directly to DNS, while a Netbios
> name will go to WINS first, then DNS. I've tried switch the primary
> and secondary DNS servers around but the response times are the same.
>
> Using NSLOOKUP and typing in SERVER.DOMAIN gets a very quick
> response, so I believe that DNS is working correctly. The
> forward-lookup-zone for DOMAIN is also setup to use WINS.
>
> Anyone have an idea of what might be the cause?


Follow what Herb suggested.

I'm curious if you have a single label DNS domain name ("DOMAIN" instead of
the minimal requirement of 'domain.com', domain.local', domain.andrew',
etc). If this is true, that would indicate and cause slow lookups because
DNS will be querying each root hint before it looks at it's own configured
zone(s) because it thinks that "DOMAIN" is a TLD (top level domain such as
'com', 'net', 'org', etc).

Looking forward to reviewing your posted unedited ipconfig /all as Herb
requested.

--
Ace
Innovative IT Concepts, Inc
Willow Grove, PA

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Directory Services
Microsoft Certified Trainer

Having difficulty reading or finding responses to your post?
Instead of the website you're using, I suggest to use OEx (Outlook Express
or any other newsreader), and configure a news account, pointing to
news.microsoft.com. This is a direct link to the Microsoft Public
Newsgroups. It is FREE and requires NO ISP's Usenet account. OEx allows you
to easily find, track threads, cross-post, sort by date, poster's name,
watched threads or subject.
It's easy:

How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

Infinite Diversities in Infinite Combinations
Assimilation Imminent. Resistance is Futile
"Very funny Scotty. Now, beam down my clothes."

The only constant in life is change...


  Réponse avec citation
Réponse


Outils de la discussion

Règles de messages
Vous ne pouvez pas créer de nouvelles discussions
Vous ne pouvez pas envoyer des réponses
Vous ne pouvez pas envoyer des pièces jointes
Vous ne pouvez pas modifier vos messages

Les balises BB sont activées : oui
Les smileys sont activés : oui
La balise [IMG] est activée : oui
Le code HTML peut être employé : non
Trackbacks are oui
Pingbacks are oui
Refbacks are oui


Fuseau horaire GMT +1. Il est actuellement 03h33.


Édité par : vBulletin® version 3.7.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 3.2.0 RC5 Tous droits réservés.
Version française #16 par l'association vBulletin francophone
PHWinfo est un site Éducation Sans Frontières ©2000-2008
Ad Management by RedTyger
©Tous droits réservés par les parties respectives
Page generated in 0,10033 seconds with 11 queries