|
|
|
#1 |
|
Messages: n/a
Hébergeur: |
Hope someone can I've been scratching my head for the past few hours. From domain abc.com I try and ping server1.xyz.com but when I look in the DNS debug log it is receiving the query as server1.xyz.com.abc.com and hence failing to resolve. To make things stranger this only happens some of the time, other times it is fine. If I use Nslookup it always resolves the name. Doing all this on a W2K DNS server on the abc.com domain which hosts zones for both domains. Cheers Joe |
|
|
|
#2 |
|
Messages: n/a
Hébergeur: |
"jwd" <jwd@discussions.microsoft.com> wrote in message news:84E7B188-03C7-441F-A3A5-EBBC1A995E67@microsoft.com... > > Hope someone can I've been scratching my head for the past few hours. > > From domain abc.com I try and ping server1.xyz.com but when I look in the > DNS debug log it is receiving the query as server1.xyz.com.abc.com and hence > failing to resolve. You didn't use an FQDN terminated by a DOT. Contrary to popular misconception, a DNS name is NOT "fully qualified" until you stick a "DOT" on the end. So if you ping: server1.xyz.com. <----dot on end .... it will work as you expected. > To make things stranger this only happens some of the time, other times it > is fine. If I use Nslookup it always resolves the name. NSLookup tries the name given first (before adding suffixes); at least if it looks qualified. > Doing all this on a W2K DNS server on the abc.com domain which hosts zones > for both domains. -- Herb Martin, MCSE MVP www.LearnQuick.Com |
|
|
|
#3 |
|
Messages: n/a
Hébergeur: |
Thanks, this occured to me just after I posted the message and it works fine now. Im aware that a FQDN must end in a dot to be truly fully qualified but I have never had to use this to set up a trust before (which is what I was trying to achieve). This doesnt explain why sometimes the domain was appended and other times it wasnt when the trailing dot was not used. Thanks again for your reply Joe "Herb Martin" wrote: > > "jwd" <jwd@discussions.microsoft.com> wrote in message > news:84E7B188-03C7-441F-A3A5-EBBC1A995E67@microsoft.com... > > > > Hope someone can I've been scratching my head for the past few hours. > > > > From domain abc.com I try and ping server1.xyz.com but when I look in the > > DNS debug log it is receiving the query as server1.xyz.com.abc.com and > hence > > failing to resolve. > > You didn't use an FQDN terminated by a DOT. > > Contrary to popular misconception, a DNS name is NOT "fully qualified" > until you stick a "DOT" on the end. > > So if you ping: server1.xyz.com. <----dot on end > > .... it will work as you expected. > > > To make things stranger this only happens some of the time, other times it > > is fine. If I use Nslookup it always resolves the name. > > NSLookup tries the name given first (before adding suffixes); at least > if it looks qualified. > > > Doing all this on a W2K DNS server on the abc.com domain which hosts zones > > for both domains. > > > -- > Herb Martin, MCSE MVP > www.LearnQuick.Com > > > |
|
|
|
#4 |
|
Messages: n/a
Hébergeur: |
Read inline,
In news:84E7B188-03C7-441F-A3A5-EBBC1A995E67@microsoft.com, jwd <jwd@discussions.microsoft.com> typed: > Hope someone can I've been scratching my head for the past few > hours. > > From domain abc.com I try and ping server1.xyz.com but when I look in > the DNS debug log it is receiving the query as > server1.xyz.com.abc.com and hence failing to resolve. This is not the reason it is failing to resolve, it just means the DNS Client is properly appending at least one suffix from the search list. Are there any other names in the DNS Suffix search list, besides abc.com? > > To make things stranger this only happens some of the time, other > times it is fine. If I use Nslookup it always resolves the name. What are the DNS servers listed in TCP/IP properties? > Doing all this on a W2K DNS server on the abc.com domain which hosts > zones for both domains. If the DNS server has both zones, and nslookup is always able to resolve the name, and it happens intermittently, I would think this falls back to a DNS Client configuration problem. Which is usually caused by an incorrect DNS IP in TCP/IP properties. -- Best regards, Kevin D. Goodknecht Sr. [MVP] Hope This s =================================== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue, to respond directly to me remove the nospam. from my email address. =================================== http://www.lonestaramerica.com/ http://support.wftx.us/ http://message.wftx.us/ =================================== Use Outlook Express?... Get OE_Quotefix: It will strip signature out and more http://home.in.tum.de/~jain/software/oe-quotefix/ =================================== Keep a back up of your OE settings and folders with OEBackup: http://www.oe.com/OEBackup/Default.aspx =================================== |
|
![]() |
| Outils de la discussion | |
|
|