Re: DNS not authoritative for domain
- From: "Brian" <Brian@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 4 Oct 2005 17:23:03 -0700
Once again, I'm sorry for not being able to reply a lot sooner to your
request for information.
In answer to your questions:
I am using an internal DHCP server (the dc) which is also my DNS and WINS
server. I had to include options 044 and 046 (they weren't checked when I
looked via Add/Remove Programs).
I have configured a PPTP VPN using ISA to test whether or not I had an issue
with my SonicWALL and it is still a bit erratic. The first time I connected
everything worked, but hasn't on subsequent connections.
I think this problem will be solved when I figure out what is wrong with my
DNS which I have to say thanks to you as well for your help.
Thank you,
Brian.
"Ace Fekay [MVP]" wrote:
> In news:30E97860-0272-4860-AFA6-8CD94ED97A58@xxxxxxxxxxxxx,
> Brian <Brian@xxxxxxxxxxxxxxxxxxxxxxxxx> made this post, which I then
> commented about below:
> > Hello,
> >
> > I can't understand what has went wrong with our DNS; I hope someone
> > can help point me in the right direction.
> >
> > I have a SonicWALL and a Windows 2000 domain.
> >
> > I can correctly resolve short and FQDN inside my domain. When I'm
> > logged in via VPN, or directly to the SonicWALL, I am unable to
> > resolve short names. I can resolve FQDN and reverse lookups. The
> > returned error is the server is not authoritative for the domain.
> >
> > I don't have more than one DNS server, and I rebuilt DNS last night
> > and no one has complained today (I'm sure I would have heard about it
> > if there were problems). I wasn't asked if this was the first DNS
> > server for the domain when I rebuilt it last night, so I'm not sure
> > if I need to delete any left over configuration files or what, but I
> > can't find any way that I can make the domain authoritative.
> >
> > Thanks for any help,
> >
> > Brian.
>
> Are you using WINS? "Short" names, as you put it, or actually NetBIOS names,
> do not traverse a router (VPNs can be looked at as a 'routed' connection).
> For VPN connections and for multi-subnetted environments, we need to have a
> NetBIOS name resolution solution, such as WINS.
>
> What DHCP service are you using for your VPN clients? If using the internal
> Windows DHCP server, and you are using WINS, and DHCP is configured with
> Options 044 and 046, that should support it.
>
> Keep in mind, the search suffix on the client plays a big role in NetBIOS
> name resolution, since the name is devolved by the resolver service using
> the search suffixes until it can find a name, if it doesn't, then it looks
> at NetBIOS. If WINS is involved, it will ask WINS at this point if the
> previous methods didn't resolve it.
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> If this post is viewed at a non-Microsoft community website, and you were to
> respond to it through that community's website, I may not see your reply
> unless that website posts replies back to the original Microsoft forum.
> Therefore, please direct all replies ONLY to the Microsoft public newsgroup
> this thread originated in so all can benefit or ensure the web community
> posts it back to the original forum.
>
> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
> Microsoft Windows MVP - Windows Server - Directory Services
> Microsot Certified Trainer
> Infinite Diversities in Infinite Combinations.
> =================================
>
>
>
.
- Follow-Ups:
- Re: DNS not authoritative for domain
- From: Ace Fekay [MVP]
- Re: DNS not authoritative for domain
- Prev by Date: Re: A challenge >>
- Next by Date: Re: dcdiag error: DsBindWithSpnEx
- Previous by thread: Re: Copy file at logon
- Next by thread: Re: DNS not authoritative for domain
- Index(es):
Relevant Pages
|
