Re: DNS & Domain Resolution

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

Okay... so heres my next question.
Should you be able to go \\microsoft and it hit up one of your domain
controllers? Or should it error and say it doesnt exist?

"Bill Grant" wrote:

That depends on what tool you use for lookup. nslookup will not find a
Netbios name unless the Netbios name is the same as the name+dns suffix.

"Nomad" <Nomad@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4AD029A7-1A3C-40FB-914E-EB9BC3D16328@xxxxxxxxxxxxxxxx
Hi Bill

But you should be able to resolve your own domain names NETBIOS name.
So using an example,

if your domain name was microsoft.com

internally you should be able to resolve microsoft (without the .com)

"Bill Grant" wrote:

That is what should happen. If you specify a single name without a
"dot"
in it, nslookup will add a domain suffix to the request, because it is
not a
valid name without one.

"Nomad" <Nomad@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8D3669CD-48B6-47CA-8533-1ECEE81B4C3F@xxxxxxxxxxxxxxxx
Hey

Have a domain lookup problem in regards to my DNS.
I can lookup all PC's / Servers / External Websites (DNS appears to be
working just fine), and I can lookup (and using this as an example of
my
domain name, incl Active Directory name) domainname.com but cannot
resolve
domainname on its own without the .com
It returns a server *** can't find domainname: Non-existant domain
Using WireShark you see the computer ask for domainname.domainname.com
and
the server rejects that and says it doesnt exist. But on a domain that
can
lookup itself you can see the cant find domainname.domainname.com BUT i
do
know domainname

It automatically adds the .domainname.com onto the end of it (eg
domainname.domainname.com) and rejects it, but its like something picks
it
up
and says but I do know who your talking about without the
.domainname.com
on
the end.

Anyone ran into this problem before? Thanks in advance :)






.

Relevant Pages

  • Re: DNS and NIS help
    ... + have from the servers. ... can resolve network addresses properly> ... + file the server can no longer resolve any web addresses. ... he'll still consult the nis hosts tables (for local IP lookup) ...
    (comp.sys.sun.admin)
  • Re: NetBIOS over IP -- XP to NT via VPN
    ... Although I can resolve to the computer name, I can see it's computer name. ... > Allow you to browse objects on the remote network - which LMHOSTS doesn't ... > NetBIOS names to IP addresses. ... there is a firewall, and I will try to disable it for my next wins test... ...
    (microsoft.public.windowsxp.security_admin)
  • Re: DNS query basics
    ... netBIOS disabled ... I suppose in my scenario DNS should be used to resolve names. ... if i ping xp by name with a trailing dot - it responds. ... it will use DirectSMB to resolve it. ...
    (microsoft.public.windows.server.dns)
  • Re: Massive Port 137 Access Denials
    ... Port 137 is used for the NetBios name service. ... register or lookup computer names on a Microsoft network. ... the computers within a network so that further access can be gained. ...
    (comp.security.firewalls)
  • Re: Name resolution vs. multiple NICs
    ... > configuration anyway.) ... If you can see them by the NetBIOS name ... > cares if it can resolve the name on the computer you run it on. ... > others around the network will have to resolve it. ...
    (microsoft.public.win32.programmer.networks)