DNS problems : "Non-authoritative answer"
apple Verified ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Hi everybody,
i have some problems with my DNS Server!
When im using "+*nslookup hostname*+" i will get this result:
*+Non-authoritative answer:+*
*+Name: hostname.myurl.de+*
*+Address: 80.156.86.77+*
*+Name: hostname.myurl.de+*
*+Address: 62.157.140.132+*
+Sudo changeip -checkhostname+ says: +*The names match. There is nothing to change.*+
I also recognized this in the DNS Log:
+15-Jul-2009 16:59:52.025 checkhints: view com.apple.ServerAdmin.DNS.public: l.root-servers.net/A (199.7.83.42) missing from hints+
+15-Jul-2009 16:59:52.025 checkhints: view com.apple.ServerAdmin.DNS.public: l.root-servers.net/A (198.32.64.12) extra record in hints+
6 replies
Sign in or join Beachball Help to reply.
- 0
Camelot ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
'Non-authoritative answers' are not necessarily a problem.
All it means is that the server you queried is not a master server for the domain in question, so the DNS server reached out to another server to find the answer to your question.
For example, if you run 'nslookup http://www.apple.com', you're likely to get a 'Non-authoritative answer' because your DNS server is not authoritative for 'apple.com', so your server had to go and find the apple.com name servers in order to answer your query.
Now, it
could be a problem if you are querying your own name server for a hostname in your own domain - and that server should be authoritative for that domain. That isn't clear from your post because we don't know what hostname you're actually looking up (unless 'hostname.myurl.de' is the hostname, in which case your server would have to be authoritative for 'myurl.de'... is that the case?)You'll also find that
dig provides far more information about a lookup, including the server details, and can be much more useful than
nslookup when debugging DNS issues. - 0
sykane ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
This is my situation:
I have a regular webspace provider (outsourced) with an URL (lets say it would be http://www.myurl.com).
I set up my OS-X server with the same hostname, i followed the solution provided by makemacwork.com called Split-DNS:*+The most common solution is configuring a “split” DNS, where servers both inside and outside your network control customized resolution of your domain for only those machines that can see them. This would, were I hosting my own email for instance, let internet machines find mail.makemacwork.com at an external IP of 64.13.192.203 routed through my firewall, while still pointing internal clients at 192.168.0.250 on their local network. In this case, both IPs would be the same machine, but with the external record on the DNS server at my ISP and the internal record on my own internal server.+*
*+Even if you’re not hosting any internet-available services, though, your internal machines will see your new DNS server as the authoritative source of information on your domain. So if you’ve outsourced any kind of hosting with the same domain name, you’ll need to put that information in your internal zone record as well.+*
So when im trying to reach http://www.myurl.com my DNS-Server will bring me to the outsourced webserver but if im trying to reach myserver.myurl.com it will bring me to my internal webserver.
So... ** i right that there is no problem?! 😀
- 0
sykane ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Oh no its not working right...!
*+nslookup <myHOSTNAME>+*
*+zdm:~ administrator$ nslookup zdm.<myHOSTNAME<>.de+*
*+Server: 217.0.43.17+*
*+Address: 217.0.43.17#53+**+server can't find zdm.<myHOSTNAME>.de: NXDOMAIN+*
nslookup should return the IP address of my machine, without any error messages. I repeated the test but reverse:
*+nslookup <192.168.0.3>+*
*+zdm:~ administrator$ nslookup 192.168.0.3+*
*+Server: 217.0.43.17+*
*+Address: 217.0.43.17#53+**+server can't find 3.0.168.192.in-addr.arpa.: NXDOMAIN+*
- 0
Mabel O'Farrell ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Do you have all your internal clients and servers configured to use your internal DNS server or your ISPs DNS server? You can setup your internal DNS to be authoritative for your local domain and to resolve only for local network clients and have it configured to forward all requests for resolution for domains that it is not authoritative for to your ISPs DNS servers.
- 0
sykane ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Im testing right now directly from the server.
In the Network Settings of the Server Machine i use under DNS-Server my local machine, but the server *** Forwarder Adresses from my ISP.
I thought that would be right?! - 0
Mabel O'Farrell ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
In the Network Settings of the Server Machine i use under DNS-Server my local machine, but the server *** Forwarder Adresses from my ISP.
You would place your internal DNS server as the only one in the Network preferences on your clients and servers. Then you will have to configure your DNS server to forward all non-authoritative request to your ISPs DNS servers. You may have to edit your zone files by hand to accomplish this. If you do any hand editing you should
stop the DNS server
first using Server Admin, then make
backups of the zone files
before editing them. Some
sample text for setting up forwarding in your zone files:// sample master zone
zone "site.example.com" {
type master;
file "pathto/site.example.com";
// do normal iterative resolution (do not forward)
forwarders { your.ISPs.DNS.serverIP; };
allow-query { internals; };
allow-transfer { internals; };
};// sample slave zone
zone "site.example.com" {
type slave;
file "pathto/site.example.com";
masters { 172.16.72.3; };
forwarders { our.ISPs.DNS.serverIP; };
allow-query { internals; };
allow-transfer { internals; };
};The BIND 9 Admin Reference Manual contains many examples as-well-as necessary options and configuration switches that may be used. It is available in the latest BIND tarball from the ISC:
ftp://ftp.isc.org/isc/bind9/9.7.0a1/bind-9.7.0a1.tar.gz
Uncompress the archive and look in
/doc/arm for the PDF.