Results 1 to 5 of 5

Thread: Ping does not resolve, nslookup does, DNS queries end up externall

  1. #1
    Mike. Guest

    Ping does not resolve, nslookup does, DNS queries end up externall

    Every so often a few XP machines on our network lose the ability to resolve
    DNS for domains hosted on our internal DNS servers.

    A ping from the XP machine will either not find the host, or will end up
    reaching our External DNS servers to resolve (if the domain in question is on
    that external server as well for public resolution).

    Nslookup does find the correct host and IP address using our internal DNS
    servers.

    ipconfig /flushdns solves this issue at times, other times we have to /renew
    to get everything to resolve properly.

    Any ideas as to what the root of this problem could be?

    Thank you for your time.


  2. #2
    Phillip Windell Guest

    Re: Ping does not resolve, nslookup does, DNS queries end up externall

    Never ever ever allow Client machines to ever even "know" an external DNS
    exists.

    All machines on the LAN (every last one) uses only the internal AD/DNS and
    nothing else,...ever.

    Configure the AD/DNS machine with the ISPs DNS in the Forwarders List or
    leave the list blank and let it default to using Root Hints.

    Make sure the Firewall allows *only* the AD/DNS machines to make outbound
    DNS Queries. The Firewall should not allow any other machine to ever make
    DNS queries.

    --
    Phillip Windell
    www.wandtv.com

    The views expressed, are my own and not those of my employer, or Microsoft,
    or anyone else associated with me, including my cats.
    -----------------------------------------------------


    "Mike." <Mike. @discussions.microsoft.com> wrote in message
    news:9252E1B3-94E8-4B15-AE26-9D12268A6A34@microsoft.com...
    > Every so often a few XP machines on our network lose the ability to
    > resolve
    > DNS for domains hosted on our internal DNS servers.
    >
    > A ping from the XP machine will either not find the host, or will end up
    > reaching our External DNS servers to resolve (if the domain in question is
    > on
    > that external server as well for public resolution).
    >
    > Nslookup does find the correct host and IP address using our internal DNS
    > servers.
    >
    > ipconfig /flushdns solves this issue at times, other times we have to
    > /renew
    > to get everything to resolve properly.
    >
    > Any ideas as to what the root of this problem could be?
    >
    > Thank you for your time.
    >




  3. #3
    Mike. Guest

    Re: Ping does not resolve, nslookup does, DNS queries end up exter

    Yes, it looks like one of my DHCP servers had both the internal and external
    DNS servers on the scope. I have removed the external, and ensured that the
    external ones are in the forwarders.

    Thank you for your time.

    "Phillip Windell" wrote:

    > Never ever ever allow Client machines to ever even "know" an external DNS
    > exists.
    >
    > All machines on the LAN (every last one) uses only the internal AD/DNS and
    > nothing else,...ever.
    >
    > Configure the AD/DNS machine with the ISPs DNS in the Forwarders List or
    > leave the list blank and let it default to using Root Hints.
    >
    > Make sure the Firewall allows *only* the AD/DNS machines to make outbound
    > DNS Queries. The Firewall should not allow any other machine to ever make
    > DNS queries.
    >
    > --
    > Phillip Windell
    > www.wandtv.com
    >
    > The views expressed, are my own and not those of my employer, or Microsoft,
    > or anyone else associated with me, including my cats.
    > -----------------------------------------------------
    >
    >
    > "Mike." <Mike. @discussions.microsoft.com> wrote in message
    > news:9252E1B3-94E8-4B15-AE26-9D12268A6A34@microsoft.com...
    > > Every so often a few XP machines on our network lose the ability to
    > > resolve
    > > DNS for domains hosted on our internal DNS servers.
    > >
    > > A ping from the XP machine will either not find the host, or will end up
    > > reaching our External DNS servers to resolve (if the domain in question is
    > > on
    > > that external server as well for public resolution).
    > >
    > > Nslookup does find the correct host and IP address using our internal DNS
    > > servers.
    > >
    > > ipconfig /flushdns solves this issue at times, other times we have to
    > > /renew
    > > to get everything to resolve properly.
    > >
    > > Any ideas as to what the root of this problem could be?
    > >
    > > Thank you for your time.
    > >

    >
    >
    >


  4. #4
    Phillip Windell Guest

    Re: Ping does not resolve, nslookup does, DNS queries end up exter

    Good to hear Mike, glad it worked out.


    --
    Phillip Windell
    www.wandtv.com

    The views expressed, are my own and not those of my employer, or Microsoft,
    or anyone else associated with me, including my cats.
    -----------------------------------------------------

    "Mike." <Mike@discussions.microsoft.com> wrote in message
    news:3DB6EAEC-E63A-440D-B1BA-DBB4BD2CFFDF@microsoft.com...
    > Yes, it looks like one of my DHCP servers had both the internal and
    > external
    > DNS servers on the scope. I have removed the external, and ensured that
    > the
    > external ones are in the forwarders.
    >
    > Thank you for your time.
    >
    > "Phillip Windell" wrote:
    >
    >> Never ever ever allow Client machines to ever even "know" an external DNS
    >> exists.
    >>
    >> All machines on the LAN (every last one) uses only the internal AD/DNS
    >> and
    >> nothing else,...ever.
    >>
    >> Configure the AD/DNS machine with the ISPs DNS in the Forwarders List or
    >> leave the list blank and let it default to using Root Hints.
    >>
    >> Make sure the Firewall allows *only* the AD/DNS machines to make outbound
    >> DNS Queries. The Firewall should not allow any other machine to ever make
    >> DNS queries.
    >>
    >> --
    >> Phillip Windell
    >> www.wandtv.com
    >>
    >> The views expressed, are my own and not those of my employer, or
    >> Microsoft,
    >> or anyone else associated with me, including my cats.
    >> -----------------------------------------------------
    >>
    >>
    >> "Mike." <Mike. @discussions.microsoft.com> wrote in message
    >> news:9252E1B3-94E8-4B15-AE26-9D12268A6A34@microsoft.com...
    >> > Every so often a few XP machines on our network lose the ability to
    >> > resolve
    >> > DNS for domains hosted on our internal DNS servers.
    >> >
    >> > A ping from the XP machine will either not find the host, or will end
    >> > up
    >> > reaching our External DNS servers to resolve (if the domain in question
    >> > is
    >> > on
    >> > that external server as well for public resolution).
    >> >
    >> > Nslookup does find the correct host and IP address using our internal
    >> > DNS
    >> > servers.
    >> >
    >> > ipconfig /flushdns solves this issue at times, other times we have to
    >> > /renew
    >> > to get everything to resolve properly.
    >> >
    >> > Any ideas as to what the root of this problem could be?
    >> >
    >> > Thank you for your time.
    >> >

    >>
    >>
    >>




  5. #5
    dennyd Guest
    good job, You dont need the external server. your internal dns server will use roothints to resolve external queries.
    Quote Originally Posted by Mike. View Post
    Yes, it looks like one of my DHCP servers had both the internal and external
    DNS servers on the scope. I have removed the external, and ensured that the
    external ones are in the forwarders.

    Thank you for your time.

    "Phillip Windell" wrote:

    > Never ever ever allow Client machines to ever even "know" an external DNS
    > exists.
    >
    > All machines on the LAN (every last one) uses only the internal AD/DNS and
    > nothing else,...ever.
    >
    > Configure the AD/DNS machine with the ISPs DNS in the Forwarders List or
    > leave the list blank and let it default to using Root Hints.
    >
    > Make sure the Firewall allows *only* the AD/DNS machines to make outbound
    > DNS Queries. The Firewall should not allow any other machine to ever make
    > DNS queries.
    >
    > --
    > Phillip Windell
    > www.wandtv.com
    >
    > The views expressed, are my own and not those of my employer, or Microsoft,
    > or anyone else associated with me, including my cats.
    > -----------------------------------------------------
    >
    >
    > "Mike." <Mike. @discussions.microsoft.com> wrote in message
    > news:9252E1B3-94E8-4B15-AE26-9D12268A6A34@microsoft.com...
    > > Every so often a few XP machines on our network lose the ability to
    > > resolve
    > > DNS for domains hosted on our internal DNS servers.
    > >
    > > A ping from the XP machine will either not find the host, or will end up
    > > reaching our External DNS servers to resolve (if the domain in question is
    > > on
    > > that external server as well for public resolution).
    > >
    > > Nslookup does find the correct host and IP address using our internal DNS
    > > servers.
    > >
    > > ipconfig /flushdns solves this issue at times, other times we have to
    > > /renew
    > > to get everything to resolve properly.
    > >
    > > Any ideas as to what the root of this problem could be?
    > >
    > > Thank you for your time.
    > >

    >
    >
    >

Similar Threads

  1. DNS resolve problem with ping but not nslookup
    By vagniphor in forum Windows Server Help
    Replies: 9
    Last Post: 12-08-2011, 12:52 AM
  2. Ping returns the wrong name; nslookup OK
    By Phil Tuttiett in forum Windows Server Help
    Replies: 5
    Last Post: 14-09-2009, 09:20 AM
  3. Replies: 3
    Last Post: 05-02-2009, 01:27 PM
  4. Can nslookup dns but cannot ping name
    By Colarado in forum Networking & Security
    Replies: 3
    Last Post: 30-09-2008, 02:32 PM
  5. Ping fails to resolve name but nslookup OK
    By AXJ in forum Windows Server Help
    Replies: 5
    Last Post: 18-04-2008, 11:08 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •