jozeph

Well-Known Member
Apr 16, 2004
59
0
156
I don't understand! When logged in the server, I try:

nslookup
server XX.XX.XX.XX (ip of the server)
domain.com

I get:

** server can't find domain.com: SERVFAIL

For ANY OTHER DOMAIN configured on this server, I get the correct message:

Name: domainB.com
Address: XX.XX.XX.XX

I would like to know WHY I can resolve any other domain and just the main domain can not be resolved?
 

jozeph

Well-Known Member
Apr 16, 2004
59
0
156
urgent

I'm hosting DNS for several customers on RH Linux Enterprise Edition. All is working fine except on a single zone, for which this server is authoritative. I tailed the message log then performed a reload, No entries were ever displayed concerning the newly created zone file. When performing an nslookup on the server itself, the error message "**server cannot find requestedfile.com: SERVFAIL" is returned.

dig produces:
; <<>> DiG 9.2.2 <<>> requestedfile.com ANY
;; global options: printcmd ;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 14152 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION:
;requestedfile.com. IN ANY
;; Query time: 6 msec ;; SERVER: 127.0.0.1#53(localhost) ;; WHEN: Fri Jun 25 15:36:10 2004
;; MSG SIZE rcvd: 47

Here is how the zone file looks:
$TTL 3600
@ IN SOA ns1.location.net. hostmaster.location.com. (

2004062502 ; Serial
3H ; Refresh every 3 hours
1H ; Retry every hour
1W ; Expire after a week
1D ) ; Minimum TTL of 1 day

IN NS ns1.location.net.
IN NS ns2.location.net.

IN MX 10 mail.requestedfile.com.
IN A 66.66.156.4
www IN A 66.66.156.4
mail IN A 66.66.156.4

Again, all is functioning properly except for this zone. Any help would be appreciated as I can't see the error.

Thanks in advance!
 

brianoz

Well-Known Member
Mar 13, 2004
1,146
7
168
Melbourne, Australia
cPanel Access Level
Root Administrator
Check your /var/log/messages file (or equivalent), it's likely there's a syntax error in the zone file causing it to be ignored. SERVFAIL means that named doesn't know anything about that zone. The other possibility is that the zone file is not being included from /etc/named.conf or whatever the FreeBSD equivalents are.
 

jozeph

Well-Known Member
Apr 16, 2004
59
0
156
Yes! I tried messages, named.log, etc... But, no error messages on that files!
But now, the problem has been solved! :)