Linux - EnterpriseThis forum is for all items relating to using Linux in the Enterprise.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm setting up and internal domain, so far portions of the DNS appear to be working however, when I try to ping the domain i.e.: ping cscd.internel I get the following response:
[louis@Lenovo-T510 ~]$ nslookup cscd.internel
;; Got SERVFAIL reply from 10.7.30.20, trying next server
;; Got SERVFAIL reply from 10.7.30.20, trying next server
Server: 208.67.220.220
Address: 208.67.220.220#53
** server can't find cscd.internel: NXDOMAIN
I get the same response when I also do an nslookup cscd.internel.
I have reverse DNS configured with 30.7.10.in-addr-arpa zone that contains the following entry: 25.30.7.10.in-addr-arpa PTR 86400 cscd.internel.
It appears to me that nslookup and ping are looking outside for the resolution. I have and internal resolution so why would it be looking outside? What am I missing?
[louis@Lenovo-T510 ~]$ nslookup cscd.internel
;; Got SERVFAIL reply from 10.7.30.20, trying next server
;; Got SERVFAIL reply from 10.7.30.20, trying next server
Server: 208.67.220.220
Address: 208.67.220.220#53
** server can't find cscd.internel: NXDOMAIN
From the above nslookup output, looks like your server at 10.7.30.20 gives a SERVFAIL, so the next nameserver is used (opendns: 208.67.220.220) that of course gives a NXDOMAIN answer.
You should post here your dns server config file and the zone file, both included in CODE tags for readability, so we could try to help you.
I'm using DNS on a Synology NAS, they've not been very helpful all so I'm working to resolve it on my own. What did you find strange?
Thanks
Getting a SERVFAIL means that there is a misconfiguration somewhere, most likely in the zone file.
The only error I see for now, is that you have both an A and a CNAME record for CSCD-NAS-1.cscd.internel. Delete the latter and see if it helps.
BTW I find strange the zone file format (TTL after RR type for example), but I guess you've posted the contents of the dns config web interface.
If you can export the zone file to the classic format, it could be more useful.
** server can't find 20.30.7.10.in-addr.arpa.: NXDOMAIN
The above suggest that there is no reverse lookup for the IP Address, I checked the above reference and there is no reverse entry for the IP Address 10.7.30.20. Therefore one should be added, should it be a PTR record or NS record because it is the start of the domain?
OK. You've fixed the SERVFAIL problem! Good...bathory was right about the CNAME and A issue.
Now, we're at what I said earlier...there is no A record defined for cscd.internel in the config you posted
There are A records for:
mailserver.cscd.internel
ns.cscd.internel
and
CSCD-NAS-1.cscd.internel
...but none for cscd.internel
a
Code:
nslookup CSCD-NAS-1.cscd.internel
should work just fine.
Try it. Let us know. Use [code] tags when you post your output. Please.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.