Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
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.
Thanks so much MR C. for the tips, hints and suggestions.
In terms of editors I'm using ssh sessions with nano, which I gather should be alright.
In terms of learning DNS I wish I could've taken your courses as you seem well versed in loads of things but I guess I just have to wait for it to come up in my Cisco CCNA which is starting in just under a week now and I'm already nearly finished with the first sommester having started studying for it early, also since the stuff was covered in my university degree about 4 years ago now I think.
I see character \224 for your quote characters in your post. I referred to copy/paste errors earlier. Be sure the double quotes in your named.conf file are actual ASCII quotes.
Sure, of course, download away. I really need (want to) update them to be more useful online tools, and more current. Still, I focused more on fundamentals and less on distro-specific details.
Right, How To's can be used to give you an overview of steps required, but they always fail miserably when any problem occurs. They teach blind following rather than critical thinking and learning.
Location: Under the bridge where proper engineers walkover
Distribution: Various Linux, Solaris, BSD, Cisco
Posts: 443
Original Poster
Rep:
This is the zone file I'm working with:
Code:
;
; BIND data file for example.com
;
$TTL 604800
@ IN SOA ns1.optiplex-networks.com. info.optiplex-networks.com. (
2008092305 ; Serial
7200 ; Refresh
120 ; Retry
2419200 ; Expire
604800) ; Default TTL
;
IN NS ns1.optiplex-networks.com.
optiplex-networks.com. IN MX 10 mail.optiplex-networks.com.
optiplex-networks.com. IN A 192.168.1.50
gx110.optiplex-networks.com. IN A 192.168.1.51
ns1.optiplex-networks.com IN A 192.168.1.51
www.optiplex-networks.com IN A 192.168.1.50
mail.optiplex-networks.com IN A 192.168.1.50
ftp.optiplex-networks.com IN A 192.168.1.51
mail.gx110.optiplex-networks.com IN A 192.168.1.51
ferrari3200.optiplex-networks.com IN A 192.168.1.5
optiplex-networks.com. IN TXT "v=spf1 ip4:192.168.1.50 a mx ~all"
mail IN TXT "v=spf1 a -all"
have checked with checkzone-named and says Ok! Other then that; here phishy phishy???
Your previous usage of the NS record was also correct - a zone file uses a remember-last-name policy, so that you can eliminate the name portion when the previous name was the same. Frankly, I think this form of syntax is plain silly and adds needless complexity for the sake of saving a few characters (and perhaps allowed the author to boast his lexical parsing prowess).
OK, so I decided to take your zone file and save it on my Debian box (the one I loaded bind on yesterday). Stock standard Debian setup, except for the change to named.conf.local and the necessary zone file.
Here's the output:
Quote:
dig @localhost optiplex-networks.com
; <<>> DiG 9.3.4-P1.1 <<>> @localhost optiplex-networks.com
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15481
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;optiplex-networks.com. IN A
;; ANSWER SECTION:
optiplex-networks.com. 604800 IN A 192.168.1.50
;; AUTHORITY SECTION:
optiplex-networks.com. 604800 IN NS ns1.optiplex-networks.com.
Location: Under the bridge where proper engineers walkover
Distribution: Various Linux, Solaris, BSD, Cisco
Posts: 443
Original Poster
Rep:
Again spoken like a man who knows his stuff! But for us mere mortals or well just me in particular, whats going on how come I'm not getting any name resolution with dig or nslookup commands?? Zone file checks out; is actually quite similar to the implementation I had created in my Cisco box, slightly different syntax but hey who's counting.
......So where does the problem lie I wonder?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.