DNS & Domain Resolution

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

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" <(E-Mail Removed)> wrote in message
news:8D3669CD-48B6-47CA-8533-(E-Mail Removed)...
> 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

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" <(E-Mail Removed)> wrote in message
> news:8D3669CD-48B6-47CA-8533-(E-Mail Removed)...
> > 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
>
>
>

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" <(E-Mail Removed)> wrote in message
news:4AD029A7-1A3C-40FB-914E-(E-Mail Removed)...
> 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" <(E-Mail Removed)> wrote in message
>> news:8D3669CD-48B6-47CA-8533-(E-Mail Removed)...
>> > 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
>>
>>
>>

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" <(E-Mail Removed)> wrote in message
> news:4AD029A7-1A3C-40FB-914E-(E-Mail Removed)...
> > 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" <(E-Mail Removed)> wrote in message
> >> news:8D3669CD-48B6-47CA-8533-(E-Mail Removed)...
> >> > 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
> >>
> >>
> >>
>
>
>