Re: Win2003 DNS not working using own ip address
- From: "Jeremy Church" <church@xxxxxxxxxx>
- Date: Thu, 21 Dec 2006 09:18:11 -0500
When it comes to DNS name resolution, recursion is necessary unless
referrals can be handled and the client can iteratively resolve names
itself. If you are using iteration, the DNS server will respond to the
client with a list of nearest names servers to resolve the name. If this
name is not in the database on the DNS server queried, the server will most
likely respond with a list of root servers for the client to use for
resolution. The client would then take on the role of a DNS server itself
and resolve the name using iteration.
Depending on the number of computers, this would dramatically increase DNS
traffic to the internet because there would be no name caching server. I
don't believe Windows XP supports this type of name resolution. Because
Windows does not support this type of resolution, when it receives the
response from its query to the DNS server, it will respond with host not
found or something.
Hope this helps.
"MarshMan" <MarshMan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:28255EF6-D336-4371-BBFE-08EA5533442C@xxxxxxxxxxxxxxxx
Thanks Jeremy,
A few pieces of info, I made up bogus IPs for the sake of this post so the
IP can be overlooked. I agree with you concerning forwarding, in fact
forwarding is not an option for me as I have disabled recursion. So
according to
http://207.46.196.114/WindowsServer/en/library/0bcd97e6-b75d-48ce-83ca-bf470573ebdc1033.mspx?mfr=true
I should be resolving names using the iteration method vs recursion.
- server does have a static, valid public IP address
- all root hints are present and configured and I can ping all root
servers
except e and g (I think those are the two I can't reach right now)
- I have selected a specific IP on the Interfaces tab because I do indeed
have multiple IPs / NICs with specific needs running on this server. I
have
confirmed that I have chosen the correct IP address as the listener.
Is there anything else you can think of? It still won't resolve names if
I
key in its own IP into the DNS client setting.
Thanks to both of you.
Darin
"Jeremy Church" wrote:
I would recommend against forwarding to an external DNS server. If your
server is on the inside of your network, there are a few things you can
check.
- Server needs a static IP address on the inside.
- Unless there is some special network setup, your server should not be
pointing to 192.0.2.43 for DNS. This is not a legitimate private IP
address.
- There should be no DNS forwards configured on the server.
- There should be a list of root servers on the Root Servers tab on your
DNS
Server.
- On the interfaces tab in the DNS Server properties, choose All IP
Addresses. Again, unless you have multiple IPs / NICs with a specific
need
to limit the listening IP addresses.
- Set the DNS server to be the same as the IP of the server itself.
Hope this helps
"Bill Grant" <not.available@online> wrote in message
news:OeOWeCwIHHA.1008@xxxxxxxxxxxxxxxxxxxxxxx
Set the local DNS server to forward to a public DNS. It will then be
able to resolve external URLs as well as resolve local requests from
its
own database.
"MarshMan" <MarshMan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:11ED26CA-34D1-4F8B-8D9C-08C9371D67E5@xxxxxxxxxxxxxxxx
when I run the dns report against our domain name of example.com I get
3
warnings, none of them I'm concerned about. This server has used
itself
to
resolve names up until last friday when it's client software
mysteriously
stopped resolving when configured with its own address.
To clarify:
I do a properties on My Network Connections and then properties on
TCP/IP
and set Preferred DNS server: 192.0.2.43 - per DNS report
then at a command prompt type in:
ipconfig /flushdns
and then
ping www.yahoo.com
I get:
Ping request could not find host www.yahoo.com. Please check the name
and
try again.
I then go back to properties on My Network Connections and then
properties
on TCP/IP and set Preferred DNS server: 4.2.2.2 - external dns server
and I can ping www.yahoo.com just fine.
Again last Thursday this server used its own IP as its resolver.
According
to DNS report there are no errors on the "Server Service" side of
things.
I
just can't figure out why the Server Service doesn't seem to want to
resolve
names for itself.
Has anyone else seen this and know the resolution?
Darin
.
- References:
- Re: Win2003 DNS not working using own ip address
- From: Bill Grant
- Re: Win2003 DNS not working using own ip address
- From: Jeremy Church
- Re: Win2003 DNS not working using own ip address
- From: MarshMan
- Re: Win2003 DNS not working using own ip address
- Prev by Date: DHCP Scope based on MAC Vendor ID?
- Next by Date: Re: Share level permissions from Command Prompt
- Previous by thread: Re: Win2003 DNS not working using own ip address
- Next by thread: Re: vpn
- Index(es):
Relevant Pages
|
