Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a very strange problem that I not able to figure out. On my server I host two applications with two different domains: 1. 2.

I also host a DNS server (fedora server) that I configured to resolve these two domains. The problem is that only the first domain resolve and the other does not.

The zone file for '' is:     IN      SOA (





                        38400 )

@       IN      NS     IN      NS     IN      NS IN      A IN      A     IN      A IN      A IN      A   IN      A

*   IN      A

                        IN      A     IN      MX      10 ASPMX.L.GOOGLE.COM.     IN      MX      20 ALT1.ASPMX.L.GOOGLE.COM.     IN      MX      20 ALT2.ASPMX.L.GOOGLE.COM.     IN      MX      30 ASPMX2.GOOGLEMAIL.COM.     IN      MX      30 ASPMX3.GOOGLEMAIL.COM.     IN      MX      30 ASPMX4.GOOGLEMAIL.COM.     IN      MX      30 ASPMX5.GOOGLEMAIL.COM.     IN      TXT     "v=spf1 a mx ip4: ?all"onlinelogistics:~

Now, for the other domain I did a copy/paste and replaced with "" but still the domain is not found.

The comand "whois" finds the nameservers ( so I am sure the problem is with the DNS server not being able to find the address.

Any ideas are highly appreciated!

Thank you!

share|improve this question

migrated from Jan 12 '10 at 15:29

This question came from our site for professional and enthusiast programmers.

You might want to replace your original IP addresses and names with placeholders... – PEra Jan 12 '10 at 18:51
Very bad advice for PEra: quite the contrary, use REAL names if you want people to help. – bortzmeyer Jan 13 '10 at 8:04
You did not mention the name server software you use. BIND ? – bortzmeyer Jan 13 '10 at 8:05

Have you created the zone in your named.conf file? i.e.:

zone "" {
        type master;
        file "";

According to a dig +trace, it does resolve...and checking via browser, it loads. So is this resolved?

; <<>> DiG 9.2.4 <<>> +trace
;; global options:  printcmd
.                       306040  IN      NS      A.ROOT-SERVERS.NET.
.                       306040  IN      NS      B.ROOT-SERVERS.NET.
.                       306040  IN      NS      C.ROOT-SERVERS.NET.
.                       306040  IN      NS      D.ROOT-SERVERS.NET.
.                       306040  IN      NS      E.ROOT-SERVERS.NET.
.                       306040  IN      NS      F.ROOT-SERVERS.NET.
.                       306040  IN      NS      G.ROOT-SERVERS.NET.
.                       306040  IN      NS      H.ROOT-SERVERS.NET.
.                       306040  IN      NS      I.ROOT-SERVERS.NET.
.                       306040  IN      NS      J.ROOT-SERVERS.NET.
.                       306040  IN      NS      K.ROOT-SERVERS.NET.
.                       306040  IN      NS      L.ROOT-SERVERS.NET.
.                       306040  IN      NS      M.ROOT-SERVERS.NET.
;; Received 316 bytes from in 1 ms

org.                    172800  IN      NS
org.                    172800  IN      NS
org.                    172800  IN      NS      A0.ORG.AFILIAS-NST.INFO.
org.                    172800  IN      NS
org.                    172800  IN      NS      C0.ORG.AFILIAS-NST.INFO.
org.                    172800  IN      NS      A2.ORG.AFILIAS-NST.INFO.
;; Received 439 bytes from in 61 ms    86400   IN      NS    86400   IN      NS    86400   IN      NS    86400   IN      NS
;; Received 180 bytes from in 42 ms    3600    IN      A    86400   IN      NS    86400   IN      NS    86400   IN      NS    86400   IN      NS
;; Received 196 bytes from in 29 ms
share|improve this answer

No, unlike what you say, works, it is which fails:

% check_soa
There was no response from
There was no response from
% check_soa has serial number 1001120004 has serial number 1001120004 has serial number 1001120004 has serial number 1001120004

First thing to do, with every daemon running on Unix: check the log file! BIND, for instance, gives comprehensive information about the zones it loaded or failed to load. This would address greeblesnort's suggestion.

Also, "does not resolve" is not sufficiently precise. Test with dig @your-name-server and report the actual result.

Finally, your zone files would be simpler to read and easier to manage with relative names.

share|improve this answer

Have you got the ip address for the nameservers correct? reports the nameservers ( aren't responding. If this ip address is correct, then likely Bind failed to start because you have errors in your zonefile or named.conf.local. Check both of these using named-checkconf and named-checkzone.

share|improve this answer
And, above all, read BIND log file! – bortzmeyer Jan 13 '10 at 8:03

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.