Results 1 to 7 of 7
Folks,
I just installed DNS server (bind) on Fedora 11.
In /etc/resolv.conf, I have the following lines:
domain abc.com
search abc.com
nameserver 127.0.0.1
nameserver ....
In /etc/named.conf, I have defined ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 07-20-2009 #1Just Joined!
- Join Date
- Jul 2009
- Posts
- 22
DNS - "abc.com." works but not "abc.com"
Folks,
I just installed DNS server (bind) on Fedora 11.
In /etc/resolv.conf, I have the following lines:
domain abc.com
search abc.com
nameserver 127.0.0.1
nameserver ....
In /etc/named.conf, I have defined a zone "abc.com"
When I do a nslookup,
mybox.abc.com. works. Notice the dot at the end.
However, mybox.abc.com doesn't work.
Also, just mybox does not work either (although abc.com is specified in resolv.conf).
I must be making some simple configuration mistake. Can someone please tell me how to fix this?
Thank you in advance for your help.
Regards,
Peter
- 07-21-2009 #2Just Joined!
- Join Date
- Jul 2009
- Location
- Washington(home), Montana(school), California(internship)
- Posts
- 6
Hey Peter,
I am just an intern and have no idea what you are dealing with. However, maybe it has something to do with fully qualified domain names? I can't post the wiki link, since this is my first post. But search for it on wikipedia and read the entry.
Cheers!In the DNS, and most notably, in DNS zone files, a FQDN is specified with a trailing dot, for example, "somehost.example.com.". The trailing dot denotes the root domain. Most DNS resolvers will process a domain name that contains a dot as being an FQDN[1] or add the final dot needed for the root of the DNS tree. Resolvers will process a domain name without a dot as unqualified and automatically append the system's default domain name and the final dot.
- 07-22-2009 #3Just Joined!
- Join Date
- Jul 2009
- Posts
- 22
- 07-23-2009 #4
Take either DOMAIN or SEARCH statement out of your resolv.conf. You don't need both and I would suggest leaving SEARCH as you can add to this one later if needed.
What does your zone file look like?
What does your named.conf look like?
What does your hosts look like?
- 07-23-2009 #5
You probably left out a trailing dot in a zone file.
Without the trailing dot, you try to resolve foo dot comCode:$TTL 3D localdomain. IN SOA shelly.localdomain. xxxxxxx.xxxxxxx.net. ( 2003060932 ; serial 21600 ; refresh after 6 hours 3600 ; retry after 1 hour 604800 ; expire after 1 week 86400 ) ; minimum TTL of 1 day localdomain. IN NS shelly.localdomain. coffee.localdomain. IN A 192.168.15.130 genius.localdomain. IN A 192.168.15.131 lisa.localdomain. IN A 192.168.15.28 shelly.localdomain. IN A 192.168.15.20 blue.localdomain. IN A 192.168.15.19 kirby.localdomain. IN A 192.168.15.10 ocean.localdomain. IN A 192.168.15.8 stacy.localdomain. IN A 192.168.15.7 router.localdomain. IN A 192.168.15.1 ns.localdomain. IN CNAME kirby.localdomain.
and it looks up foo dot com dot <your domain>
- 07-24-2009 #6
This is one reason why you shouldn't add your records as FQDN to avoid mistakes. You domain will get added automaticly.
- 07-29-2009 #7Just Joined!
- Join Date
- Jul 2009
- Posts
- 8
Please provide your named.conf and zone file.


Reply With Quote

