Announcement

Collapse
No announcement yet.

DNS :non-existent domain error

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • DNS :non-existent domain error

    Howdy guys
    Got a problem with DNS.
    Was working fine up until today.
    We have a Forward Lookup Zone which stores records for our London domain. It's a Standard Secondary zone, and gets it's zone details from one of the London AD-Integrated DNS servers. No problems with domain trusts.

    Even though the relevant host records are all contained within the zone, DNS is unable to resolve. It's as if it doesn't know it's there.

    The nslookup error message is this: <our_dns_server> can't find <host> :non-existent domain

    nslookup can resolve an FQDN but not a host name for this zone.

    What I don't get is that the zone is right there under the Forward Lookup Zone but DNS is unable to read it.
    Anyone seen this before?
    I've deleted the zone and transfered a fresh copy from the London DNS server, which transferred fine but still doesn't work.
    The other 5 Forware Lookup Zones work perfectly.

    Advice most welcome

    Cheers for now

    JHH
    -

  • #2
    Re: DNS :non-existent domain error

    Does the forward lookup zone have the correct records for the host???

    Does the FQDN differ from your servers FQDN??

    Comment


    • #3
      Re: DNS :non-existent domain error

      Yes, the zone has the correct records for all hosts.

      Not sure exactly what you mean by the second question.

      The secondary zone is in a DNS server which is in a different but trusted domain from the secondary zones ADI DNS servers.

      Comment


      • #4
        Re: DNS :non-existent domain error

        The FQDN is the Fully Qualified Domain Name.

        I'm assuming that this is different to the one that you use on your domain.

        Try doing a search for the machine using its fqdn, i.e host.domain.com adn tell us the results.

        Or even easier post a screenshot.

        Comment


        • #5
          Re: DNS :non-existent domain error

          Yeah I know what an FQDN is, dude.

          nslookup can resolve FQDNs of servers on the orher domain.

          It cannot resolve host names.

          Comment


          • #6
            Re: DNS :non-existent domain error

            What happens when you try to resolve the hosts using the FQDN???

            Does it work??

            Do you have a relevant Reverse lookup zone setup for this domain??

            Comment


            • #7
              Re: DNS :non-existent domain error

              nslookup can successfully resolve the FQDN of the hosts, but it cannot resolve the hostname.

              No, there is not a reverse lookup zone for the zone in question, there never has been and it has worked correctly up until today.

              For whatever reason, DNS is unable to 'see' this particular zone anymore. It's as if this particular zone is not even there.

              Will look into problems that cause zones to become invalid, though there are no dodgy characters used in any of the records.

              Cheers

              JHH

              Comment


              • #8
                Re: DNS :non-existent domain error

                Originally posted by johnhenryshammer
                nslookup can successfully resolve the FQDN of the hosts, but it cannot resolve the hostname.
                I'm pretty sure that if you don't specify a FQDN, in the actual query nslookup appends the DNS suffix of the computer you're on to the host name.

                If you have implemented the use of the search list in the Domain Suffix Search Order defined on the DNS tab of the Microsoft TCP/IP Properties page, devolution will not occur. The query will be appended to the domain suffixes specified in the list. To avoid using the search list, always use a Fully Qualified Domain Name (that is, add the trailing dot to the name).
                Taken from http://support.microsoft.com/default...b;EN-US;200525
                Regards,
                Jeremy

                Network Consultant/Engineer
                Baltimore - Washington area and beyond
                www.gma-cpa.com

                Comment


                • #9
                  Re: DNS :non-existent domain error

                  Jeremy you are correct

                  If you append a list of domain names in the DNS Suffix search order it will append the domain name to end of the host name in that order i.e.:

                  abc.com
                  def.com
                  ghi.com

                  Will be appended to the hostname in that order

                  Michael
                  Michael Armstrong
                  www.m80arm.co.uk
                  MCITP: EA, MCTS, MCSE 2003, MCSA 2003: Messaging, CCA, VCP 3.5, 4, 5, VCAP5-DCD, VCAP5-DCA, ITIL, MCP, PGP Certified Technician

                  ** Remember to give credit where credit is due and leave reputation points sigpic where appropriate **

                  Comment


                  • #10
                    Re: DNS :non-existent domain error

                    Thanks guys!

                    Added in the DNS suffixes, now works perfectly.

                    Many many thanks to all who replied ith advice!

                    All the best

                    JHH

                    Comment


                    • #11
                      Re: DNS :non-existent domain error

                      Been thinking about this, and still don't understand why suddenly a particular zone became invalid.

                      What could cause it?

                      Comment


                      • #12
                        Re: DNS :non-existent domain error

                        Originally posted by johnhenryshammer
                        Been thinking about this, and still don't understand why suddenly a particular zone became invalid.

                        What could cause it?
                        Changing/adding DNS suffixes could do it... DHCP configs, TCP/IP configs, Network Identification configs.
                        Regards,
                        Jeremy

                        Network Consultant/Engineer
                        Baltimore - Washington area and beyond
                        www.gma-cpa.com

                        Comment

                        Working...
                        X